BuyerTwin works with AI assistants that support remote Model Context Protocol servers.
The connection uses OAuth, so there is no API key to copy. Sign in, approve access, and select the BuyerTwin workspace you want the assistant to use.
What you need
Connect BuyerTwin with MCP
- Open your AI assistant’s settings for MCP servers, connectors, or integrations.
- Choose the option to add a remote or custom MCP server.
- Enter BuyerTwin as the connection name.
- Use the BuyerTwin MCP server URL: https://mcp.buyertwin.com/mcp
- Save or connect. Your browser should open the BuyerTwin OAuth sign-in flow.
- Sign in to BuyerTwin and approve access.
- Select the workspace you want the AI assistant to use.
- Return to your AI assistant and confirm that BuyerTwin appears as connected.
Menu names vary by AI product. If you cannot find the MCP settings, ask the product’s coding assistant or support documentation how to add a remote MCP server with OAuth.
Test the connection
Start with a request that explicitly names BuyerTwin and the workspace or buyer context you want to use:
If your AI assistant asks for permission to use a BuyerTwin tool, review and approve the request. A successful response should be grounded in the selected workspace rather than generic buyer assumptions.
What BuyerTwin can help your AI do
The available capabilities depend on the workspace, your permissions, and the AI client.
Ask a buyer
Understand how a target buyer is likely to think, react, prioritize, question, or object.
Compare buyers
Identify meaningful similarities, differences, patterns, and implications across buyer types.
Create buyer-focused content
Draft messaging, content, and briefs grounded in BuyerTwin intelligence.
Evaluate messaging
See what aligns with a buyer, what is missing, and what should change.
Prepare for sales conversations
Plan questions, talking points, risks, and likely objections.
Improve buyer knowledge
Propose corrections or updates to maintained buyer intelligence when your access allows it.
Behind these skills, MCP tools let the AI find approved buyer context, apply it to the task, and—where permitted—propose or make updates. Your AI assistant can show you which BuyerTwin tools are available for the current connection.
Example prompts
Troubleshooting
The sign-in window does not open Confirm that your AI assistant supports remote MCP servers with OAuth. Then remove the incomplete connection and add the BuyerTwin server URL again.
I selected the wrong workspace Disconnect BuyerTwin in your AI assistant, reconnect it, and choose the correct workspace during authorization.
BuyerTwin is connected but no tools appear Restart the conversation or refresh the connection. Confirm that your BuyerTwin account has access to the selected workspace. Your AI client may also require you to enable tools for the conversation.
The response seems generic Explicitly ask the assistant to use BuyerTwin and name the buyer you want it to consult. You can also ask which BuyerTwin tools and skills are available before beginning the task.
Security and access
BuyerTwin uses OAuth for authentication. Access is tied to the signed-in user, the workspace they select, and the permissions available to them. Only approve the connection on a device and in an AI application you trust.
Official BuyerTwin plugin
We are working toward an official BuyerTwin plugin that will make setup and capability discovery even easier. Until then, the standard MCP connection above gives supported AI assistants secure access through BuyerTwin OAuth and lets each user choose the workspace they want to use.