PixdataOrg Coderide

What PixdataOrg-coderide MCP server does

PixdataOrg-coderide MCP server exposes CodeRide task and project management through the Model Context Protocol. It is intended for AI coding assistants and IDEs that need to work from structured project context rather than relying on manually copied task details.

The server supports task retrieval, task updates, project lookup, project updates, task-specific prompts, and workflow navigation. An assistant can inspect a task, change its description or status, obtain instructions for starting work, and move toward the next task in a sequence. Project-level operations include listing projects, retrieving project details, and maintaining project knowledge such as a knowledge graph or architecture diagram.

How it works

An MCP client launches the package with npx -y @coderide/mcp. The client sends tool calls to the local server, which uses the configured CodeRide API key to access the corresponding workspace in production. Responses are returned as compact JSON, according to the README, to reduce the amount of context used by the model.

The documented tools include get_task, update_task, get_prompt, get_project, and update_project. Task identifiers use values such as APP-101, while projects can be addressed by a slug and, for project lookup, optionally by name. Task status values include to-do, in-progress, and done.

Setup and configuration

PixdataOrg-coderide MCP server requires Node.js and npm for the traditional setup. Add it to an MCP client configuration with a stdio command similar to:

{
  "mcpServers": {
    "CodeRide": {
      "command": "npx",
      "args": ["-y", "@coderide/mcp"],
      "env": {
        "CODERIDE_API_KEY": "YOUR_CODERIDE_API_KEY_HERE"
      }
    }
  }
}

For real CodeRide data, provide an active CodeRide account and an API key beginning with CR_API_KEY_. The README also documents Smithery installation for Claude Desktop. In Smithery, leaving the key empty or supplying a placeholder selects mock mode, which provides sample projects and tasks without making real API calls. A valid production key selects access to the connected CodeRide workspace.

Tools and capabilities

The README describes nine tools covering these areas:

• Retrieve an individual task or list project tasks.
• Update task descriptions and statuses.
• Get the first or next task in a project workflow.
• Retrieve prompts or instructions associated with a task.
• List projects and retrieve project details.
• Update project knowledge graphs and architecture diagrams.

These operations suit workflows where an assistant needs to understand the current task, perform implementation work, and report progress back to CodeRide.

Limitations and notes

PixdataOrg-coderide MCP server is centered on CodeRide; the provided material does not document connectors to other task-management systems. Production access depends on a valid CodeRide API key and workspace scope. Mock mode is for testing and uses sample data, so changes made there do not represent real project updates. The README names Cursor, Cline, Windsurf, and Claude Desktop, while also referring generally to other MCP clients.