Skip to main content

​
Claude Code

Add to your ~/.claude.json: 
{
  "mcpServers": {
    "brik64": {
      "command": "brikc",
      "args": ["mcp-server"]
    }
  }
}
Or add at the project level in .claude/settings.json: 
{
  "mcpServers": {
    "brik64": {
      "command": "brikc",
      "args": ["mcp-server"]
    }
  }
}

​
Cursor

Add to your Cursor MCP settings (.cursor/mcp.json): 
{
  "mcpServers": {
    "brik64": {
      "command": "brikc",
      "args": ["mcp-server"]
    }
  }
}

​
Windsurf

Add to your Windsurf MCP configuration (~/.windsurf/mcp.json): 
{
  "mcpServers": {
    "brik64": {
      "command": "brikc",
      "args": ["mcp-server"]
    }
  }
}

​
With API Key

If you want the MCP server to authenticate with the registry, set the environment variable: 
{
  "mcpServers": {
    "brik64": {
      "command": "brikc",
      "args": ["mcp-server"],
      "env": {
        "BRIK64_API_KEY": "brik_live_xxx"
      }
    }
  }
}

​
Testing the Connection

After configuring, verify the MCP server is working: 
# Test manually
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | brikc mcp-server
Expected response includes brik64.discover and brik64.execute tools. In Claude Code, you can verify with: 
/mcp
This lists all connected MCP servers. You should see brik64 with 2 tools available.
The MCP server respects the same BRIK64_API_KEY environment variable used by the CLI. If you have already run brikc auth login, the MCP server will use the stored credentials automatically.