codecks-mcp
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 show me my daily standup summary"
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.
codecks-mcp
TypeScript MCP server for Codecks project management. Exposes 32+ tools for managing cards, decks, milestones, tags, and PM workflows via the Model Context Protocol.
Built with @modelcontextprotocol/server, zod, and Express.
Quick Start
# Run directly (no install needed)
npx codecks-mcp
# Or install globally
npm install -g codecks-mcp
codecks-mcpRelated MCP server: TypeScript Tools MCP
Configuration
Create a .env file in your working directory:
CODECKS_TOKEN=your_session_cookie
CODECKS_ACCOUNT=your_account_slugTokens
Variable | Source | Expires |
| Browser DevTools > Cookie | Yes |
| CLI | No |
| Your Codecks account slug | N/A |
| Auto-discovered if unset | N/A |
Optional Settings
Variable | Default | Description |
|
|
|
|
| Request timeout |
|
| Retry count |
Transports
stdio (default)
codecks-mcpHTTP
codecks-mcp --transport http --port 3000Endpoints:
POST /mcp— MCP protocol (Streamable HTTP)GET /ping— Health check
IDE Setup
Claude Code
{
"mcpServers": {
"codecks": {
"command": "npx",
"args": ["-y", "codecks-mcp"]
}
}
}Cursor
{
"mcpServers": {
"codecks": {
"command": "npx",
"args": ["-y", "codecks-mcp"]
}
}
}Remote (HTTP)
{
"mcpServers": {
"codecks": {
"url": "http://localhost:3000/mcp"
}
}
}Tools
Read (10)
Tool | Description |
| Current account info |
| List/filter cards with pagination |
| Full card details |
| All decks |
| Projects with decks |
| Milestones |
| Project-level tags |
| Recent activity feed |
| PM dashboard (blocked, stale, suggested) |
| Daily standup summary |
Hand (3)
Tool | Description |
| Personal work queue |
| Add cards to hand |
| Remove cards from hand |
Mutation (9)
Tool | Description |
| Create card (supports sub-cards) |
| Batch update properties |
| Mark cards done |
| Mark cards started |
| Archive (reversible) |
| Restore archived |
| Permanent delete |
| Hero + lane sub-cards |
| Batch-split features |
Comments (5)
Tool | Description |
| Start thread |
| Reply to thread |
| Resolve thread |
| Reopen thread |
| List threads |
PM Session (3)
Tool | Description |
| Methodology guide |
| Load preferences |
| Save preferences |
Feedback (2)
Tool | Description |
| Save feedback |
| Read feedback |
Security
Prompt injection detection (6 regex patterns)
[USER_DATA]boundary tagging on user-authored contentInput validation with zod schemas + length limits
UUID validation on all card IDs
Control character stripping
Development
# Install
pnpm install
# Dev mode (tsx, auto-reload)
pnpm dev
# Build
pnpm build
# Test
pnpm test
# Lint + format
pnpm lint
pnpm format:check
# Type check
pnpm typecheckAlso Available
Python version: codecks-mcp-python — same tools, Python runtime
Full CLI: codecks-cli — CLI + library with formatters, GDD sync, and more
License
MIT
Available Tools
38 toolsadd_to_handAdd to HandC
Add cards to the user's hand.
Inputs: card_ids (required).
archive_cardArchive CardA
Archive a card (reversible).
Inputs: card_id (required).
close_commentClose CommentC
Close (resolve) a comment thread.
Inputs: thread_id (required), card_id (required).
create_cardCreate CardB
Create a new card. Set deck/project to place it. Use parent to nest as sub-card.
Inputs: title (required), content, deck, project, +4 more.
create_commentCreate CommentC
Start a new comment thread on a card.
Inputs: card_id (required), message (required).
delete_cardDelete CardA
Permanently delete a card. Cannot be undone — use archive_card if reversibility needed.
Inputs: card_id (required).
get_accountGet AccountB
Get current account info (name, id, email, role).
Inputs: no named parameters.
get_cardGet CardC
Get full card details (content, checklist, sub-cards, conversations, hand status).
Inputs: card_id (required), include_content, include_conversations, archived.
get_cli_feedbackGet CLI FeedbackA
Read saved CLI feedback items. Optionally filter by category. No auth needed.
Inputs: category.
get_lane_registryGet Lane RegistryB
Get the local lane (deck category) definitions and metadata. No auth needed.
Inputs: required_only.
get_pm_playbookGet PM PlaybookB
Get PM session methodology guide. No auth needed.
Inputs: no named parameters.
get_tag_registryGet Tag RegistryA
Get the local tag taxonomy (definitions, hero tags, lane-tag mappings). No auth needed.
Inputs: category.
get_workflow_preferencesGet Workflow PreferencesA
Load user workflow preferences from past sessions. No auth needed.
Inputs: no named parameters.
list_activityList ActivityC
Show recent activity feed.
Inputs: limit.
list_cardsList CardsC
List cards. Filters combine with AND.
Inputs: deck, status, project, search, +15 more.
list_conversationsList ConversationsC
List all comment threads on a card with messages and thread IDs.
Inputs: card_id (required).
list_decksList DecksB
List all decks. Set include_card_counts=True for per-deck counts.
Inputs: include_card_counts.
list_handList HandB
List cards in the user's hand (personal work queue), sorted by hand order.
Inputs: no named parameters.
list_milestonesList MilestonesB
List all milestones with card counts.
Inputs: no named parameters.
list_projectsList ProjectsB
List all projects with deck info.
Inputs: no named parameters.
list_tagsList TagsB
List project-level tags (sanctioned taxonomy).
Inputs: no named parameters.
mark_doneMark DoneC
Mark cards as done.
Inputs: card_ids (required).
mark_startedMark StartedC
Mark cards as started.
Inputs: card_ids (required).
planning_initPlanning InitA
Create lean planning files (task_plan.md, findings.md, progress.md) in project root. No auth needed.
Inputs: force.
planning_measurePlanning MeasureA
Track token usage of planning files over time. No auth needed. Operations: snapshot, report, compare_templates.
Inputs: operation (required).
planning_statusPlanning StatusB
Get compact planning status: goal, phases, decisions, errors, token count. No auth needed.
Inputs: no named parameters.
planning_updatePlanning UpdateC
Update planning files mechanically. No auth needed. Operations: goal, advance, phase_status, error, decision, finding, issue, log, file_changed, test.
Inputs: operation (required), text, phase, status, +7 more.
pm_focusPM FocusC
PM focus dashboard: blocked, stale, unassigned, and suggested next cards.
Inputs: project, owner, limit, stale_days.
remove_from_handRemove from HandC
Remove cards from the user's hand.
Inputs: card_ids (required).
reopen_commentReopen CommentC
Reopen a closed comment thread.
Inputs: thread_id (required), card_id (required).
reply_commentReply CommentC
Reply to an existing comment thread.
Inputs: thread_id (required), message (required).
save_cli_feedbackSave CLI FeedbackC
Save a CLI feedback item for the development team. No auth needed.
Inputs: category (required), message (required), tool_name, context.
save_workflow_preferencesSave Workflow PreferencesB
Save observed workflow patterns from current session. No auth needed.
Inputs: observations (required).
scaffold_featureScaffold FeatureC
Create a Hero card with Code/Design/Art/Audio sub-cards.
Inputs: title (required), hero_deck (required), code_deck (required), design_deck (required), +9 more.
split_featuresSplit FeaturesB
Batch-split unsplit feature cards into lane sub-cards. Use dry_run=true to preview.
Inputs: deck (required), code_deck (required), design_deck (required), art_deck, +5 more.
standupStandupC
Daily standup summary: recently done, in-progress, blocked, and hand.
Inputs: days, project, owner.
unarchive_cardUnarchive CardB
Restore an archived card.
Inputs: card_id (required).
update_cardsUpdate CardsB
Update card properties. Doc cards: only owner/tags/milestone/deck/title/content/hero.
Inputs: card_ids (required), status, priority, effort, +9 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 38 tools
Most tools have distinct purposes, but some overlap exists. For example, 'list_cards' and 'list_hand' both list cards, with the latter being a filtered subset, which could cause confusion. Similarly, 'mark_done' and 'mark_started' are clear, but 'archive_card' and 'delete_card' are distinguished by reversibility, which might not be immediately obvious. Overall, descriptions help clarify, but there is moderate overlap in card-related operations.
Tool names follow a consistent verb_noun pattern throughout, such as 'create_card', 'list_cards', and 'update_cards'. Minor deviations include 'scaffold_feature' and 'split_features', which use slightly different verbs but maintain readability. The naming is largely predictable, with only a few tools breaking the pattern without causing significant confusion.
With 38 tools, the count is excessive for a project management server, making it feel heavy and potentially overwhelming. While the domain is broad, many tools could be consolidated or omitted without losing functionality. This high number increases complexity and reduces usability for agents, indicating poor scoping.
The tool set provides comprehensive coverage for project management tasks, including CRUD operations for cards, comments, and planning, along with workflow utilities and reporting. It supports full lifecycle management from creation to archiving, with no apparent gaps. The inclusion of planning, feedback, and preference tools ensures agents can handle all core workflows without dead ends.
Maintenance
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
A MCP server built for developers enabling Git based project management with project and personal…
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for generating rough-draft project plans from natural-language prompts.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA server implementation of the Model Context Protocol (MCP) for managing development workflow with features like project management, task tracking, and QA review support.3AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides TypeScript development tools for automated refactoring and code analysis.1-
- AlicenseBqualityDmaintenanceA TypeScript-based MCP server that provides tools to interact with local Codex and Gemini CLIs via stdio transport. It enables users to execute prompts through the ask_codex and ask_gemini tools, supporting custom models and timeout configurations.111 npm6MIT
- AlicenseAqualityDmaintenanceA lightweight MCP server that provides 40 tools for TypeScript/JavaScript refactoring and code intelligence, directly mapping to TypeScript's tsserver protocol commands for accurate structural changes and workspace analysis.4029 npm3MIT