Koskamo

CiteLadder MCP

An official MCP server that allows AI assistants to access CiteLadder's AI visibility data, including brand mentions, cited sources, site health, and search performance. It enables agents to read visibility results, trends, and perception data from dated records, and with user approval, to manage prompts, competitors, and audits.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

CiteLadder MCP logo, by CiteLadderVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-10-26Operated by CiteLadder
You need:A CiteLadder workspace with an active trial or subscription, and a project for the assistant to read.Sign in to CiteLadder, choose which workspaces the assistant may use and whether it may make changes.
MCP endpoint (Streamable HTTP)
https://api.citeladder.com/mcp
Vendor documentation

What you can do with it

  • Ask questions grounded in recorded AI visibility evidence
  • Read visibility results, trends, and cited sources
  • Prepare briefs and fix lists from site health crawls
  • Manage prompts and track competitors with user approval

Source and maintenance

Vendor evidenceRegistry 1.0.1

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · registry · passed · metadata changed · Source metadata updated
  • · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http citeladder-mcp https://api.citeladder.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add citeladder-mcp --url https://api.citeladder.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable citeladder-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "citeladder-mcp": {
      "url": "https://api.citeladder.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "citeladder-mcp": {
      "type": "streamableHttp",
      "url": "https://api.citeladder.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start citeladder-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "citeladder-mcp": {
      "type": "http",
      "url": "https://api.citeladder.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http citeladder-mcp https://api.citeladder.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "citeladder-mcp": {
      "url": "https://api.citeladder.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "citeladder-mcp": {
      "serverUrl": "https://api.citeladder.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like CiteLadder MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run CiteLadder MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing