Cursor & Other Clients

Any client that supports remote (Streamable HTTP) MCP servers with custom headers can connect directly.

Cursor

Add to .cursor/mcp.json (project) or your global Cursor MCP settings:

{
  "mcpServers": {
    "zingasuite": {
      "url": "https://mcp.zingasuite.com/mcp",
      "headers": { "Authorization": "Bearer zk_live_YOUR_KEY" }
    }
  }
}

Reload Cursor; the Zingasuite tools become available to the agent.

Generic Streamable-HTTP clients

For any MCP-capable client or SDK, use:

Transport: Streamable HTTP
URL: https://mcp.zingasuite.com/mcp
Header: Authorization: Bearer <your zk_ key>

The server is stateless per request, so no session bootstrapping beyond the standard MCP initialize handshake is required.

Clients that only support stdio

If your client can only launch a local command (not call a remote URL), use the @zingasuite/mcp bridge the same way as Claude Desktop.

Building your own agent

Point your MCP client library at the URL above with the auth header. Start from the zinga://entity/profile resource to discover the entity and your key's scopes, then call tools. For non-MCP integrations, the same capabilities are on the REST API, described by a machine-readable spec at https://api-v1.zingasuite.com/papi/v1/openapi.json.