Introduction
What is MCP?
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external data and tools. The Org provides an MCP server so you can use Claude, Cursor, and other MCP-compatible clients to query companies, people, open jobs, org charts, reporting lines, positions, contact details, people/lead lists, and API usage in natural language.
MCP server URL
https://api.theorg.com/v1.1/mcpPaste this URL into Cursor, Claude, ChatGPT, or any other MCP-compatible client. For client-specific setup, see Get started.
What you can do
Once connected, your AI assistant can call these tools on your behalf:
| Tool | Description | Credits | Rate limit |
|---|---|---|---|
| search_companies | Look up companies by name, domain, email, or LinkedIn company URL/slug | Free | 30 / 60s |
| get_company | Get a company profile: description, size, location, industries, funding | Free | 60 / 60s |
| get_org_chart | Get an iframe embed URL for a company’s org chart (by domain or LinkedIn URL/slug) | Free | 60 / 60s |
| get_company_executive_positions | Company context plus L1, L2, and advisers. Each entry can be a person, a job, or a group | 10 per company per API key, then free for 30 minutes | Global 15/s |
| get_company_position_reports | Direct reports of one chart position (p-… person or job, g-… group) | Same 30-minute exploration pass | Global 15/s |
| search_company_positions | Search one company’s chart by name or title. Results can be people, jobs, or groups | Same 30-minute exploration pass | Global 15/s |
| find_person | Look up a specific person by LinkedIn URL/slug, or by full name + company name/domain | Free | 30 / 60s |
| find_jobs | Search open job vacancies by job URL/slug, title, company, or filters. Max 25 results | Free | 30 / 60s |
| get_manager | Find the manager of a person (by position ID, work email, or LinkedIn URL/slug) | 1 per find | Global 15/s |
| get_reports | Find the direct reports of a person (by position ID, work email, or LinkedIn URL/slug) | 1 when reports are found | Global 15/s |
| find_positions | Search positions/people with filters (company, department, job titles, etc.). Max 25 results per call | 1 per row returned | Global 15/s |
| resolve_contacts | Resolve work emails for up to 25 people found via find_positions or find_person | 1 per person newly resolved | Global 15/s |
| get_lists | List people/lead lists for your account (owned and shared) | Free | 30 / 60s |
| add_to_list | Add people (position IDs from find_positions / find_person) to an existing list. Max 25 IDs per call | Free | Global 15/s |
| create_list | Create a people/lead list and optionally add position IDs in the same call. Max 25 IDs | Free | Global 15/s |
| get_usage | Check your remaining API credits and usage | Free | 30 / 60s |
List tools return links like https://theorg.com/people/lists/{slug} (for example https://theorg.com/people/lists/empty-list).
Credits are deducted from the same balance as your API usage. List tools do not consume credits. Re-resolving a contact your account has already paid for is free. Free-tool rate limits are per API key and shared with the matching REST route — see Rate Limiting.
get_company_executive_positions, get_company_position_reports, and search_company_positions share one exploration pass. The first call that finds a company on an API key costs 10 credits and unlocks those three tools for that company for 30 minutes. An OAuth connection is its own API key, so its pass is separate from a key you paste yourself. An unknown company id is not charged. Another company, or the same company on a different key, is a separate charge. If the key does not have 10 credits, the call returns an error and nothing is charged.
Integration with AI assistants
The MCP server works with any client that supports MCP over HTTP, including Cursor, Claude, and ChatGPT. Clients that support remote MCP OAuth only need the server URL. Claude Desktop can also connect through mcp-remote with an API key. Setup is in Get started.
The MCP server supports OAuth in full, and it also accepts an API key.
OAuth. Paste the server URL into a client that implements MCP OAuth (Cursor, Claude, ChatGPT, and others). The client discovers the authorization server, registers itself, and sends you to The Org to sign in and approve access. Later calls use Authorization: Bearer. You do not paste an API key into the client. The flow is authorization code with PKCE (S256), dynamic client registration, and OpenID Connect discovery. Scopes are openid, email, and mcp.
API key. You can still send your API key in the X-Api-Key header, or as the api_key query parameter.
OAuth connections and API keys use the same credit balance. Details are in the MCP API reference.
For setup, see Get started. For endpoint details, protocol, and examples, see the MCP API reference.