Codecks

Provides programmatic access to Codecks cards, decks, spaces, and projects via MCP for creating, updating, searching, and organizing work.
  • javascript

0

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "microkorg-codecks-mcp": {
      "command": "node",
      "args": [
        "/path/to/codecks-mcp/index.js"
      ],
      "env": {
        "CODECKS_URL": "YOUR_TEAM_CODECKS_URL",
        "CODECKS_TOKEN": "YOUR_TOKEN",
        "CODECKS_USER_ID": "YOUR_USER_ID",
        "CODECKS_DEFAULT_PROJECT": "My Project"
      }
    }
  }
}

You can run a Codecks MCP Server to let AI assistants interact with Codecks project management. It enables querying cards, creating tasks, updating statuses, and managing spaces, decks, and projects from MCP-compatible tools. This guide shows how to install, configure, and use the server end to streamline your game development workflow with AI assistants like Claude.

How to use

You will run a local MCP server and connect it to your MCP client. The server exposes a set of functions that let you list, search, create, update, move, and archive cards; manage decks, spaces, and projects; and filter results by project or other attributes. In practice, you can ask your AI assistant to show items in a backlog, create new tasks from your conversational prompts, move cards between decks, or mark work as complete. The client will invoke the server’s tools using the provided command configuration, and the server will respond with structured data you can present in your workflow.

How to install

Prerequisites you need before installation:

  • Node.js v18 or later

  • A Codecks account with an organization

Step-by-step setup you should follow:

This process installs dependencies and creates your .env configuration file. You will use this file to store your Codecks token, URL, and user ID.

Available tools

codecks_list_cards

List all cards with optional filters for deck, project, and status.

codecks_search_cards

Search cards by title or content.

codecks_get_card

Retrieve a card by its ID.

codecks_create_card

Create a new card in a specified deck.

codecks_update_card

Update the content of an existing card.

codecks_move_card

Move a card to a different deck.

codecks_complete_card

Mark a card as complete or incomplete.

codecks_archive_card

Archive a card for historical reference.

codecks_unarchive_card

Unarchive a card to make it visible again.

codecks_list_decks

List all decks in a project with card counts and space information.

codecks_create_deck

Create a new deck, optionally within a specific space.

codecks_update_deck

Rename a deck.

codecks_list_spaces

List all spaces in a project.

codecks_create_space

Create a new space (deck container).

codecks_rename_space

Rename a space.

codecks_delete_space

Delete a space (cannot delete the default space).

codecks_list_projects

List all projects within your organization.

codecks_create_project

Create a new project.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational