1
Open Claude connector settings
Sign in to Claude, then open Customize → Connectors. For Team or Enterprise, an Owner starts in Organization settings → Connectors.
Set up the connector
Follow the route for your Claude workspace. Registration and authorisation are one-time steps; after that, enable OneSales only in conversations that need account intelligence.
Individual workspace: Free, Pro, or MaxAdd OneSales from your personal connector settings. Claude Free supports one custom connector.
Organisation workspace: Team or EnterpriseAn Owner or Primary Owner registers OneSales once. Each member then connects and authorises their own OneSales account.
2
Add a custom connector
On an individual plan, select +, then Add custom connector. On Team or Enterprise, select Add, hover over Custom, then choose Web.
3
Enter the exact connector details
If Claude asks for a name, enter OneSales. Paste the URL below into the remote MCP server URL field. Leave the optional advanced OAuth fields blank.
https://app.onesales.ai/mcpCopy4
Authorise the correct OneSales account
Select Add. On the OneSales sign-in page, confirm that you are using the intended workspace, review the requested access, and select Authorize.
5
Enable OneSales in your conversation
Start a chat, select the + button in the lower-left of the composer, open Connectors, and turn on OneSales for that conversation.
6
Verify the connection before relying on it
Ask: “What OneSales information can you access?” Confirm that Claude can see the expected OneSales tools. If a tool or dataset is missing, check your OneSales access before continuing.
Team and Enterprise members: after your Owner adds OneSales, go to Customize → Connectors, find OneSales, and select Connect to authorise your own account.
Use OneSales intelligence across the account lifecycle
Ask in plain language. When OneSales is enabled, Claude can select the relevant intelligence available to your workspace. The quality and completeness of each answer depend on the underlying OneSales data.
Prioritise accounts and territories
Compare ICP fit, research readiness, and recent buying signals to focus seller time on the accounts with the strongest available evidence.
Map complex buying groups
Organise known stakeholders by role, influence, and relationship, then identify gaps that still require research or validation.
Prepare evidence-based briefings
Bring account context, stakeholder intelligence, recent changes, known risks, and open questions into one meeting-ready briefing.
Create relevant value messaging
Connect verified account priorities to approved positioning, capabilities, proof points, and previous outreach without inventing missing context.
Develop strategic account plans
Structure objectives, stakeholders, opportunities, risks, evidence, open questions, and next actions into an account plan your team can review.
Monitor material account changes
Review available leadership, funding, hiring, company news, and champion job-change signals, with sources where OneSales provides them.
Enterprise sales prompts for OneSales in Claude
Copy a prompt, replace the bracketed details, and keep the instruction to distinguish verified OneSales evidence from assumptions. This makes the output easier to review, challenge, and use with customers.
Prioritise accounts
Which accounts show the strongest fit and verified buying signals this week? Rank them, explain the evidence, and recommend the next action for each.
Copy promptAccount brief
Brief me on [account]. Summarise why the account matters now, its ICP fit, recent signals, key stakeholders, risks, and the three best next actions.
Copy promptBuying team map
Map the buying team at [account]. Identify likely champions, decision-makers, influencers, blockers, and any important roles still missing.
Copy promptMeeting preparation
Prepare me for my meeting with [account]. Include recent signals, stakeholder priorities, known risks, open questions, and five questions I should ask.
Copy promptPersonalised outreach
Draft a concise email to [contact] at [account], grounded in verified account signals, relevant positioning, approved proof points, and previous outreach.
Copy promptStrategic account plan
Start a strategic account plan for this account. Use available OneSales intelligence to structure business priorities, stakeholders, buying signals, opportunities, risks, open questions, and next actions. Separate verified facts from assumptions.
Copy promptIdentify key pains
Start identifying the key pains for this account. Connect each pain to available evidence, affected stakeholders, likely business impact, and questions that would validate or disprove it. Flag unsupported assumptions.
Copy promptValue messaging
Start value messaging for this account. Tailor the message to [persona], link verified pains and priorities to relevant capabilities and approved customer evidence, and clearly flag any assumptions or missing proof.
Copy promptChoose the OneSales intelligence available in Claude
The connector exposes only the OneSales products, tools, and data available to the signed-in user. Select the level that matches the sales workflows you want Claude to support.
OneSales ICP Engine
Define and maintain your ideal customer profile, then make that shared fit context available to Claude.
Open OneSalesOneSales Account Intelligence
Add account research, signal monitoring, buying-group mapping, seller context, and evidence-based messaging workflows.
Compare plansOneSales intelligence reference
You do not need to memorise or manually select these tools. Claude selects the relevant tool for the request. Availability depends on the signed-in user’s OneSales product access and underlying data.
View the complete intelligence reference
Account intelligence
- Account Brief
- Account overview, timing, and ICP fit.
- Account Universe
- Your accounts ranked and prioritised by fit.
- Research Status
- Whether research is available and ready to use.
- Intelligence Sources
- Sources and citations behind account intelligence.
Buying-team intelligence
- Buying Team
- Champions, decision-makers, influencers, and other stakeholders.
- Buying Team Profile
- A detailed profile of one buyer or stakeholder.
Signal intelligence
- Account Signals
- Recent leadership, funding, hiring, news, and champion changes.
- Cross-Account Signal Feed
- Recent signals across your full book of accounts.
Seller strategy
- Strategy Context
- Your go-to-market context and selling foundation.
- ICP Engine
- Target segments, industries, company size, and other fit criteria.
- Positioning
- Company identity, category, description, and value proposition.
- Capabilities
- Your products, the problems they solve, and the outcomes they support.
- Persona Value Mapping
- Target personas and the value you provide to each.
- Competitive Intelligence
- Competitors and approved positioning against them.
- Customer Evidence
- Approved proof points and guidance for using them.
- Signal Framework
- Signals that indicate account fit or timing.
- Disqualifiers
- Traits that indicate an account may be a poor fit.
Sales context and knowledge
- Account Chat History
- Previous OneSales conversations for an account.
- Email History
- Outreach already sent through OneSales.
- CRM Connection Status
- Whether CRM context is connected and the account owner.
- Seller User Profile
- User details, signature, and scheduling links.
- Sales Prompts
- Prepared prompt templates for common sales tasks.
- Company Knowledge Base
- Your organisation’s shared OneSales knowledge.
Data access, permissions, and user control
The OneSales tools listed on this page provide intelligence and context to Claude. They do not send emails, update CRM records, or change OneSales account data by themselves.
Access follows the signed-in user
Review the requested access during authorisation. Claude can use only the OneSales tools and data exposed to that user. Any action performed through another connected service remains subject to that service’s permissions and approval controls.
Frequently asked questions
Which Claude plans support the OneSales connector?
Claude custom connectors using remote MCP are available on Free, Pro, Max, Team, and Enterprise plans. Free users are currently limited to one custom connector. Team and Enterprise connectors must first be registered by an Owner or Primary Owner.
Is OneSales for Claude read-only?
The OneSales tools described on this page provide intelligence and context. They do not send emails, update CRM records, or change OneSales account data by themselves. Actions performed through other connected services remain subject to those services’ permissions and approval controls.
Why can’t Claude see all of my OneSales data?
Access follows the signed-in OneSales user. Confirm that you authorised the intended OneSales workspace and that the user has access to the relevant product, account, tool, and underlying data.
How do I disconnect OneSales from Claude?
Open Customize → Connectors in Claude and manage the OneSales connection. In Team or Enterprise workspaces, an Owner or Primary Owner manages the organisation-level connector registration.
About this guide
Authorship and verification
Written by Seamus Devine, founder of OneSales and former co-founder of ClosePlan.
- Published
- 23 August 2026
- Last verified
- 24 August 2026
- Verification method
- Checked against the current OneSales connector configuration and Anthropic’s official custom-connector documentation.
Primary sources
- Anthropic: Get started with custom connectors using remote MCP
- Anthropic: Use connectors to extend Claude’s capabilities
- OneSales Privacy Policy
Continue exploring OneSales
Need help connecting OneSales to Claude?
Contact support@onesales.ai. Include your Claude plan and the setup step where you are blocked.
