Use Pathbound with Claude.
A customer asks why they have to explain the problem again. Claude needs the ticket history, the last email, and what happened on your site before anyone replies. Pathbound gives Claude that record as one current profile.
A customer asks why they have to explain the problem again. Claude needs the ticket history, the last email, and what happened on your site before anyone replies. Pathbound gives Claude that record as one current profile.
Pathbound appears as a remote connector in Claude. Enable it for a conversation, name the customer, and Claude reads the relevant profile and timeline instead of asking you to paste context.
One profile for the contact and company across CRM, support, email, meetings, and website activity.
Plain-language questions backed by Pathbound tools for contacts, companies, events, timelines, and conversations.
The same account-level remote connector available from Claude web, desktop, and mobile.
Specific write tools only where the Pathbound credential and connected source permit them.
Individual accounts can add Pathbound from Customize. Team and Enterprise owners add the remote connector for the organization first; each member then connects their own Pathbound account.
Open Customize → Connectors.
Select + → Add custom connector.
Enter https://mcp.pathbound.ai/mcp and select Add.
Select Connect, sign in to Pathbound, and approve the OAuth request.
In a conversation, open the plus menu, choose Connectors, and enable Pathbound.
An owner opens Organization settings → Connectors, selects Add, then chooses Custom → Web.
The owner enters https://mcp.pathbound.ai/mcp and adds the connector.
Each member opens Customize → Connectors, finds Pathbound, and selects Connect.
The member signs in to Pathbound over OAuth, then enables Pathbound for the conversations that need customer data.
Once connected, these are real jobs Claude runs against your customer data. Each recipe is one tested prompt—paste it and go.
Research every trial signup from the last 24 hours. For each one, pull their profile and company details, read what they did on our site and in the product, and work out who they are and whether the account is a fit. Write a short research brief as a note on each contact (who they are, what they did, verdict, suggested opener), then give me the list ranked by how promising they look, with one line each on why.See the full recipe—Trial-signup research
More jobs in use cases, each with a tested prompt.
Yes. Anthropic brokers remote connectors through your Claude account, so Pathbound is available across those Claude clients after you connect it. Enable the connector for the conversation where you want Claude to use it.
Only an Owner or Primary Owner can add the remote connector to the organization. Once Pathbound is listed, individual members connect and authenticate their own accounts from Customize → Connectors.
No. Claude is interactive, so it connects through Pathbound OAuth. API keys are for headless runners that cannot open a browser.
Check the plus menu in the current conversation and make sure Pathbound is enabled under Connectors. If several connectors can answer, tell Claude to use Pathbound for the identity-resolved customer record.
Only through specific write tools allowed by the connected source and Pathbound permissions. Review tool approval requests before allowing a change. Versioning and rollback are not live yet.
Use Claude chat for a question you are working through now. Use Claude Cowork when you want to hand off a multi-step job, work through files, or repeat the same customer operation.
Sign up, connect one CRM or drop the events snippet, and point your MCP client at mcp.pathbound.ai/mcp.
