CLAUDE DESKTOP CONNECTOR SETUP
Comprehensive guidelines for AI-assisted development within the Editor platform
Claude Desktop Custom Connector Setup
Session: 79 | Last Updated: February 1, 2026
Overview
Claude Desktop now supports Custom Connectors (Beta) that enable native MCP tool integration over HTTP. This allows Claude Desktop (Cowork) to connect directly to our GoGrab AI backend and use all 79+ MCP tools without browser automation.
Quick Setup
1. Start the Backend
cd apis/backend-ai-api
yarn start:dev
# or
npm run start:dev
Backend runs on port 3000 (or 3001 depending on config).
2. Add Custom Connector in Claude Desktop
- Open Claude Desktop
- Go to Settings → Connectors
- Click "Add custom connector"
- Configure:
- Name:
GoGrab AI - URL:
http://localhost:3000/ai-api/mcp - Advanced Settings: (leave default for local)
- Name:
3. Verify Connection
After adding, Claude Desktop should:
- Send
initializerequest - Request
tools/list - Display 79+ tools in the tool picker
Endpoints
Main JSON-RPC Endpoint
URL: POST /ai-api/mcp or POST /ai-api/mcp/jsonrpc
All MCP protocol messages go through this endpoint.
Server-Sent Events (SSE)
URL: GET /ai-api/mcp/events?agentId=xxx
For real-time notifications (handoff completion, etc.)
MCP Protocol Methods
| Method | Description |
|---|---|
initialize |
Setup session, register as agent, get capabilities |
tools/list |
Get all 79+ available tools |
tools/call |
Execute a specific tool |
resources/list |
List resources (empty for now) |
prompts/list |
List prompts (empty for now) |
ping |
Health check |
Tool Categories (79 Tools)
| Category | Count | Examples |
|---|---|---|
| Core Intelligence | 4 | preflight, log_decision, find_similar |
| Session Management | 10 | set_session, get_session_info |
| Multi-Agent | 12 | create_handoff, send_agent_message |
| Conventions & Learning | 16 | get_conventions, report_outcome |
| Code Intelligence | 10 | generate_module, analyze_code |
| Browser Automation | 9 | browser_navigate, browser_screenshot |
| Desktop Connectivity | 7 | desktop_read_file, desktop_execute |
| Task Runner | 6 | workflow_create, task_execute |
| Testing | 4 | test_run, test_coverage |
| Handoff (NEW) | 3 | check_handoffs, accept_handoff, complete_handoff |
Handoff Tools (Session 79)
These tools enable Cowork to participate in the multi-agent handoff system:
check_handoffs
Check for pending handoffs assigned to you.
{
"method": "tools/call",
"params": {
"name": "check_handoffs",
"arguments": {
"agentId": "cowork-claude-desktop-xxx",
"workspace": "editor2"
}
}
}
accept_handoff
Accept a handoff before starting work.
{
"method": "tools/call",
"params": {
"name": "accept_handoff",
"arguments": {
"handoffId": "handoff-123",
"agentId": "cowork-claude-desktop-xxx"
}
}
}
complete_handoff
Mark a handoff as complete with results.
{
"method": "tools/call",
"params": {
"name": "complete_handoff",
"arguments": {
"handoffId": "handoff-123",
"agentId": "cowork-claude-desktop-xxx",
"response": "Tested login flow successfully. All 5 test cases passed."
}
}
}
Authentication
Local Development
No authentication required for localhost connections.
Production
Use API key authentication:
POST /ai-api/mcp
X-MCP-API-Key: mcp_your_api_key
X-MCP-Project-Id: your-project-id
Recommended Workflow
- Initialize: Claude Desktop auto-registers as a Cowork agent
- Preflight: Call
preflightbefore any task to get context - Check Handoffs: Periodically call
check_handoffsduring idle time - Accept: When you get a handoff, call
accept_handoff - Work: Complete the assigned tasks
- Complete: Call
complete_handoffwith results - Log: Use
log_decisionfor important decisions
Troubleshooting
"Connection refused"
- Ensure backend is running:
yarn start:dev - Check port (3000 or 3001)
- Verify URL format:
http://localhost:3000/ai-api/mcp
"Tools not discovered"
- Check Claude Desktop logs for error details
- Verify
/tools/listreturns tools via curl:curl -X POST http://localhost:3000/ai-api/mcp/jsonrpc \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'
"Agent not registered"
- Check backend logs for registration errors
- Verify AgentService is available in module
Protocol Reference
Request Format (JSON-RPC 2.0)
{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "preflight",
"arguments": {
"task": "Analyze authentication flow"
}
},
"id": 1
}
Response Format
Success:
{
"jsonrpc": "2.0",
"result": {
"content": [
{
"type": "text",
"text": "..."
}
]
},
"id": 1
}
Error:
{
"jsonrpc": "2.0",
"error": {
"code": -32602,
"message": "Missing required parameter: name"
},
"id": 1
}
Related Documentation
Session 79 - Claude Desktop Connector Integration