Claude Code can read and update your tasks while it works in your repository. Ask it to pick up a task by its reference and carry on from the note, park a follow-up it noticed as a task with a day on it, and close the task when the change is merged.
No API key. One command, then a sign-in.
Connect
Already connected Taskaid on claude.ai? Claude Code picks up that connector when you're signed in with the same Claude account. It shows in claude mcp list as claude.ai Taskaid, and there's nothing more to do.
Otherwise:
-
Add the server:
claude mcp add --scope user --transport http taskaid https://taskaid.ai/mcp--scope usermakes it available in every project, since your tasks aren't tied to a repository. Without it, Claude Code adds the server to the current project only. -
Sign in:
claude mcp login taskaidYour browser opens Taskaid's sign-in; approve the access you want to grant. Claude Code prints Authenticated with "taskaid" when it's done. You can also sign in from a session: run
/mcp, select taskaid and choose Authenticate. -
Check it with
claude mcp list, which shows taskaid as Connected.
Claude Code identifies itself to Taskaid when you sign in, so there's no client ID or secret to enter.
Try it
- "Read TASKAID-45 and carry on from its note."
- "Add a task to remove the old config path after this ships, next Friday, in the Backend list."
- "Before you finish, save what we decided and why as a note on TASKAID-45."
- "What's on my plate today?"
A task's note is Markdown, so it's a fair place for Claude Code to leave the reasoning behind a change for the next session, in Claude Code or anywhere else. More starting points on the Assistants page.
What Claude Code can do
Claude Code asks before it uses a tool you haven't allowed, and you can allow a Taskaid tool once or for good. Taskaid has no delete tool, so Claude Code cannot delete anything even if you ask it to.
Every task it creates records where it came from. Through the server you added, that's Claude Code. Through the claude.ai connector it's Claude, because the connector is the one you made on claude.ai.
Every action runs as your own account, limited to what you approved, and your data is never used to train AI models. For the tools themselves see the MCP server reference, and our Privacy Policy and Terms of Service for everything else.
Questions
Can I use Taskaid from scripts with claude -p?
Yes. Allow Taskaid's tools for the run with --allowedTools: mcp__taskaid allows every Taskaid tool, or name one, such as mcp__taskaid__search_tasks. Through the claude.ai connector the prefix is mcp__claude_ai_Taskaid instead.
Can I sign in over SSH?
Yes. claude mcp login taskaid --no-browser prints the sign-in link instead of opening a browser. Open it on any machine, approve, then paste the address your browser lands on back into the terminal.
Manage or disconnect
claude mcp logout taskaid signs Claude Code out of Taskaid, and claude mcp remove taskaid removes the server. The claude.ai connector is removed on claude.ai, at claude.ai/customize/connectors. To revoke access from Taskaid's side, open Settings and disconnect Claude Code under Connected apps.
Troubleshooting
claude mcp list shows "Needs authentication". Run claude mcp login taskaid and approve once more.
Taskaid's tools show up twice. You've added the server and also connected Taskaid on claude.ai, so Claude Code runs both. Keep one: run claude mcp remove taskaid, or remove the connector on claude.ai.
Claude Code asks you to sign in again. Your access was revoked. Run claude mcp login taskaid.
