Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Codecks MCP Server Create a new card for the inventory bug fix in the Backlog deck"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP (Model Context Protocol) server that lets AI assistants interact with Codecks project management. Query cards, create tasks, update status, and manage your game dev workflow directly from Claude or other MCP-compatible AI tools.
Repository: github.com/microkorg/Codecks-MCP
List & Search Cards - Query all cards or filter by deck/project/status, search by title/content
Create Cards & Decks - Add new tasks directly from your AI assistant, reference decks by name or ID
Update Cards - Modify card content, move between decks, rename decks
Status Management - Mark cards complete, archive/unarchive finished work
Space Management - List, create, rename, and delete spaces (deck containers)
Flexible Project Filtering - Set a default project or specify per-call for cross-project workflows
Related MCP server: Todocko MCP Server
git clone https://github.com/microkorg/Codecks-MCP.git
cd Codecks-MCPThen run the setup script for your platform:
Windows: setup.bat
Mac/Linux: bash setup.sh
This installs dependencies and creates your .env config file. See Configuration below for how to find your token and user ID.
Edit .env with your Codecks credentials:
# Required: Your auth token (see below for how to find it)
CODECKS_TOKEN=your_token_here
# Required: Your Codecks organization URL
CODECKS_URL=yourteam.codecks.io
# Optional: Default project filter (can be overridden per-call)
CODECKS_DEFAULT_PROJECT=My Project
# Required for create/update operations
CODECKS_USER_ID=your_user_id_hereOpen your Codecks organization in your browser
Press F12 to open Developer Tools
Go to Application tab > Cookies > your codecks domain
Find the cookie named at and copy its value
Open Developer Tools (F12) > Network tab
Create any card in Codecks
Find the request to api.codecks.io/dispatch/cards/create
Look at the request payload - the userId field is your user ID
Add to your .claude/settings.json:
{
"mcpServers": {
"codecks": {
"command": "node",
"args": ["/path/to/codecks-mcp/index.js"],
"cwd": "/path/to/codecks-mcp"
}
}
}Optionally, prevent Claude from reading your credentials:
{
"deny": ["path/to/codecks-mcp/.env"]
}Tool | Description |
| List all cards, optionally filter by deck name, project, and/or status |
| Search cards by title or content |
| Get a specific card by ID |
| Create a new card in a deck (by ID or name) |
| Update card content |
| Move a card to a different deck |
| Mark a card as complete or incomplete |
| Archive a card |
| Unarchive a card, making it visible again |
Tool | Description |
| List all decks in a project with card counts and space info |
| Create a new deck, optionally in a specific space |
| Rename a deck |
Tool | Description |
| List all spaces in a project |
| Create a new space (deck container) |
| Rename a space |
| Delete a space (cannot delete the default space) |
Tool | Description |
| List all projects in your organization |
| Create a new project |
Once configured, you can ask Claude things like:
"What cards are in my backlog?"
"Show me all started cards"
"Create a card for implementing the save system in the Ideas deck"
"Mark the authentication card as complete"
"Move the UI polish card to the In Progress deck"
"Show me all cards in the other project"
"Create a deck called 'Sprint 1' in the Design space"
"What spaces are in this project?"
"Rename the Art deck to Art Assets"
The at cookie token may expire. If you start getting authentication errors, grab a fresh token from your browser cookies.
MIT
Archive a card. Use this for cards that are done and no longer needed in active view.
Inputs: cardId (required).
Mark a card as complete or incomplete.
Inputs: cardId (required), complete (required).
Create a new card in a deck. Specify either deckId or deckName (with optional project for name resolution).
Inputs: content (required), deckId, deckName, project.
Create a new deck in a project, optionally in a specific space.
Inputs: title (required), project, spaceId.
Create a new project in the Codecks organization.
Inputs: name (required).
Create a new space in a project. Spaces are containers for organizing decks.
Inputs: name (required), project.
Delete a space from a project. Cannot delete the default space (ID 1).
Inputs: spaceId (required), project.
Get a specific card by its ID
Inputs: id (required).
List all cards from Codecks. Optionally filter by deck name, project, and/or status. Returns derivedStatus for each card.
Inputs: deck, project, status.
List all decks in a project with card counts and space info. Uses default project if not specified.
Inputs: project.
List all Codecks projects with their IDs. Use this to find a project ID for configuration.
Inputs: no named parameters.
List all spaces in a project. Spaces are containers for organizing decks.
Inputs: project.
Move a card to a different deck.
Inputs: cardId (required), deckId (required).
Rename a space in a project.
Inputs: spaceId (required), name (required), project.
Search cards by title or content within a project.
Inputs: query (required), project.
Unarchive a card, making it visible again. Use this to undo an accidental archive.
Inputs: cardId (required).
Update the content of an existing card.
Inputs: cardId (required), content (required).
Rename a deck by updating its title.
Inputs: deckId (required), title (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
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.
Manage Redbooth tasks, task lists, comments, tags and files from Claude and other AI assistants.
Create and manage MeisterTask projects, tasks, and notes from your AI assistant.
Manage Loom projects, tasks, bugs, defects, clients and phases from AI assistants
Manage Orangescrum projects, tasks, users, sprints, test cases, releases, and risks from AI tools.
