@cocaxcode/suite-mcp

One command. Five MCP servers. Any AI tool.
Install 100+ tools into your AI coding assistant in under 10 seconds.

What's included · Quick start · Usage · Supported AI tools · Boundaries · Architecture

An interactive CLI installer that configures all five cocaxcode MCP servers in your AI tool of choice. It auto-detects your tool, lets you pick which MCPs to add, and writes directly to your user-level global config — merging with your existing setup, never overwriting it.

npx @cocaxcode/suite-mcp install

What's included

Each MCP is independently published on npm and works standalone. suite-mcp simply wires them all up at once.

Quick start

npx @cocaxcode/suite-mcp install

The CLI detects your AI tool, shows available MCPs, and writes the config. Done.

To install everything without prompts:

npx @cocaxcode/suite-mcp install --all

Usage

Install

# Interactive — pick which MCPs to add
npx @cocaxcode/suite-mcp install

# All MCPs, no prompts
npx @cocaxcode/suite-mcp install --all

# Target a specific AI tool
npx @cocaxcode/suite-mcp install --target cursor
npx @cocaxcode/suite-mcp install --target gemini --all

Note: Already-installed MCPs are skipped automatically. Only missing ones get added.

List status

npx @cocaxcode/suite-mcp list

@cocaxcode/suite-mcp — Available MCPs (claude)

  Status  MCP                   Description
  ✓       api-testing           API testing with collections, assertions, and flows
  ✓       database              PostgreSQL, MySQL, and SQLite management
  ✓       devflow               Jira + GitHub/GitLab workflow automation
  ✗       logbook               Developer logbook with notes and TODOs
  ✗       ai-context-inspector  AI ecosystem scanner and migrator

  3/5 installed

Remove

npx @cocaxcode/suite-mcp remove

Shows only installed MCPs and lets you choose which to remove. Empty selection cancels.

Command reference

Supported AI tools

suite-mcp auto-detects your tool by scanning for marker files in the working directory, then installs MCPs into your user-level global config so they are available in every project.

Tip: If no tool is detected, the CLI prompts you to choose one. Use --target to skip detection entirely.

What it does NOT do

• Does not run MCP servers. It only writes config files. Each MCP runs via npx at invocation time.
• Does not manage versions. MCPs install with @latest. Re-run install to pick up updates.
• Does not bundle MCPs together. Each server stays independent with its own lifecycle and data.
• Does not touch non-cocaxcode entries. Your existing MCP configs are preserved — merge, never overwrite.

Architecture

src/
├── index.ts       # CLI entry point and arg parsing
├── types.ts       # TypeScript interfaces
├── registry.ts    # MCP catalog (add new MCPs here)
├── config.ts      # Config read/write with atomic operations
├── detect.ts      # AI tool auto-detection via marker files
├── prompts.ts     # Interactive readline prompts
├── install.ts     # Install subcommand
├── remove.ts      # Remove subcommand
├── list.ts        # List subcommand
└── __tests__/     # 52 tests across 5 suites

• Zero runtime dependencies — uses only Node.js built-ins (readline, fs, crypto, path, os)
• Atomic writes — write to temp file, then rename, preventing config corruption on crash
• Path traversal protection — all file paths are validated to stay within the user's home directory or working directory
• Merge, never overwrite — existing MCP entries from other sources are always preserved
• 52 tests — config I/O, detection logic, parsing, and security edge cases

Stack: TypeScript · ESM · tsup · Vitest · Node >= 20

MIT · Built by cocaxcode