Get started
This guide walks you through connecting The Org’s MCP server to Cursor, Claude, or ChatGPT so you can query companies, people, open jobs, org charts, reporting lines, positions, contact details, people/lead lists, and usage from your AI assistant.
Prerequisites
- OAuth or an API key. Clients that implement MCP OAuth (Cursor, Claude, ChatGPT, and others) only need the server URL. They register themselves and send you to The Org to sign in and approve access. If your client cannot do OAuth, create an API key in Manage subscription (Developers section).
- Node.js – Required if you use mcp-remote to connect Claude Desktop to the remote MCP server.
OAuth
Use this when the client has a remote MCP URL field and an OAuth or “sign in” option. Set the URL to:
https://api.theorg.com/v1.1/mcpLeave the API key blank. On the first connection the client discovers /.well-known/oauth-protected-resource/v1.1/mcp, registers, and opens The Org consent page. After you approve, it calls the MCP with Authorization: Bearer. Credits are charged to the account you signed in with.
The server implements the MCP authorization spec: protected-resource metadata, authorization-server metadata, OpenID Connect discovery, dynamic client registration, authorization code with PKCE (S256), and a userinfo endpoint. Supported scopes are openid, email, and mcp. See Authentication.
Credits for requests performed through the MCP server are deducted from the same credit balance as your other API usage. Credit-free tools also have per-key rate limits shared with the matching REST routes — see Rate Limiting.
Claude Desktop
To set up your Claude Desktop assistant, add this entry to your claude_desktop_config.json file.
Config file location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
With API key in config (replace YOUR_API_KEY):
{
"mcpServers": {
"theorg": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.theorg.com/v1.1/mcp",
"--header",
"X-Api-Key: YOUR_API_KEY"
]
}
}
}With API key in an environment variable (recommended):
{
"mcpServers": {
"theorg": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.theorg.com/v1.1/mcp",
"--header",
"X-Api-Key:${THEORG_API_KEY}"
],
"env": {
"THEORG_API_KEY": "your-api-key-here"
}
}
}
}Restart Claude Desktop after changing the config.
Cursor
Cursor has integrated support for MCP servers.
OAuth (recommended):
- Go to Cursor > Settings > Cursor Settings > MCP
- Click Add new global MCP server
- Add the server URL and leave the API key empty:
{
"mcpServers": {
"theorg": {
"type": "streamableHttp",
"url": "https://api.theorg.com/v1.1/mcp"
}
}
}Cursor starts OAuth and opens The Org so you can approve the connection.
API key:
- Go to Cursor > Settings > Cursor Settings > MCP
- Click Add new global MCP server
- Add the following configuration:
{
"mcpServers": {
"theorg": {
"type": "streamableHttp",
"url": "https://api.theorg.com/v1.1/mcp",
"headers": {
"X-Api-Key": "YOUR_API_KEY"
}
}
}
}Replace YOUR_API_KEY with your API key. Restart Cursor if the server does not show up.
Integration with AI assistants
Once the MCP server is connected, you can ask your assistant to:
- Find a company – e.g. “Search for The Org company”, “Look up apple.com”, or “Find the company with LinkedIn slug stripe”
- Research a company – e.g. “How big is theorg.com, what industry are they in, and have they raised funding?”
- Fetch an org chart – e.g. “Get the org chart for theorg.com”
- Explore a chart – e.g. “Who are the executives at Stripe, and who reports to the CFO?” (
get_company_executive_positions, thenget_company_position_reportsorsearch_company_positions; results can be people, jobs, or groups; 10 credits per company per API key for 30 minutes) - Look up a person – e.g. “Find Patrick Collison at Stripe” or “Look up https://www.linkedin.com/in/patrickcollison”
- Find open jobs – e.g. “Show Product Manager jobs at Stripe” or “Find remote engineering roles”
- Find a manager – e.g. “Who is the manager of andreas@theorg.com?”
- Find direct reports – e.g. “Who reports to the CTO of theorg.com?”
- Search positions – e.g. “Who is the CTO of The Org?” or “Find marketing people at Apple”
- Get contact details – e.g. “Get work emails for the marketing leaders you just found”
- Build a lead list – e.g. “Find CTOs at Series B fintechs and save them to a new list”
- Manage lists – e.g. “What lists do I have?” or “Add these people to my Empty List”
- Check usage – e.g. “How many API credits do I have left?”
The assistant will call the appropriate MCP tools and return the data (including list links like https://theorg.com/people/lists/{slug}). Prefer find_person when you already have a LinkedIn URL or a name+company pair; use find_positions for role/department searches. If the question is about one company’s org chart structure, get_company_executive_positions, get_company_position_reports, and search_company_positions need companyId, a UUID. Identify that company and its id with search_companies first, then call those tools. The signed-in account needs enough credits for paid operations such as chart exploration, find_positions, and resolve_contacts.
The workEmail field on a position search result only shows an email we already have on file. If it is empty, ask the assistant to resolve contacts for those people — resolve_contacts runs a live lookup and often finds an address that was not stored yet.