Get started

This guide walks you through connecting The Org’s MCP server to Claude Desktop or Cursor 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

• API key – Create one in Manage subscription  (Developers section).
• Node.js – Required if you use mcp-remote  to connect Claude Desktop to the remote MCP server.

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:

1. Go to Cursor > Settings > Cursor Settings > MCP
2. Click Add new global MCP server
3. 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”
• 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. Ensure your API key has enough credits for paid operations such as find_positions and resolve_contacts.