Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.topograph.co/llms.txt

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

Company data is complex: 60+ countries, each with its own registers, identifiers, modes, and data quirks. The Topograph MCP plugs into your AI coding agent — Claude Code, Cursor, or any MCP-aware editor — so it pulls live coverage, pricing, and integration methodology on demand. Ask questions in plain English. Get grounded answers. Ship your integration in an afternoon.
Two commands and you’re in. In Claude Code:
/plugin marketplace add getsemaphore/topograph-mcp-library
/plugin install topograph@topograph
Sign in with Topograph the first time; the MCP runs against https://api.topograph.co/designer-mcp from there.

​
What you can ask

These prompts work today and call the right tools and rules under the hood:
Sample prompts
"Does France have UBO data? What about Italy and the UK?"

"How do I authenticate? Walk me through getting an API key
 and making my first call."

"What's the difference between onboarding mode and verification
 mode, and when do I use each?"

"What does Topograph cover in Germany for company + UBOs,
 and what response fields will I get back?"

"Write me a Node.js example that searches a French company,
 then fetches its profile with progressive results."

"How do I handle webhooks for /v2/company? Which event tells
 me a request is fully done?"

"I'm a fintech reselling Topograph KYB to my customers — how
 do I attribute usage per end-client for rebilling?"

"How do I test my integration end-to-end without hitting real
 registers?"

"What's the canonical KYB onboarding flow with Topograph,
 from signup search to compliance record?"

"How do I cap a single /v2/company request so a deep
 ownership graph stays within a known bound?"
Each answer is grounded in live data from the Topograph catalog and the canonical integration rules — not from training data that may be months out of date.

​
Why it’s better than reading docs

Live country catalog

Coverage, identifiers, datapoints, and pricing are pulled live from the catalog. You’ll never get an answer based on stale documentation.

Methodology built in

The MCP ships with the canonical patterns: search-first identifier resolution, onboarding vs verification phasing, webhook terminal detection, budget caps, and more.

Code that compiles

Example snippets are derived from the OpenAPI spec. No hallucinated endpoint paths, no fabricated request shapes.

Grounded in your editor

Your agent works alongside your existing code — pull data, write the integration, run it, iterate. No copy-pasting from a docs tab.

​
When the MCP earns its keep

Use it when you would otherwise be context-switching to docs:
  • Onboarding a country you’ve never integrated before
  • Sizing volume against country coverage and capability
  • Designing async delivery (webhooks vs polling, terminal-event detection)
  • Picking the right datapoint mix for KYB vs onboarding flows
  • Debugging “why am I getting this error / why is this datapoint missing?”
  • Reviewing an existing integration against the canonical methodology
  • Writing tests against the built-in TEST country
For one-off questions, the regular docs are still the right tool. For real integration work, the MCP is faster.

​
What’s inside

Tools your agent will call:
  • list_countries, get_country, find_data — live country and capability catalog.
  • get_pricing — public per-country prices for any data block.
  • search_docs, get_doc — search and fetch documentation pages.
  • get_openapi — endpoint definitions straight from the OpenAPI spec.
  • example_snippet — copy-paste snippets in curl, Node, Python, or Go.
  • whoami, my_pricing_simulations, personalized_quote — pricing simulator quotes tied to your Topograph login.
Built-in integration rules your agent reads:
  • Onboarding methodology — the five-step KYB flow from search to audit.
  • Search-first resolution — turning fuzzy user input into a canonical company ID.
  • Onboarding vs verification mode — picking the right one per call.
  • Webhooks — signed delivery, progressive payloads, terminal-event detection.
  • Workspaces — required for resellers, end-client attribution and rebilling.
  • Budgets — maxBudget, profileMaxBudget, graphMaxBudget.
  • TEST country — magic identifiers for deterministic CI testing.
  • Data blocks, documents, common pitfalls, and country coverage matrix.

​
Install: other clients

If your client supports HTTP MCP servers and OAuth discovery, point it at the endpoint directly: 
{
  "mcpServers": {
    "topograph": {
      "type": "http",
      "url": "https://api.topograph.co/designer-mcp"
    }
  }
}
Your client will prompt you to sign in with Topograph the first time it queries the MCP. No REST API key is required for the MCP itself; it’s a separate authentication tied to your Topograph login.

​
Public repository

The plugin is published from the public marketplace repository: github.com/getsemaphore/topograph-mcp-library The source is mirrored from Topograph’s monorepo on every release.