Skip to content

clients.md

Latest commit

 

History

History
137 lines (110 loc) · 4.23 KB

clients.md

File metadata and controls

137 lines (110 loc) · 4.23 KB
Raw

MCP Client Integration Notes

This document supplements the CLI installers documented in the README. Each section outlines discovery paths, schema nuances, and post-installation tips.

Tip: Run npx @pv-bhat/vibe-check-mcp --list-clients to see a quick summary of every supported integration.

For supported providers, secret resolution, and storage guidance, read API Keys & Secret Management. The notes below cover only client-specific requirements and edge cases.

Claude Desktop

  • Config path: claude_desktop_config.json (auto-detected per platform).
  • Schema: mcpServers map keyed by server ID.
  • Default transport: stdio (npx -y @pv-bhat/vibe-check-mcp start --stdio).
  • API keys: Requires ANTHROPIC_API_KEY.
  • Restart: Quit and relaunch Claude Desktop after installation.
{
  "mcpServers": {
    "vibe-check-mcp": {
      "command": "npx",
      "args": ["-y", "@pv-bhat/vibe-check-mcp", "start", "--stdio"],
      "env": {},
      "managedBy": "vibe-check-mcp-cli"
    }
  }
}

Docs: Claude Desktop MCP

Claude Code

  • Config path: ~/.config/Claude/claude_code_config.json (auto-detected per platform).
  • Schema: Claude-style mcpServers map.
  • Default transport: stdio (npx -y @pv-bhat/vibe-check-mcp start --stdio).
  • API keys: Requires ANTHROPIC_API_KEY.
  • Bootstrap: Run claude code login or any Claude Code command once to scaffold the config file.
{
  "mcpServers": {
    "vibe-check-mcp": {
      "command": "npx",
      "args": ["-y", "@pv-bhat/vibe-check-mcp", "start", "--stdio"],
      "env": {},
      "managedBy": "vibe-check-mcp-cli"
    }
  }
}

Docs: Claude Code MCP integration

Cursor

  • Config path: ~/.cursor/mcp.json (override with --config if needed).
  • Schema: Claude-style mcpServers map.
  • Fallback: When the config file is missing, the CLI prints a JSON snippet suitable for Cursor's MCP settings UI.
{
  "mcpServers": {
    "vibe-check-mcp": {
      "command": "npx",
      "args": ["-y", "@pv-bhat/vibe-check-mcp", "start", "--stdio"],
      "env": {},
      "managedBy": "vibe-check-mcp-cli"
    }
  }
}

Reference: Cursor community thread on MCP

Windsurf (Cascade)

  • Config paths: legacy ~/.codeium/windsurf/mcp_config.json, new builds ~/.codeium/mcp_config.json.
  • Transports: stdio by default; HTTP uses serverUrl.
  • Restart: Close and reopen Windsurf to reload MCP servers.
// stdio
{
  "mcpServers": {
    "vibe-check-mcp": {
      "command": "npx",
      "args": ["-y", "@pv-bhat/vibe-check-mcp", "start", "--stdio"],
      "env": {},
      "managedBy": "vibe-check-mcp-cli"
    }
  }
}

// http
{
  "mcpServers": {
    "vibe-check-mcp": {
      "serverUrl": "http://127.0.0.1:2091",
      "managedBy": "vibe-check-mcp-cli"
    }
  }
}

Docs: Codeium Windsurf MCP guide

Visual Studio Code

  • Workspace config: .vscode/mcp.json (profiles use the VS Code user data dir).
  • Transports: stdio (transport: "stdio") or HTTP (url + transport: "http").
  • CLI tips: Provide --config to target a workspace file. Without it, the CLI prints a JSON snippet plus a vscode:mcp/install?... quick-install link.
  • Dev helpers: --dev-watch sets dev.watch=true; --dev-debug <value> populates dev.debug.
{
  "servers": {
    "vibe-check-mcp": {
      "command": "npx",
      "args": ["-y", "@pv-bhat/vibe-check-mcp", "start", "--stdio"],
      "env": {},
      "transport": "stdio",
      "managedBy": "vibe-check-mcp-cli"
    }
  }
}

Docs:

JetBrains (future)

JetBrains AI Assistant already consumes Claude-style MCP configs over stdio. Import from Claude or point it at the same command once JetBrains exposes MCP import hooks publicly.

Docs: JetBrains AI Assistant MCP