Sales & Customer Support · The Org + Claude
The Org MCP with Claude: Faster Lead Lists and Org Chart Research
The short answer
Claude connects to The Org through the Model Context Protocol, a secure standard that lets Claude read and act within the tool. Once connected, a team member can ask Claude in plain English to find decision makers, look up a manager, or build a lead list. Access is set up with an API key and limited to the permissions the organisation chooses.
What is The Org?
The Org is a company intelligence platform. It holds information about how companies are structured, including org charts, job positions, reporting lines and people. Sales, recruitment, account management and customer support teams use it to understand who works where, who reports to whom, and which people to contact. It helps teams find the right person faster instead of guessing from job titles or scrolling through company websites.
How Claude connects to The Org through MCP
The Model Context Protocol, or MCP, is an open standard that lets Claude securely use other software. Think of it as a universal adapter between Claude and the tool. The Org provides an MCP server, and it can also be reached through its direct API, so Claude can use the platform without anyone copying data by hand.
Once connected, Claude can search for people, inspect an organisation's structure, look up who a person's manager is, and assemble lead lists from criteria you describe. A salesperson might ask for finance directors at mid-sized manufacturers in a given region, and Claude carries out the search and presents the results in a clear table.
Permissions and approvals keep your people in charge. Access uses an API key with least-privilege settings, so Claude only sees what you allow. Consequential actions, such as exporting a large list or sending it to another system, can require a person to approve them first, and audit logs record what was done and when.
What you can automate
Building targeted lead lists
A sales team describes its ideal customer, such as operations heads at logistics firms with more than 500 staff. Claude searches The Org, returns matching people with their roles, and prepares a list the team can review. Reps spend their time contacting prospects rather than building spreadsheets by hand.
Mapping a target account
Before a first meeting, an account executive asks Claude to show the org chart of a prospect and identify the department heads. The summary helps the rep understand who influences a buying decision and who they should approach first.
Finding the right escalation contact
A customer support lead has a complex account issue and needs to reach a senior decision maker at a customer. Claude looks up the customer's structure and manager relationships, so the team can route the escalation to the correct person quickly and politely.
Preparing for partner and vendor outreach
A procurement or partnerships manager wants to know who runs technology at a potential supplier. Claude searches positions and reporting lines and produces a short brief, saving research time before the first call.
Keeping account data current
A revenue operations team periodically asks Claude to review key accounts for changes in leadership or structure. Claude highlights new or departed people so records in the CRM can be updated with human review.
An end-to-end workflow: Account research to CRM update
TriggerA new target account is added to the CRM by a sales development representative.
Claude reads the account name and industry from the CRM record.
Claude uses The Org to retrieve the company's org chart and identify department heads in sales, finance and operations.
Claude produces a short brief listing the key contacts and their reporting lines.
The representative reviews the brief and approves which contacts to add.
Approved contacts are created as records in the CRM, linked to the account, with the source noted.
The sales manager receives a summary in Microsoft 365 Teams for the weekly pipeline review.
OutcomeTypical teams find that new accounts are ready for outreach within minutes rather than hours, with cleaner CRM records and a clear audit trail of where each contact came from.
How we set it up
Free automation audit
We review your sales, recruitment and support workflows to find where people search and list building take the most time. There is no charge for this session, and you leave with a clear view of what is worth automating.
Connection design
We confirm your access needs and set up The Org connection using an API key, scoped to the minimum permissions your team requires. We agree which data Claude can read and which actions need approval.
Workflow build
We design the end-to-end workflow across The Org and your other systems, such as your CRM, Microsoft 365 or ticketing tool. Consequential steps are built with human approval points.
Testing with real cases
We test the workflow against real past accounts and searches from your team, checking accuracy and refining prompts and filters until the results meet your standards.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your team on how to ask Claude for org charts and lead lists safely and effectively.
Who benefits
- Sales leaders
- Faster, more targeted pipeline building and clearer account maps for deal planning.
- Sales development representatives
- Less time on manual research and more time spent on outreach.
- Customer support and account managers
- Quicker routing of escalations to the right decision makers.
- Revenue operations teams
- Cleaner CRM records with a traceable source for every new contact.
Security and control
- Access is controlled by an API key with least-privilege permissions, so Claude only reaches the data your team has approved.
- People approve consequential actions, such as large exports or writes to other systems.
- Audit logs record every search and action so you can review what was done.
- Contact data is used only for the business purposes you define, in line with your internal policies.
- We recommend a periodic review of permissions as your team and processes change.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can use the connection under their own data protection frameworks, and we configure it to match their policies. In India, we design workflows to meet the Digital Personal Data Protection Act, 2023. For organisations in the UAE and Saudi Arabia, we align data handling with local data protection laws. Custom applications can be hosted in India, the United States, the United Kingdom or the European Union, chosen to meet your requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does The Org MCP server do?
The Org MCP server lets Claude securely use The Org platform. Through it, Claude can search people, inspect org charts, look up managers and build lead lists based on plain English requests. The server acts as the adapter between Claude and The Org, with access controlled by the permissions you set.
Is connecting The Org to Claude secure?
Security depends on how the connection is configured. We use an API key with least-privilege permissions, so Claude only reaches the data you allow. Approval steps and audit logs add further control. We review the setup with your IT team before launch.
What can Claude do with The Org?
Once connected, Claude can search for people by role, location or company, show how an organisation is structured, identify a person's manager, and assemble lead lists from criteria you describe. It presents results clearly so your team can act on them quickly.
How long does setup take?
Many projects reach launch within a few weeks, depending on how many systems are involved and how complex the workflow is. The free automation audit gives a clearer timeline for your organisation.
What plan or permissions do I need?
You need an API key from your The Org account with permissions suited to the searches and data your team wants Claude to use. The exact access depends on your existing agreement with The Org, so we check this during the audit before building anything.