Connect your agent to Cadensia.

Connect in 3 steps

From zero to tools/list.

1. 1

   Create an API token

   Tokens are per account and scoped. In the dashboard at /api_tokens, mint a token and copy the secret — it is shown once. Store it in your client's secret manager.

   Log in to create a token

   Token creation happens in the dashboard — after you log in you will find it at /api_tokens.

2. 2

   Add the server to your MCP client

   Add a Streamable HTTP server entry. The generic JSON shape below uses the http transport; the Authorization header carries your token as a Bearer credential.

   {
     "mcpServers": {
       "cadensia": {
         "type": "http",
         "url": "https://cadensiastudio.com/mcp",
         "headers": {
           "Authorization": "Bearer YOUR_API_TOKEN"
         }
       }
     }
   }

   The same entry is the Claude Desktop / Cursor variant — put it in the client's MCP config file (claude_desktop_config.json for Claude Desktop, .cursor/mcp.json for Cursor):

   {
     "mcpServers": {
       "cadensia": {
         "type": "http",
         "url": "https://cadensiastudio.com/mcp",
         "headers": {
           "Authorization": "Bearer YOUR_API_TOKEN"
         }
       }
     }
   }

   Replace YOUR_API_TOKEN with the secret from step 1. Keep the token out of source control.

3. 3

   Verify the connection

   The MCP Inspector runs one method and disconnects. Point it at the hosted endpoint and list the tools:

   npx --yes @modelcontextprotocol/inspector --cli https://cadensiastudio.com/mcp --transport http --header "Authorization: Bearer $CADENSIA_API_TOKEN" --method tools/list

   A valid token returns the fifteen tools. A missing or invalid token returns an HTTP 401, and the Inspector CLI exits with code 3.

Agents can self-serve

Create an account, then discover and buy.

An agent with no account can create one over the API, then use the tools it unlocks. Sign-up, catalog discovery, and checkout are all Bearer-token operations:

1. POST /api/v1/registrations

   Create an account and receive a restricted, scoped API token — the secret is returned once. Requires accepting the terms.

2. GET /api/v1/catalog

   List the purchasable plans, credit packs, and one-time SKUs (billing:read).

3. POST /api/v1/checkouts

   Start a checkout for a plan, credit pack, or one-time SKU (billing:write); payment completes with Stripe.

Every request is scoped to the account behind the token. See the pricing page for what's available.

Auth & security

Token-scoped, account-scoped.