Model Context Protocol server for CodeRide, task management redesigned for AI
Model Context Protocol server for CodeRide, task management redesigned for AI. Exposed over MCP by the coderide mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Imagine your AI not just writing code, but truly understanding project context, managing its own tasks, and collaborating seamlessly with you. No more endless copy-pasting or manual updates. With CodeRide MCP, your AI becomes a first-class citizen in your CodeRide workflow.
Everything the assistant can do here goes through one of these:
get_task — Retrieves detailed information about a specific task by its number (e.g., "TCA-3")update_task — Updates an existing task's description, status, or other mutable fieldsget_prompt — Retrieves the specific prompt or instructions tailored for an AI agent to work on a given taskget_project — The get_project tool exposed by this serverupdate_project — Updates a project's high-level information, such as its knowledge graph or system architecture diagramstart_project — Retrieves the first or next recommended task for a given project, allowing an AI to begin workInstallation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need one environment variable: CODERIDE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the planning and project tracking options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Coderide MCP's toolset — get_task, update_task, get_prompt and 3 more — is a fair guide to whether it matches your workflow. It is maintained by PixdataOrg; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Coderide MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_task | Retrieves detailed information about a specific task by its number (e.g., "TCA-3"). |
| update_task | Updates an existing task's description, status, or other mutable fields. |
| get_prompt | Retrieves the specific prompt or instructions tailored for an AI agent to work on a given task. |
| get_project | The get_project tool exposed by this server. |
| update_project | Updates a project's high-level information, such as its knowledge graph or system architecture diagram. |
| start_project | Retrieves the first or next recommended task for a given project, allowing an AI to begin work. |
{
"mcpServers": {
"coderide": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"CODERIDE_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CODERIDE_API_KEY | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.