Full read-write Claude connector for MeisterTask
Make Claude create cards and move work across your board in MeisterTask
Stop dragging cards and chasing status by hand. Claude creates tasks in the right project section, moves them across the board, assigns owners and due dates, and posts updates where the work already lives, once you approve.
MeisterTask is a kanban-style project and task manager where teams organize work into projects, sections, and cards that move across a board. People want Claude to do more than read a board: to create cards, move them between sections, and assign work inside the right project.
What is a MeisterTask MCP server?
A MeisterTask MCP server is a small hosted service that exposes MeisterTask's data and actions to Claude over the Model Context Protocol, so Claude can tasks, projects, and docs inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can MeisterTask's current connector do today?
Today, MeisterTask offers a public API and an integration directory, and Claude can connect through them to read projects, sections, and tasks. Coverage of write actions like creating cards, moving them across sections, assigning owners, and setting due dates varies by setup and may be limited. A custom MeisterTask connector adds those writes with scoped, human-in-the-loop controls.
What does full read-write MeisterTask access unlock?
Full read-write MeisterTask access lets Claude create a task in the right project section, move cards across the board, set assignees and due dates, add checklist items and tags, and post comments as work progresses. The board upkeep that used to mean dragging cards by hand happens where the work already lives, once you approve.
- Create a task in a chosen project and section with a due date and description
- Move a card between sections to reflect its current status
- Assign a task to a teammate and set or shift its due date
- Add checklist items or tags to break down and triage a card
- Post a comment on a task to capture context for the team
- Complete or archive cards after you approve the change
Can Claude create and move cards in MeisterTask?
Yes. With a full read-write MeisterTask connector, Claude can create a task in the right project and section with a due date and description, then move that card between sections to reflect its current status. Read-only setups can only list what already exists, which is why writes need a purpose-built connector.
Can Claude assign tasks and set due dates in MeisterTask?
Claude can assign a task to a teammate, set or shift its due date, and add checklist items or tags to break a card down. It can also post a comment to capture context for the team. Every write stays inside the projects and sections your own account can already reach.
Will Claude archive or delete my MeisterTask cards on its own?
No. Completing, archiving, and deleting cards are gated actions that run only after you confirm them. Claude can prepare the change and show exactly which tasks it affects, while routine writes like creating or moving a card can flow directly. Nothing gets removed from your board by surprise.
How a MeisterTask connector works
We build a small MCP server that authenticates to MeisterTask with OAuth or a scoped API token and requests only the access the work needs. Read tools (list projects, sections, and tasks) and write tools (create, move, assign, comment) are separated, and destructive or outbound actions like deleting or archiving a card require your confirmation. Claude never has more access to your MeisterTask than your own account already has.
Frequently asked questions
Can Claude create and move MeisterTask cards, not just read the board?
Will Claude delete or archive my MeisterTask cards without approval?
Does the MeisterTask connector get more access than I have?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.