Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect MeisterTask to Claude Code

Make Claude create cards and move work across your board in MeisterTask. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect MeisterTask to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect MeisterTask, you add a MeisterTask MCP server: a small hosted service that exposes MeisterTask's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own MeisterTask account. No API keys pasted into config files.

claude mcp add --transport http meistertask https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in MeisterTask once connected?

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

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same MeisterTask access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the MeisterTask API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when MeisterTask changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build MeisterTask connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same MeisterTask connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own MeisterTask account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on MeisterTask's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to MeisterTask?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the MeisterTask account it signs in with. Revoking access is one click in MeisterTask.

More on the MeisterTask connector

MeisterTask connector for claude.aiTodoist + Claude CodeTeamwork + Claude CodeShortcut + Claude Code

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.

Build my connectorTalk to us