coderide
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODERIDE_API_KEY | Yes | Your CodeRide API key, which you can obtain from your workspace settings on app.coderide.ai |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_projectB | 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. |
| get_promptB | 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_taskA | Retrieves detailed information for a specific task using its unique task number (e.g., 'CRD-1'). |
| get_projectA | Retrieves detailed information about a specific project using its unique 'slug' (three uppercase letters, e.g., 'CRD'). |
| list_projectsA | Lists all projects in the user workspace. No input parameters required as the workspace is automatically determined from the API key authentication. |
| list_tasksA | 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_taskA | 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. |
| update_taskA | 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. |
| update_projectA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a distinct purpose: getting, listing, updating, or starting projects/tasks. No two tools overlap in functionality, making it easy for an agent to select the right one.
Tools mostly follow a verb_noun pattern (get_project, list_tasks, update_task), but 'next_task' deviates by using a noun phrase instead of a verb. This minor inconsistency is still clear.
With 9 tools, the set is well-scoped for a project/task management server. Each tool serves a clear purpose without being excessive or too sparse.
The domain appears to be project and task management, but there is no way to create or delete projects or tasks. Only update and list/get operations are provided, which is a significant gap for a complete workflow.