logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

chronos-integration-gateway

Interface with the Shortcut issue tracking system to retrieve details on initiatives, feature specifications, and goal alignments. This implementation strictly enforces read-only retrieval and the provisioning of novel records, ensuring zero destructive modification to existing artifacts.

Author

chronos-integration-gateway logo

zekus

No License

Quick Info

GitHub GitHub Stars 5
NPM Weekly Downloads 0
Tools 1
Last Updated 2026-02-19

Tags

shortcuttoolszekustools zekuszekus shortcutbusiness tools

Chronos Integration Gateway (Shortcut MCP Adapter)

[!ATTENTION] This service layer is currently under active development and its stability cannot be guaranteed.

An implementation of the Model Context Protocol (MCP) designed specifically for interfacing with the Shortcut platform (formerly known as Clubhouse).

Core Capabilities

  • Cataloging of organizational units, user stories, feature sets, and high-level objectives.
  • Facilitate sophisticated searching across all available user stories.
  • Provisioning new entries across stories, features, and objectives.
  • Rigorous adherence to safety protocols: only retrieval and creation are permitted; no modification or purging of established data.

Deployment Sequence

  1. Ensure Python environment is established via ASDF:

bash asdf install

  1. Prepare the isolated environment and load dependencies:

bash uv venv source .venv/bin/activate # Windows users: .venv\Scripts\activate uv pip install -e . # Install the package in development mode

  1. Configure operational parameters:

bash cp .env.example .env

Populate .env with your requisite Shortcut access credential (API Token)

  1. Initiate the service daemon:

bash python -m shortcut_mcp

Repository Layout

shortcut-mcp/ ├── src/ │ └── shortcut_mcp/ # Core package directory │ ├── init.py # Package bootstrapping file │ ├── main.py # Application entry point definition │ └── server.py # Logic for the network interface ├── pyproject.toml # Project metadata and dependency manifest ├── .tool-versions # Specifies required runtime versions via ASDF ├── .pylintrc # Configuration rules for static analysis └── README.md

Integration with Local Client

In your Claude Desktop settings file (claude_desktop_config.json), include the following stanza for server registration:

On macOS (~/Library/Application Support/Claude/claude_desktop_config.json):

{ "mcpServers": { "shortcut": { "command": "python", "args": ["-m", "shortcut_mcp"], "env": { "SHORTCUT_API_TOKEN": "your_token_here" } } } }

On Windows (%AppData%\Claude\claude_desktop_config.json):

{ "mcpServers": { "shortcut": { "command": "python", "args": ["-m", "shortcut_mcp"], "env": { "SHORTCUT_API_TOKEN": "your_token_here" } } } }

Verification Procedures

Testing the connection and functionality can be performed using the dedicated MCP Inspector utility:

bash npx @modelcontextprotocol/inspector python -m shortcut_mcp

Integrity Safeguards

This adapter enforces a highly restricted operational mode:

  • Only HTTP GET (data extraction) and POST (asset creation) verbs are permitted.
  • No mechanisms for updating existing records or permanent data removal are exposed.
  • All transactional activity is logged against the identity associated with the configured API credential.

Maintenance & Development Practices

Runtime Environment Configuration

This project standardizes on asdf for managing the Python runtime version, as defined in .tool-versions.

bash

Obtain the necessary Python version

asdf install python

The active environment will automatically align with project specification

Code Standard Enforcement

Static analysis is enforced using pylint. Execution command:

bash pylint src/shortcut_mcp

Configuration overrides for pylint are housed in the .pylintrc file.

See Also

`