# Mewboard MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.mewboard%2Fmewboard
Registry id: `mcp-registry/com.mewboard/mewboard`
Status: live (checked 2026-11-22T18:54:35.869Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 801
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "mewboard-mcp-server": {
      "type": "http",
      "url": "https://app.mewboard.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http mewboard-mcp-server https://app.mewboard.com/mcp
```

## Tools (66)

- `add_checklist`: Add a named checklist to an issue. Optionally give the item texts to create with it. Returns the checklist with item ids.
- `add_checklist_item`: Add one item to an existing checklist (use the checklist id from get_issue / read_issue).
- `add_comment`: Add a Markdown comment to an issue or to a project (give exactly one of issue/project).
- `attach_file`: Upload a file and attach it to an issue, project, or comment. Send the file content as base64 in content_base64 (up to 25 MB). Returns `markdown` (a ready relat
- `create_client`: Create a client (a person or company). Only name is required. Then give projects or issues a `client`.
- `create_field`: Add a custom field to a project, e.g. Price (money, UAH), Hours (number), Platform (select), Client contact (text). Types: text, number, money (an amount in the
- `create_form`: Create a questionnaire for a client in a project (platform owner only). Give `markdown` (headings = sections, numbered lines = questions, indented "- " lines un
- `create_issue`: Create an issue (task) in a project. Description supports Markdown.
- `create_milestone`: Create a milestone in a project.
- `create_project`: Create a project. Issues get identifiers like KEY-1. key is derived from the name if omitted. Give it an `icon`: ONE emoji that fits what the project is about (
- `create_reminder`: Remind a person about an issue, a project or a comment at a time. It is delivered to the channels that person switched on (the bell in Mewboard, email, Telegram
- `create_template`: Create an own template of the workspace from scratch, e.g. a project template for a kind of client work with its board columns, fields and starter tasks. kind p
- `delete_attachment`: Delete an attachment.
- `delete_checklist`: Delete a whole checklist with its items.
- `delete_client`: Delete a client. Its projects and issues are kept and just lose the client link.
- `delete_comment`: Delete a comment of an issue or project for good, with the files attached to it. Use update_comment to change the text instead.
- `delete_field`: Delete a custom field of a project together with its values in every issue.
- `delete_issue`: Delete an issue: it moves to the trash with its comments and attachments and is erased for good when the trash period of the server ends (14 days by default; it
- `delete_milestone`: Delete a milestone (its issues stay, unassigned).
- `delete_reminder`: Cancel (delete) a reminder of the token owner.
- `follow_issue`: Follow an issue: hear about its comments, status and due date changes, checklists and files.
- `get_client_totals`: The money of all projects of a client: per project (see get_project_totals) and the totals of the fields across them. Use it for "how much does this client owe 
- `get_issue`: Get an issue (by identifier like WEB-12 or id) including its attachment list and checklists with item ids (no comments or file contents).
- `get_mewboard_guide`: What Mewboard can do and which tool does what, with typical requests. Read it when unsure how to do something.
- `get_money_report`: The money report of the workspace, from the payments fields of every project you can see: received, expenses (negative payments), net, expected and overdue mone
- `get_project`: Get one project by key (e.g. "WEB") or id, with the list of files attached to the project itself (its Overview). To read the description, comments and the CONTE
- `get_project_totals`: The money of a project (sub-projects included unless subprojects=false): the total of every number / money / payments / numeric formula field (summed by field n
- `get_template`: Read one own template of the workspace with all its projects, statuses, fields, milestones, starter tasks and checklists (see list_templates for ids). A templat
- `import_issues`: Create many issues of one project at once (up to 2000), e.g. a list or a payment history moved from a spreadsheet or another CRM. New fields can be created in t
- `list_attachments`: List attachments of an issue, of a project (the files on the project Overview, not those of its issues) or of a comment.
- `list_changes`: List the change history as batches, newest first: who changed what (issue fields, created / trashed / restored issues, added / edited / deleted comments), group
- `list_clients`: List the clients of the workspace (the people or companies projects are for) with their projects and the number of open issues.
- `list_comments`: List comments on an issue (issue=WEB-12) or on a project (project=WEB), with their attachment metadata.
- `list_fields`: List the custom fields of a project (name, type, options, currency of money fields, formula of formula fields). Their values are set with fields: { "Field name"
- `list_following`: The issues I follow in this workspace (newest change first) and why: author, assignee, comment, mention or follow.
- `list_form_responses`: Read the answers clients sent to a questionnaire: the form with its questions, and every response keyed by question id (platform owner only).
- `list_forms`: List the questionnaires of a project with their links and answer counts (platform owner only).
- `list_issues`: List/filter issues. status may be comma-separated (e.g. "todo,in_progress"): kinds, or names of the project's own statuses.
- `list_members`: List the members of the workspace (people and agent accounts) an issue can be assigned to. Use their name as `assignee`, or "me".
- `list_milestones`: List milestones of a project with progress (issue_done / issue_total).
- `list_notifications`: What is new FOR ME: changes by other people (or their agents) in the issues I follow, @mentions, assignments and my reminders, newest first. unread_only = only 
- `list_projects`: List all projects with issue counts per status. A sub-project has parent_id and path (its parents, from the top). with_money: true adds each project's money (bu
- `list_reminders`: List the reminders of the token owner (pending, and the ones that fired in the last 7 days). Optionally for one issue or project; status: open (default), pendin
- `list_templates`: List the own templates of the workspace: kind project (start a project from it with create_project template) or workspace (offered when a new workspace is creat
- `list_trash`: Issues (and projects) in the trash, restorable for a while (14 days by default).
- `mark_notifications_read`: Mark all my notifications as read (the bell count goes to zero).
- `read_attachment`: Read ONE attachment. Images are returned as images; text/JSON/CSV/Markdown files as text; PDFs as text plus page images; Word/Excel/PowerPoint/OpenDocument/EPUB
- `read_issue`: READ EVERYTHING about an issue in one call: fields, full description, ALL comments, and the content of ALL files — attached to the issue, attached to comments, 
- `read_project`: READ EVERYTHING about a project in one call: description, ALL project-level comments, and the content of ALL files attached to the project, its comments, or lin
- `restore_issue`: Bring an issue back from the trash (see list_trash).
- `save_project_as_template`: Save a project as a template of the workspace: its statuses, custom fields, milestones and (unless issues=false) its open issues with their checklists, unticked
- `search`: Full-text-ish search over issue titles/descriptions and projects.
- `set_project_notifications`: How much I hear about a project: all (every change and every new issue), mine (only the issues I follow; the default) or mute (only @mentions).
- `set_project_statuses`: Give a project its own statuses (board columns), e.g. for a shop: New order, Paid, Packing, Shipped, Delivered, Returned. Each status is one of 6 kinds (backlog
- `try_formula`: Try a formula on the newest issues of a project before saving it as a formula field: returns each issue's result, or the mistake in the formula. FORMULA languag
- `undo_changes`: Undo a whole batch (give batch = the batch id from list_changes) or selected changes (change_ids). Safe by default: a field is put back only if it still has the
- `unfollow_issue`: Stop following an issue (an @mention or a new comment of yours makes you follow it again).
- `update_checklist_item`: Tick or untick a checklist item (done true/false) and/or change its text.
- `update_client`: Update a client (name, company, email, phone, notes). client = its name or id.
- `update_comment`: Edit a comment body and / or pin it (pinned: true) or unpin it (false). Pinned comments are shown in a bar at the top of the issue (or project) discussion; list
- `update_field`: Rename a custom field (formulas that use it follow), change its options, its formula, the currency of a money or formula field (amounts stay as they are) or whe
- `update_form`: Edit a questionnaire: title, description, thanks message, task, questions (list or markdown), status open/closed, or regenerate=true for a new link (the old one
- `update_issue`: Update an issue: change status (move on the board), priority, assignee, labels, milestone, title or description. Pass milestone_id "" to clear. due_date (YYYY-M
- `update_milestone`: Update a milestone: rename it, change its description, target date or status (planned, in_progress, done). Its issues stay as they are.
- `update_project`: Update project name/description/status/dates. Changing key renames every issue identifier (WEB-12 -> NEW-12).
- `update_template`: Replace the content of an own template (its author or an administrator): name and/or the whole list of projects. Read it first with get_template, change it, sen

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
