codecks

A simple Model Context Protocol server for basic Codecks task management

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio simokod-codecks-mcp node /path/to/codecks-mcp/dist/server.js \
  --env CODECKS_SUBDOMAIN="your_actual_subdomain" \
  --env CODECKS_AUTH_TOKEN="your_actual_auth_token"

How to use

Codecks MCP is a server that exposes a set of Model Context Protocol (MCP) endpoints for managing Codecks cards and decks. It enables AI assistants and other MCP clients to create, read, update, and organize cards, as well as browse and create decks, with smart filtering to find cards by status or archive state. The server is designed to integrate with your Codecks account via your authentication token and subdomain, allowing programmatic manipulation of task items and collections through standard MCP tool commands. The included tools cover core operations such as listing spaces, cards, and decks, as well as creating and updating cards and decks, and retrieving option data like effort scales and priorities for card creation.

How to install

Prerequisites:

Node.js (and npm) installed on your machine
Access to the Codecks MCP repository or package source

Installation steps:

Clone or download the Codecks MCP repository
Install dependencies npm install
Build the server (if a build step is required, e.g., TypeScript to JavaScript) npm run build
Run the MCP server (example) node dist/server.js
Ensure the MCP client configuration points to the running server and includes required environment variables (see mcp_config examples)

Notes:

If your setup uses a different build path, adjust the args path to the compiled server file accordingly.
You may deploy this in a container or server environment; ensure your environment variables are securely configured.

Additional notes

Environment variables required by Codecks MCP:

CODECKS_AUTH_TOKEN: Your Codecks API token with appropriate privileges
CODECKS_SUBDOMAIN: Your Codecks subdomain (e.g., 'myteam' from https://myteam.codecks.io) Security tips:
Do not commit tokens to version control.
Rotate tokens periodically and revoke unused tokens. Configuration tips:
The MCP config should be placed in the client's MCP configuration file (e.g., ~/.cursor/mcp.json) and reference the server's command, arguments, and environment variables. Common issues:
If the server fails to start due to port or path issues, verify that the path to dist/server.js is correct and that Node can access it.
Ensure network access between the MCP client and the Codecks MCP server, especially in restrictive environments.

Related MCP Servers

vikunja

Model Context Protocol server for Vikunja task management. Enables AI assistants to interact with Vikunja instances via MCP.

taskflow

A task management Model Context Protocol (MCP) server that helps AI assistants break down user requests into manageable tasks with subtasks, dependencies, and notes. Enforces a structured workflow with user approval steps.

cursor-feedback-extension

Save your Cursor monthly quota! Unlimited AI interactions in one conversation via MCP feedback loop.

mcpdog

🐕 Universal MCP Server Manager - Configure once, manage multiple MCP servers through a single interface. Perfect for Claude Desktop, Claude Code, Cursor, Gemini CLI & AI assistants. Web dashboard, auto-detection, unified proxy layer.

attio

Model Context Protocol server for Attio CRM - enables Claude Desktop and Cursor to interact with your Attio workspace

mermaid-live

MCP server from iishyfishyy/mermaid-live-mcp