Connecting

Zeeb MCP works with any client that supports the Model Context Protocol. Below are setup instructions for the most common clients.

MCP server details

The key you connect with is bound to one project, so the connection operates on that project — you never pass a project id to a tool.

---

Claude Desktop

Claude Desktop supports MCP natively since version 0.10.

Setup

1. Open the config file:

   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
   • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add the Zeeb server:

{
  "mcpServers": {
    "zeeb": {
      "url": "https://mcp.zeeb.cloud/mcp/mcp",
      "headers": {
        "Authorization": "Bearer zb_your_key_here"
      }
    }
  }
}

1. Restart Claude Desktop.

2. Open a new conversation — you should see Zeeb tools available in the tool picker (hammer icon).

---

Cursor

Cursor supports MCP servers through its settings panel.

Setup

1. Open Cursor → Settings → Cursor Settings
2. Navigate to the MCP tab
3. Click Add new MCP server and enter:
   • Name: zeeb
   • URL: https://mcp.zeeb.cloud/mcp/mcp
4. Add the authorization header:

{
  "zeeb": {
    "url": "https://mcp.zeeb.cloud/mcp/mcp",
    "headers": {
      "Authorization": "Bearer zb_your_key_here"
    }
  }
}

1. Save and reload. Zeeb tools will be available in the Cursor Agent.

---

Lovable

Lovable supports MCP servers through OAuth. Direct bearer token auth is not supported in Lovable.

Setup

1. In Lovable, open Settings → Integrations → MCP Servers
2. Add a new server with URL: https://mcp.zeeb.cloud/mcp/mcp
3. Lovable will detect the OAuth endpoint automatically and prompt you to authorize
4. You'll be redirected to Zeeb's authorization page — enter a project-scoped Zeeb API key (the key determines the project)
5. Once authorized, Lovable can use all Zeeb tools on that project

---

Any MCP-compatible client

For any other client that supports the MCP specification:

• Server URL: https://mcp.zeeb.cloud/mcp/mcp
• Transport: Streamable HTTP (POST to /mcp/mcp)
• Auth header: Authorization: Bearer zb_your_key_here
• OAuth discovery: https://mcp.zeeb.cloud/.well-known/oauth-authorization-server

Verify the connection

Once connected, call list_available_tools to see all available Zeeb tools and verify the connection is working.

---

Troubleshooting

Tool error format

When a tool call fails, the error text carries a machine-readable code in brackets:

JOB_FAILED[<error_code>]: <message> (did you mean: <suggestions>?)

<error_code> comes from a closed vocabulary (app_not_found, model_not_found, already_exists, invalid_field_spec, invalid_permission, invalid_input, …), so clients and agents can parse the bracketed code and react programmatically. Where possible, the message includes did you mean suggestions (e.g. close matches for a misspelled app or model name).