Configure your MCP client to connect to the Sella server

Sella exposes a single endpoint for agents: POST https://sellag.vercel.app/api/mcp. It speaks JSON-RPC 2.0 and the Model Context Protocol. Connect once and all nine tools appear in your agent — covering discovery, evaluation, purchase, and compute in a unified interface.

Authentication model

Before wiring up your client, choose which authentication method fits your setup. Both are accepted by the MCP endpoint.

API key

Send Authorization: Bearer sk_live_… in the request header. Get a key from sella_auth_complete or the dashboard under Settings → Keys.

OAuth 2.0

Access tokens with the mcp:tools scope are also accepted, for clients that support OAuth flows natively.

The two auth tools — sella_auth_start and sella_auth_complete — are unauthenticated, so a fresh agent can bootstrap its own credentials without a key in place. Every other tool requires a valid key or OAuth token.

Claude Desktop

Open the Claude Desktop config file via Settings → Developer → Edit Config, then add the sella entry under mcpServers:

{
  "mcpServers": {
    "sella": {
      "type": "http",
      "url": "https://sellag.vercel.app/api/mcp",
      "headers": { "Authorization": "Bearer sk_live_your_key_here" }
    }
  }
}

{
  "mcpServers": {
    "sella": {
      "command": "npx",
      "args": ["-y", "@sella/mcp-client"],
      "env": {
        "SELLA_API_KEY": "sk_live_your_key_here",
        "SELLA_WALLET_CONFIG": "/Users/you/.sella-wallet.json"
      }
    }
  }
}

The @sella/mcp-client npx package is rolling out. Until it’s published, use the HTTP transport — it works today with every Claude Desktop version.

Restart Claude Desktop after saving. The Sella tools appear in your tool palette and Claude can invoke them in any conversation.

Cursor

Open Settings → MCP → Add new MCP server and configure an HTTP server:

URL: https://sellag.vercel.app/api/mcp
Header: Authorization: Bearer sk_live_your_key_here

Cursor lists all nine tools once the server connects successfully. You can verify by opening the MCP panel and checking that list_datasets appears.

Custom clients

Any HTTP client works — the MCP endpoint is plain JSON-RPC 2.0. Use these curl examples as a template for your own integration. List all available tools:

curl -s -X POST https://sellag.vercel.app/api/mcp \
  -H "Authorization: Bearer sk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }'

Call a tool by name:

curl -s -X POST https://sellag.vercel.app/api/mcp \
  -H "Authorization: Bearer sk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
        "jsonrpc": "2.0",
        "id": 2,
        "method": "tools/call",
        "params": { "name": "list_datasets", "arguments": { "limit": 5, "sort_by": "popular" } }
      }'

Batched JSON-RPC requests are supported — send an array of request objects to run several tool calls in one round trip and reduce latency for multi-step agent workflows.

Verify the connection

Run through these three checks after wiring up any client to confirm everything is working:

List tools

Send a tools/list call. The response should include nine tools, with list_datasets and get_dataset among them.

Make a free call

Call list_datasets with { "limit": 3 }. It should return catalogue items immediately, with no payment required.

Check auth

If any call returns 401, your key is missing or invalid. Re-run authentication to mint a fresh sk_live_ key, then update your config.

Get Started

Using the Marketplace

For Operators

Configure your MCP client to connect to the Sella server

Authentication model

API key

OAuth 2.0

Claude Desktop

Cursor

Custom clients

Verify the connection

Next steps

Authentication & wallets

MCP tool reference

​Authentication model

API key

OAuth 2.0

​Claude Desktop

​Cursor

​Custom clients

​Verify the connection

​Next steps

Authentication & wallets

MCP tool reference

Authentication model

Claude Desktop

Cursor

Custom clients

Verify the connection

Next steps