Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tryordinal.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Why migrate?

The old MCP server at https://app.tryordinal.com/api/mcp used a workspace API key that you pasted into your assistant’s config. It’s been replaced by the new server at https://app.tryordinal.com/mcp, which signs you in with OAuth — no key-pasting, and you can reach every workspace you belong to from one connection.
Remove the old server first. If you leave both servers installed, your assistant sees duplicate tool names (e.g. two versions of create_post) and may pick the wrong one or refuse to run either. Always delete the old entry before installing the new one.

​
Step 1 — Remove the old server

Pick your client below.
The old Ordinal server was installed as a local MCP server in Claude Desktop, configured via claude_desktop_config.json. Remove it like this:
1

Open Claude Desktop settings

Press Cmd + , (Mac) or Ctrl + , (Windows).
2

Go to Developer

In the sidebar under Desktop app, click Developer.
3

Edit Config

Click Edit Config, then Open File to open claude_desktop_config.json in your editor.
4

Remove the ordinal entry

Find the "ordinal" block under mcpServers and delete it. It looks like this:
{
  "mcpServers": {
    "ordinal": {
      "command": "npx",
      "args": [
        "mcp-remote@latest",
        "https://app.tryordinal.com/api/mcp",
        "--header",
        "Authorization:Bearer ord_XXXXXXXX"
      ]
    }
  }
}
Save the file. If ordinal was the only entry, leave "mcpServers": {}.
5

Restart Claude Desktop

Fully quit and relaunch. In Settings → Developer, the Ordinal entry should be gone from Local MCP servers.

​
Step 2 — (Optional) Revoke the old API key

Since the old server used a workspace API key, revoke it so it can’t be used again:
1

Open API Keys

Go to Settings → Integrations → API Keys in your workspace.
2

Revoke the key

Find the key you used for MCP, click the ... menu, and select Revoke. This is permanent and immediate.
You can skip this step if the same API key is still used for something else (for example, the REST API). The old MCP server will stop accepting requests regardless.

​
Step 3 — Install the new server

Follow the install guide for your client:

Claude

Via the Connectors UI

Claude Code

Via claude mcp add

Cursor

Via MCP settings

VS Code

Via .vscode/mcp.json

​
After migrating

The new server’s tools are named and organized differently. For example, the old server had separate create_post and update_post tools — the new server uses ordinal_create_post and ordinal_manage_post. See the full tools reference.
The old API key was tied to a single workspace. The new server signs you in as a user, so every tool call takes a workspaceSlug argument. Call ordinal_get_workspace_context with no arguments to list your workspaces and get the slug.
You probably didn’t fully restart the client, or the old entry is still in config. Double-check the config file, fully quit the app (not just close the window), and relaunch.