> ## Documentation Index
> Fetch the complete documentation index at: https://cadenya.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP server

> Connect an MCP client to https://mcp.cadenya.com/mcp, sign in with your Cadenya account or send an API key as a bearer token, and manage Agents, Tool Sets, and objectives through three tools.

Cadenya's MCP server hands an MCP client, such as Claude Code, the Cadenya API as three tools. Ask it to list your Agents, create a Tool Set from an OpenAPI URL, or approve a waiting tool call. It finds the right operation first, then runs it.

The server lives at:

```text theme={null}
https://mcp.cadenya.com/mcp
```

It speaks MCP `2026-07-28`, the stateless revision of the protocol, over streamable HTTP. **It speaks only that revision, so clients that support only older ones can't connect.**

## Tools

Three tools cover every operation:

| Tool | What it does |
| - | - |
| `cadenya_discover` | Finds operations for Agents, variations, Tool Sets, tools, memory layers and entries, objectives, Widgets, and workspaces. Pass `query` to search, or `operation` to get one operation's input schema and an example. Results come eight at a time, and `offset` pages through them. |
| `cadenya_read` | Runs a read operation. Workspace resources take an explicit `workspaceId`, and lists return one page. |
| `cadenya_write` | Runs a create, update, or delete, including Continue and tool call approvals and denials. |

Every call to `cadenya_read` and `cadenya_write` takes an `operation` name from `cadenya_discover` and an `input` object. Discover lists only the operations your credential can run, so the client never finds a door it can't open.

## Sign in with your Cadenya account

The server signs clients in with OAuth, and app.cadenya.com is the authorization server. Clients that support client ID metadata documents need no setup: add the URL, approve the sign-in in your browser, and pick the workspaces the client can reach.

With Claude Code:

```bash theme={null}
claude mcp add --transport http cadenya https://mcp.cadenya.com/mcp
claude mcp login cadenya
```

`claude mcp login` opens the sign-in page in your browser. Inside a session, `/mcp` does the same.

Building your own client? Here are the details:

| Setting | Value |
| - | - |
| Protected resource | `https://mcp.cadenya.com/mcp` |
| Authorization server | `https://app.cadenya.com` |
| Scope | `cadenya:manage` |
| PKCE | `S256` |
| Client registration | Client ID metadata documents (dynamic client registration isn't supported) |

## Send an API key instead

A script, or a client without that sign-in flow, can send an [API key](https://cadenya.com/docs/api-keys.md) as a bearer token. The key's workspaces and scopes still apply.

In a project's `.mcp.json`, Claude Code reads the key from the environment. So the file never holds the key, and you can commit it:

```json .mcp.json theme={null}
{
  "mcpServers": {
    "cadenya": {
      "type": "http",
      "url": "https://mcp.cadenya.com/mcp",
      "headers": { "Authorization": "Bearer ${CADENYA_API_KEY}" }
    }
  }
}
```

**Any client that speaks MCP `2026-07-28` connects the same way: the URL, plus a browser sign-in or an `Authorization: Bearer` header.**

Want the setup in your repository, behind code review? Use [config files](https://cadenya.com/docs/config-files.md) instead.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.