Codecks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODECKS_URL | Yes | Your Codecks organization URL (e.g., yourteam.codecks.io). | |
| CODECKS_TOKEN | Yes | Your auth token. Found in browser cookies as 'at' for your Codecks domain. | |
| CODECKS_USER_ID | Yes | Your Codecks user ID, required for create and update operations. | |
| CODECKS_DEFAULT_PROJECT | No | Optional: Default project filter (can be overridden per-call). |
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 |
|---|---|
| codecks_list_cardsB | List all cards from Codecks. Optionally filter by deck name, project, and/or status. Returns derivedStatus for each card. |
| codecks_search_cardsC | Search cards by title or content within a project. |
| codecks_get_cardC | Get a specific card by its ID |
| codecks_list_projectsA | List all Codecks projects with their IDs. Use this to find a project ID for configuration. |
| codecks_list_decksA | List all decks in a project with card counts and space info. Uses default project if not specified. |
| codecks_create_cardB | Create a new card in a deck. Specify either deckId or deckName (with optional project for name resolution). |
| codecks_create_deckB | Create a new deck in a project, optionally in a specific space. |
| codecks_create_projectC | Create a new project in the Codecks organization. |
| codecks_update_cardC | Update the content of an existing card. |
| codecks_move_cardC | Move a card to a different deck. |
| codecks_complete_cardC | Mark a card as complete or incomplete. |
| codecks_archive_cardB | Archive a card. Use this for cards that are done and no longer needed in active view. |
| codecks_unarchive_cardA | Unarchive a card, making it visible again. Use this to undo an accidental archive. |
| codecks_update_deckC | Rename a deck by updating its title. |
| codecks_list_spacesC | List all spaces in a project. Spaces are containers for organizing decks. |
| codecks_create_spaceC | Create a new space in a project. Spaces are containers for organizing decks. |
| codecks_rename_spaceC | Rename a space in a project. |
| codecks_delete_spaceA | Delete a space from a project. Cannot delete the default space (ID 1). |
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 18 tools
Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific resource (card, deck, project, space) and action (create, list, get, update, archive, move, etc.), making it easy for an agent to select the correct tool. For example, codecks_archive_card and codecks_unarchive_card are complementary but distinct operations.
Tool names follow a consistent verb_noun pattern throughout, all using snake_case with the prefix 'codecks_' for clarity. The naming convention is predictable: codecks_<action>_<resource>, such as codecks_create_card, codecks_list_decks, and codecks_update_deck, which enhances readability and usability.
With 18 tools, the server is well-scoped for managing a project management system like Codecks, covering cards, decks, projects, and spaces comprehensively. Each tool earns its place by providing necessary CRUD and lifecycle operations without being excessive, making it suitable for agent workflows.
The tool surface offers complete CRUD and lifecycle coverage for the domain of project management in Codecks. It includes creation, listing, updating, and deletion (where applicable) for all resources (cards, decks, projects, spaces), along with specific operations like archiving, moving, and searching, leaving no obvious gaps for agent interactions.