Connect a client

Add https://mcp.cademi.dev/mcp to your MCP client as a remote server and authorize it by signing in to Cademí. You never paste an API key or a token.

Any MCP client

Your client needs to support remote MCP servers over the Streamable HTTP transport, with OAuth authorization.

Setting	Value
Server URL	`https://mcp.cademi.dev/mcp`
Transport	Streamable HTTP
Authentication	OAuth. Leave any API key or header field empty.

The server is an OAuth protected resource. The first request without an authorization returns 401 with a WWW-Authenticate header that points to the server's protected resource metadata, and that document names the Cademí authorization server. A client that implements MCP authorization follows this chain on its own and opens the Cademí authorization page in your browser. What happens on that page is described in Authorization and permissions. The administrator who approves the connection needs two-factor authentication turned on.

The server keeps no session between requests, and each connection works on one account.

Claude

In Claude on the web or in the desktop app:

Open Settings, then Connectors.
Choose Add custom connector.
Paste https://mcp.cademi.dev/mcp as the URL and add the connector.
Choose Connect. The Cademí authorization page opens.
Choose your account, sign in as an administrator of that account, and approve the connection.

Back in Claude, the connector shows as connected and its tools are available in your conversations.

Claude Code

Claude Code is tested end to end with Cademí MCP: OAuth sign-in, read tools such as the product list and the full structure of a course, and calls recorded under the administrator who approved the connection.

Add the server:

claude mcp add --transport http cademi https://mcp.cademi.dev/mcp

Then, inside Claude Code, run:

/mcp

Select cademi and authenticate. The Cademí authorization page opens in your browser: choose your account, sign in as an administrator, and approve the connection.

With the cademi CLI

If you have the cademi CLI, one command adds the server to your coding assistant:

cademi mcp install claude

Replace claude with the name of your client:

Client	Name
Claude Code	`claude`
Codex	`codex`
Cursor	`cursor`
VS Code	`vscode`
GitHub Copilot CLI	`copilot`
Gemini CLI	`gemini`
OpenCode	`opencode`

For Copilot inside VS Code, use vscode.

Claude Code and Codex are configured through their own CLIs. If that CLI is not installed, the command prints the one to run yourself. The other clients get a cademi entry in their configuration file, and the servers already there are kept. If the file is not plain JSON, for example because it has comments, the command leaves it unchanged and prints the entry for you to add.

By default, the server is added for your user, in every project. Add --project to add it to the current project only. Codex and GitHub Copilot CLI have no project-level configuration and reject --project. If the client already has a cademi server with a different URL, the command replaces it only when you pass --force.

Then sign in to Cademí. Codex opens the Cademí authorization page during the install. For the other clients, the command prints how to start the sign-in from that client.

Check the connection

Ask the assistant which account it is connected to:

Which Cademí account am I connected to?

The assistant answers with the account, its environment (production or sandbox), and the administrator the connection acts as.

If a tool returns AUTHENTICATION_REQUIRED, the authorization is no longer valid. Connect again from your client: Connect on the connector in Claude, or /mcp in Claude Code. See Errors and limits.