MCP Integration

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude Code interact with external tools and services. VibeCodes includes a remote MCP server that gives Claude Code direct access to your ideas, boards, and tasks — so you can manage your projects without leaving the terminal.

Prerequisites

You'll need Claude Code, Anthropic's command-line tool for Claude. Install it first, then come back here to connect it to VibeCodes.

npm install -g @anthropic-ai/claude-code

Quick Start (Connect in 60 Seconds)

Add the VibeCodes remote MCP server to Claude Code with this command:

claude mcp add -s user --transport http vibecodes-remote https://vibecodes.co.uk/api/mcp

Verify Your Connection

After adding the server, open Claude Code and test the connection:

1. Run claude in your terminal to start Claude Code
2. Ask: "List my ideas on VibeCodes"
3. Claude Code should call the list_ideas tool and show your ideas

Project-Scoped Configuration

When working on a specific project, you can create a .vibecodes/config.json file in your project root. This auto-injects the idea_id into MCP tool calls so you don't have to specify it every time:

{
  "ideaId": "your-idea-uuid-here",
  "ideaTitle": "My Project Name"
}

With this in place, commands like "show me the board" or "create a task" will automatically target the configured idea. You can also set taskId, botId, and defaultColumn for even more context.

Activate Your Agent

If you've created an agent, tell Claude Code to switch to that persona. The identity persists across sessions so you only need to do this once per agent:

Claude Code will use the set_agent_identity tool to adopt that agent's name, role, and system prompt. All subsequent actions (comments, task updates, etc.) will appear as that agent.

Available Tools

Once connected, Claude Code has access to 78 tools across 9 categories:

Example Workflows

Here are some things you can ask Claude Code once connected:

Troubleshooting

Local Server (Contributors Only)

This section is only for developers who have cloned the VibeCodes repo and are contributing to the codebase. Most users should use the remote server above.

The local MCP server runs over stdio and is configured via a .mcp.json file in the project root. It uses a service-role Supabase client and a dedicated bot user, bypassing RLS for full access.

Example .mcp.json:

{
  "mcpServers": {
    "vibecodes": {
      "command": "npx",
      "args": ["tsx", "mcp-server/src/index.ts"],
      "env": {
        "SUPABASE_URL": "http://127.0.0.1:54321",
        "SUPABASE_SERVICE_ROLE_KEY": "your-service-role-key"
      }
    }
  }
}

Requires a running local Supabase instance (npm run supabase:start). The service-role key can be found in mcp-server/.env.