MeisterTask
by MeisterTask
Run MeisterTask projects, tasks and Notes from an AI agent. 64 live tools, 23 read and 41 write, with 24 flagged destructive. OAuth sign-in, free on every plan, currently in public beta.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect MeisterTask via MCP
https://mcp.meistertask.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect MeisterTask once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioMeisterTask Tools & Capabilities (64)
List all MeisterTask projects with their sections.
Get a MeisterTask project by ID or token with sections and metadata. Provide exactly one of id or token.
Create a new MeisterTask project. If sectionNames is omitted, default sections (Open, In Progress, Done) are created.
Update a project's properties: name, notes, status (ACTIVE|TRASHED|ARCHIVED), share mode, start/end dates. Does not return sections — use mt_projects_get after update if you need them.
Move a project to trash. The project remains in the database and can be restored with status ACTIVE. Archiving is a separate status change that keeps the project out of the trash.
List all sections (columns) in a MeisterTask project. Sections represent stages like To Do, In Progress, Done.
Create a new section (column) in a MeisterTask project. Requires projectId.
Update a section's status, name, color, WIP limit, ordering, indicator, or description. Setting status to 'trashed' moves the section and its tasks to trash; setting it to 'active' restores the section.
Move a section to trash. Any tasks in the section are also trashed. The section can be restored via mt_sections_update by setting status back to "active".
List active (open or completed) tasks in a MeisterTask project. Requires projectId. Returns tasks with tokens, assignee, section, and labels. Archived, cancelled, and trashed tasks are not included — use mt_tasks_search with a status filter for those. Results are limited (default 200, max 500).
Create a task in a MeisterTask section. Requires sectionId. Returns task with ID, token, and URL.
Get full task details by token. Supports optional expansions for attachments, checklists, custom fields, and parent project with labels.
Add a comment to a task. Provide either taskId (numeric) or taskToken.
List recent activities on a task including comments, attachment changes, and checklist updates. Provide either taskId (numeric) or taskToken. Supports pagination.
Update a task's properties. Provide either id (numeric) or taskToken. Can change name, notes, status (open|completed|cancelled|trashed|archived), assignee, section (to move between columns), or due date.
Move a task to trash (soft delete, not permanent). Provide either id (numeric) or taskToken. The task remains in the database and can be restored by setting its status to "open".
Duplicate a task, optionally including its subtasks. Provide either id (numeric) or taskToken. The duplicate is created in the same section. Returns the new task with its own ID and token.
Remove the timeline item (start/end date bar) from a task without deleting the task itself. Provide either taskId (numeric) or taskToken; the timeline item is resolved from the task.
Search tasks across MeisterTask projects using text, status, assignee, project, label, section, and date filters. Supports pagination and returns full task snapshots with project context.
Upload a file attachment to a task. Provide either taskId (numeric) or taskToken. Provide the file via exactly one of: - url — publicly hosted file fetched server-side and stored as an attachment (max 25 MB). - data — base64 obtained programmatically (e.g. reading a local file). Do not transcribe a file from the conversation into base64 because its bytes are unavailable; ask the user to provide a URL or file path. Small files only (~100 KB practical; the remote HTTP transport rejects requests over 1 MB).
Attach an external URL to a task as a link reference without uploading or fetching its contents. Accepts any valid URL and optional display name and MIME contentType. Provide either taskId (numeric) or taskToken.
List all attachments on a task. Provide either taskId (numeric) or taskToken.
Delete an attachment from a task.
List all checklists and items on a task. Requires a task token.
Create a new checklist on a task. Requires numeric taskId.
Add an item to a checklist. Requires numeric checklistId.
Update a checklist item. Toggle checked state, rename, move between checklists, or reorder.
Delete a checklist item.
List all labels in a project.
Create a new label in a project. Colors are 6-digit hex without # prefix (e.g., "FF0000" for red).
Update a label name or color.
Delete a label from a project. Removes the label from all tasks where it was attached.
Attach a label to a task. Both label and task must belong to the same project. Returns the task_label ID needed for mt_tasks_labels_remove.
Remove a label from a task. Requires the task_label ID (returned by mt_tasks_labels_add), NOT the label ID.
List all members, individual access rights, and pending invites for a project. Returns memberships (Groups/Teams), rights (individual users with names), and pending invites (id and role only — not the invited email address).
Add a Group or Team to a project. For individual users, use mt_projects_invite with an email address — the create_project_membership mutation does not accept individual users.
Remove a Group or Team from a project. Requires the membership ID (from mt_projects_members_list), NOT the member/user ID.
Invite an individual user to a project by email. Sends an invitation; use mt_projects_members_add for Groups/Teams.
Get the current session owner (your identity). Returns your person ID, name, and team. Use this to understand who you are acting as.
List all team members. Returns person IDs, names, and avatars. Use this to build a person directory for resolving personId references in discussions, comments, and task assignments.
Resolve one or more person IDs to names and profiles in a single request.
Link two tasks with a relationship: "blocks", "blocked_by", "duplicate_of", "related_to", "is_child_of" (subtask), or "is_parent_of" (parent). Both tasks must be accessible to the caller.
Remove a task relationship by its numeric ID.
Execute up to 150 create/update/destroy operations in a single API call. Each change: { event: "create"|"update"|"destroy", itemType, id?, data? } Item types: Task, Section, Comment, Checklist, ChecklistItem, Label, TaskLabel Temp IDs: every create gets a unique negative temp ID, auto-assigned when omitted. Supply your own (-1, -2...) only to reference the new entity from other changes in the same batch. Positive id required for update/destroy. FIELDS (* = required for create): Task: name*, section_id*, assigned_to_id, due (ISO 8601), notes, status (open|completed|cancelled|trashed|archived), sequence Section: name*, project_id*, color, description, sequence, status (active|trashed), indicator, limit Comment: text*, task_id* — text supports inline @mention tags: <person_id>123</person_id>, <group_id>456</group_id>, <here/> (everyone on task), <all/> (everyone in project). Resolve person IDs via mt_projects_members_list first; a non-member mention rejects the whole comment. Checklist: name*, task_id*, sequence ChecklistItem: name*, checklist_id*, checked (boolean), sequence Label: name*, color*, project_id* TaskLabel: task_id*, label_id* Auto-conversions: due → timestamp, status → integer, checked → integer. Response: idMapping (your temp IDs→real IDs), status ("success"|"partial_success"|"conflict"), pendingChanges, results. results[] follows the sorted order destroy→create→update, not submission order. EXAMPLE: {"event":"create","itemType":"Section","id":-1,"data":{"name":"Sprint 1","project_id":123}} {"event":"create","itemType":"Task","id":-2,"data":{"name":"Design API","section_id":-1}} {"event":"create","itemType":"Task","id":-3,"data":{"name":"Implement API","section_id":-1}}
Get a single note with markdown content, revisionId, task links, and identifiers needed for follow-up actions.
Get metadata for multiple notes by tokens. Returns titles, status, and dates — not full block content.
List root-level notes by status. Returns note metadata (name, token, type, dates) but NOT full block content.
List direct child notes of a parent note by token. Returns one level of children. If a note's content is empty or minimal, it likely serves as a container; use this tool to discover child notes before concluding it has no useful content.
Create a note from markdown. If parentToken is provided, creates a child note under that parent; otherwise creates a root-level note. Returns the created note token, name, and URL.
Rename a note without changing its content. Resolves the note token internally before updating the title.
Replace a note's entire markdown body. This is a full replacement, not a partial update. Requires the latest revisionId for optimistic concurrency; if the revision changed, re-fetch and retry.
Move a note to trash or archive (soft delete, not permanent). Use mt_notes_restore to undo, or mt_notes_list with status TRASH/ARCHIVE to find affected notes.
Restore a note from trash or archive back to active status. Use mt_notes_list with status TRASH or ARCHIVE to find notes that can be restored.
Move a note under a different parent. Resolves tokens internally and appends after existing children by default.
List the user's favorite (starred) notes with their tokens.
List note groups (folders) that organize notes. Returns group metadata.
List discussions on a note, filtered by status (ACTIVE or RESOLVED). Requires the numeric note ID. Each discussion includes its comments.
Start a new discussion on a note. Accepts plain text which is wrapped internally; for advanced structured content (mentions, formatting), pass a raw Quill Delta via dataJson.
Mark a discussion as RESOLVED. Comments can no longer be added to resolved discussions — reopen by sending DiscussionUpdateInput with status ACTIVE (no MCP tool for that yet).
Add a comment to an existing discussion. The discussion must be ACTIVE (resolved discussions reject new comments). Accepts plain text which is wrapped as Quill Delta; for mentions or formatting, pass raw content via contentJson.
Edit an existing comment. Only the comment author can update their own comments (server returns access_denied otherwise).
Delete a comment. Only the comment author can delete their own comments.
Search across MeisterTask content (tasks, projects, notes, blocks). Returns items with type, token/ID, and URL.
Get notifications from MeisterTask. Includes mentions, task updates, note comments, and other activity. Filter by product origin (MT/MN), type (mentions only), or status (unread/all). Supports pagination.
Read from the server on 2026-09-09, including each tool's own safety annotations.
Limits
- It is a public beta. MeisterTask says so in the help article and marks it Beta on all four plans in the pricing comparison (both retrieved 2026-09-09). Behaviour and the tool set can change without notice.
- Notes containing Discussions or linked tasks cannot be edited. MeisterTask documents this directly: such Notes remain readable through the connector, but editing them is unsupported. It is the vendor's most consequential stated gap, and it hits exactly the collaborative Notes a team most wants an agent to maintain.
- One account at a time. MeisterTask states Claude can be connected to only one Meister account simultaneously; switching means disconnecting and re-authenticating.
- No admin blocking. MeisterTask states team-level restrictions for the MCP server are not currently available. Individual users connect and disconnect at will, with no vendor-provided team control.
- No self-hosting. MeisterTask states this is not available and directs organisations needing it to Meister Support.
- OAuth is all-or-nothing. The server advertises exactly two scopes,
meistertaskandopenid, with no read-only variant. - Some plan-gated features have tools but may not have data. MeisterTask's pricing comparison gates custom fields and subtasks to Business and Enterprise, yet
mt_tasks_getexposes anincludeCustomFieldsexpansion andmt_tasks_relationships_createaccepts an is_child_of subtask relationship. The tools exist on every plan; whether they return or create anything on Basic and Pro is not something MeisterTask documents, and we did not call a tool to find out. - Rate limits are published on the wire, not in the docs. The 401 response carried
RateLimit-Limit: 100with a 60-second window (observed 2026-09-09). MeisterTask does not state a rate limit for the MCP server in its help article, so treat the header as an observation of one unauthenticated response rather than a documented policy. - Reopening a resolved discussion has no tool.
mt_notes_discussions_resolvesays so itself: reopening requires a DiscussionUpdateInput call, and there is no MCP tool for that yet. - We did not execute any tool. Every claim above comes from schemas, annotations, descriptions and vendor documentation. No MeisterTask data was read or written.
Frequently asked questions
No. MeisterTask lists MCP as a Beta feature on all four plans, including the free Basic tier, in its published pricing comparison retrieved on 2026-09-09. That is unusual: the same table gates Full API access behind Pro and above. The connector reaches your workspace on a plan that cannot use the REST API.
No. MeisterTask states that Claude can currently only edit Notes that do not contain Discussions or linked MeisterTask tasks. Notes carrying either can still be read through the connector, but editing them is not supported. This is the vendor's own documented limitation, published in its MCP help article on 2026-09-09.
No. MeisterTask documents that Claude can only be connected to one Meister account at a time. To switch, disconnect the connector and authenticate again with the other account. There is no tool on the server for selecting an account or workspace after the sign-in has completed.
No. MeisterTask states the MCP server does not draw on the monthly prompt allowance included with Meister AI features, and that usage limits, billing and model access are managed by Claude instead. Meister AI credits are consumed by in-product features such as the Writing Assistant, not by this connector.
Not currently. MeisterTask states that team-level restrictions for the MCP server are not available, and that users can connect or disconnect Claude at any time. An admin who wants to prevent workspace access through an AI agent has no vendor-provided control, as documented on 2026-09-09.
Only what your own account can already reach. MeisterTask states Claude cannot access content that your Meister account itself lacks permission to view or edit. Within that boundary it can read Notes, tasks, projects and mind maps, create and edit supported Notes, create projects and tasks, and update task statuses and assignments.
No. MeisterTask states self-hosting is currently not available, and directs organisations that require it to contact the Meister Support team. The connector runs only as the vendor-hosted remote endpoint at mcp.meistertask.com, which is the single address every MCP client connects to, and there is no on-premise or self-managed deployment option published.
No. MeisterTask states Claude only performs actions when instructed through prompts and within the permissions granted to your account. The server backs this with annotations: 41 of its 64 tools declare themselves as writes, so a client that surfaces those flags can require your approval before each one runs.
No. MeisterTask labels it public beta in its help article and marks it Beta on all four plans in its pricing comparison, both retrieved 2026-09-09. The vendor also warns in the same article that AI can make mistakes and to double-check any changes to Meister content before relying on them.
Sources
- MeisterTask MCP Server help article (article last edited 2026-09-09; retrieved 2026-09-09). The HTML route returned HTTP 403 to our client behind a Cloudflare interstitial;
support.meistertask.com/robots.txtreturns 200 and disallows neither/hc/*/articles/nor the public Zendesk Help Center API, so we read the article throughapi/v2/help_center/en-us/articles/35486711538322.json, which returned 200. The 403 is a client-reputation block, not a policy refusal. · retrieved 2026-09-09 - Live
initialize,tools/list,resources/list,resources/templates/listandprompts/listagainsthttps://mcp.meistertask.com/mcp— 64 tools, 1 resource, 1 resource template, no prompts capability (2026-09-09). No tool was called. · retrieved 2026-09-09 - Live OAuth posture check — anonymous request returned HTTP 401 with a
WWW-Authenticate: Bearerheader naming an RFC 9728 descriptor (2026-09-09). · retrieved 2026-09-09 - MeisterTask OAuth descriptors —
https://mcp.meistertask.com/.well-known/oauth-protected-resourceandhttps://mcp.meistertask.com/.well-known/oauth-authorization-server, both HTTP 200 (2026-09-09). · retrieved 2026-09-09 - MeisterTask pricing, machine-readable edition (retrieved 2026-09-09). Linked from the pricing page as "machine-readable pricing (for AI agents)"; source for the Beta-on-all-plans row and the custom-fields and subtasks plan gates. · retrieved 2026-09-09
- MeisterTask pricing page (retrieved 2026-09-09). · retrieved 2026-09-09
- MeisterTask product site — and (both retrieved 2026-09-09).
robots.txtisAllow: /with a sitemap and noContent-Signalline. · retrieved 2026-09-09 - Anthropic Connectors Directory entry (snapshot 2026-09-08), source of the partner tier and the pre-rename tool list. · retrieved 2026-09-08
- MeisterTask support — · Privacy — · Vendor — MeisterLabs,
Server Info
- Category
- Productivity
- Developer
- MeisterTask
- Tools
- 64
- Domain
- mcp.meistertask.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Productivity
Related Resources
Ready to connect MeisterTask?
Connect MeisterTask once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.