Connection setup

Every client connects to the same hosted server:

https://api.citeladder.com/mcp

The connection uses browser sign-in (OAuth) with the read scope citeladder:read, plus citeladder:write when you tick Allow changes on the consent page. Do not paste a provider API key or a CiteLadder session cookie into the client.

The quickest route is the Connect button in the CiteLadder app under Settings → MCP connections, or on the MCP product page. Selecting it opens Claude with CiteLadder’s name and URL filled in. Hover over it to choose ChatGPT, Gemini or Grok instead; CiteLadder copies the URL for you to paste there. The steps below cover the same setup by hand.

Client menus change between versions and plans. If a label differs, look for the client’s custom connector or remote MCP server setting; the URL and sign-in flow stay the same.

Add CiteLadder to your client

Claude

1. In Claude, open Customize → Connectors and choose Add custom connector. The Connect button opens this dialog with the name and URL filled in.
2. Confirm the name CiteLadder and the URL, then add it.
3. Select Connect and sign in to CiteLadder.

On Team and Enterprise plans, an owner may need to add the connector in admin settings before members can connect.

ChatGPT

1. Open chatgpt.com/plugins and select +.
2. Choose the option to add a custom MCP server.
3. Enter the name CiteLadder and the URL, and choose OAuth for authentication.
4. Acknowledge the custom server warning and select Create, then sign in to CiteLadder.

Depending on your plan, you may need to turn on developer mode first. Workspace admins can block custom servers.

Gemini

1. Open gemini.google.com/apps, then go to Settings → Connected Apps → Custom apps.
2. Choose Add a custom app, paste the URL and select Next.
3. Approve the sign-in to CiteLadder.

Google currently limits custom apps to some accounts and regions.

Cursor

Add the server to ~/.cursor/mcp.json, then sign in to CiteLadder when Cursor prompts you:

{
  "mcpServers": {
    "citeladder": { "url": "https://api.citeladder.com/mcp" }
  }
}

Grok

1. Open grok.com/connectors and select New Connector → Custom.
2. Paste the URL and sign in to CiteLadder.

On Business and Enterprise plans, an admin may need to enable connectors first.

Claude Code

Add the server, then run /mcp inside Claude Code to sign in:

claude mcp add --transport http citeladder https://api.citeladder.com/mcp

Codex

Add the server to ~/.codex/config.toml:

[mcp_servers.citeladder]
url = "https://api.citeladder.com/mcp"

Then sign in:

codex mcp login citeladder

Other clients

Any client that supports remote MCP servers with browser sign-in can connect. Add a remote (Streamable HTTP) server with the URL above and choose OAuth if the client asks for an authentication method.

Approve workspace access

Every client finishes in the same browser consent step:

1. Sign in to CiteLadder. If you do not have an account, create one; a new account gets a trial workspace. Finish project setup and you return to the approval page.
2. Select the workspaces this connection may use.
3. Leave Allow changes unticked for read-only access, or tick it to let the assistant make changes you confirm. Then select Approve.

The connection uses only the workspaces you selected. Joining another workspace later does not add it; connect again to share it. Losing membership of a selected workspace removes access to it.

The approval page explains any workspace you cannot select. A workspace whose trial or subscription has ended links to billing, and one without the current Terms acceptance can be approved once you accept the Terms on the page.

How long a connection lasts

The client renews its sign-in as you use it. A connection left unused for 30 days, or 180 days after approval however often it is used, asks you to sign in and approve again. You can end it sooner by revoking it.

Check the connection

Send a minimal request first:

List the CiteLadder projects I can access. Do not analyze them or run anything yet.

If the project list works, choose one project and ask:

For the project I choose, list the saved datasets that are available.
Include their observation dates, scope, coverage and limitations.
Do not refresh, acquire or change anything.

This separates a working connection from a missing dataset.

Begin a focused read

Ask for one audit, date window or saved dataset rather than everything at once. Follow the returned pagination cursors when you need more rows.

For exact query evidence, use an available saved window. A missing requested window does not silently fall back to a nearby period.

If authorization fails

Confirm the signed-in account and that your client supports remote MCP with browser sign-in. Restart authorization when a request is denied or expired.

If a project is absent, check that its workspace was selected at approval and that you are still a member. See Access and troubleshooting.