get_project
Retrieves detailed information about a specific project using its unique 'slug' (three uppercase letters, e.g., 'CRD').
LABSCO SUMMARY
Tasks addressed the way people say them out loud, so an agent can pick one up and hand it back.
Everything is keyed on the slug and task number you already use — CRD, CRD-1 — instead of internal IDs, and the workspace comes from the API key, so no call carries a workspace parameter. Beyond reading tasks, it writes back: status and description on the task, knowledge and a Mermaid architecture diagram on the project. The mock mode is worth knowing about before you wire it up — with no key you get sample data, not an error.
What it is
A server over CodeRide, a task tracker built for AI agents. Tasks and projects are addressed by readable identifiers — project slug CRD, task number CRD-1 — and the agent reads, works, and updates in place.
What you get
- The full detail of one task by its number, and the tailored prompt written for that task
- All tasks in a project, organized by status column with their order
- The next task in sequence from wherever you are
- The first task of a project plus the project details, for starting work on something new
- Every project in the workspace, with the workspace resolved from the API key rather than passed in
- Task updates that write a new description, a new status, or both
- Project-level knowledge updated in place, including an architecture diagram in Mermaid form
Requirements
A CodeRide account and a workspace API key from app.coderide.ai — production keys start with CR_API_KEY_. Run it with npx -y @coderide/mcp and CODERIDE_API_KEY in the environment; the npm package is @coderide/mcp, currently 0.9.3, over stdio, and it needs Node.js and npm. Calls go to https://api.coderide.ai. Leaving the key empty or setting a placeholder starts a mock mode instead, with sample projects ABC and XYZ and tasks like ABC-1 — all nine tools respond, nothing reaches the real API.
Setup effort
One command plus a key — npx -y @smithery/cli install @PixdataOrg/coderide --client claude, then supply credentials
USE CASES
01
Handing an agent the ticket it should be working on
Fetch the task by number along with the prompt written for it, so the requirements arrive intact.
02
Closing out work that just got done
Update the task's status and rewrite the description to match what actually shipped.
03
Keeping momentum through a project queue
Ask for the next task after the one you just finished and open its prompt.
04
Starting on a project you have not touched before
Pull the project details together with its very first task.
05
Keeping the architecture diagram current after a refactor
Write the new Mermaid diagram and the updated project knowledge back onto the project.
06
Working out what is left in a project
List its tasks organized by status column and read the order they are meant to happen in.
9 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_prompt
Retrieves the specific instructions or prompt for a given task, identified by its unique task number (e.g., 'CRD-1'). This is typically used to understand the detailed requirements or context for an AI agent to work on the task.
get_task
Retrieves detailed information for a specific task using its unique task number (e.g., 'CRD-1').
list_projects
Lists all projects in the user workspace. No input parameters required as the workspace is automatically determined from the API key authentication.
list_tasks
Lists all tasks within a project using the project slug (e.g., 'CDB'). Returns tasks organized by status columns with their order and current status.
next_task
Retrieves the next task in sequence based on the current task number (e.g., CDB-23 → CDB-24). This is useful for finding the next task that needs to be done in a project workflow.
start_project
Retrieves the project details and the prompt for the very first task of a specified project using the project's unique slug (e.g., 'CRD'). This is useful for initiating work on a new project or understanding its starting point.
update_project
Updates a project's knowledge graph data and/or its structure diagram (in Mermaid.js format). The project is identified by its unique 'slug'. At least one of 'project_knowledge' or 'project_diagram' must be provided for an update to occur.
update_task
Updates an existing task's 'description' and/or 'status'. The task is identified by its unique 'number' (e.g., 'CRD-1'). At least one of 'description' or 'status' must be provided for an update.
BEFORE YOU INSTALL
What to know first
Tools you get
9 tools when we connected. With an empty or placeholder CODERIDE_API_KEY the server returns mock data; a key starting CR_API_KEY_ connects to your real workspace. v0.8.0 renamed tools, for example project_list to list_projects.
Requires
- npx on PATH
- CODERIDE_API_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 9 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Claude Desktop — Smithery
TERMINAL
npx -y @smithery/cli install @PixdataOrg/coderide --client claudeMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"CodeRide": {
"command": "npx",
"args": [
"-y",
"@coderide/mcp"
],
"env": {
"CODERIDE_API_KEY": "<YOUR_CODERIDE_API_KEY>"
}
}
}
}
