What an MCP connection does
An MCP connection lets an AI assistant outside Athean, such as Claude, work with your Athean records and tools from its own conversations. For example, it can research an account, organize a prospect list, prepare outreach, check your availability and book a meeting, or create a document and give you a link to open it in Athean.
- It acts as you. The assistant has your current data access and permissions, and Athean checks them on every action. The connection doesn't grant extra access. What's available also depends on your organization's connected tools.
- Your assistant handles confirmation. Athean runs a valid action without showing its own approval card, including actions that change records, send messages, start outreach, book meetings, or use credits.
- You sign in as yourself. You don't need an organization API key. To connect your own service with an API key instead, see API setup.
Connect Claude or another MCP client
You need an active Athean account and an assistant that can add a remote MCP server with sign-in. The server URL is https://app.athean.com/api/mcp. Organization administrators can also copy it from the MCP tab in Org settings → API & MCP, which shows the steps for Claude.
To connect Claude:
- In Claude, open Customize → Connectors, then choose Add → Add custom connector.
- Enter Athean as the name and paste the server URL into MCP server URL.
- Select Continue, then connect. If Athean asks you to sign in, use the account and organization you want to connect. If this browser is already signed in to Athean, that account is connected without a sign-in step; to connect a different account, sign out of Athean in this browser first.
- Athean asks you to connect the assistant to your account and explains that it will act as you, with your data access and permissions. Select Allow, or Deny to cancel.
- Open the connector's Tool permissions and set Read-only tools and Write/delete tools. Athean's MCP tab suggests Always allow for both. Most Athean tools, including record lookups, are write/delete tools, so blocking that group stops most Athean work. With Always allow, Claude runs Athean actions without asking you first.
- Test with a read, such as "Find Acme Corp. in Athean and summarize the recent activity I can access." Check that the account and sources are the ones you expect.
Other assistants have their own connection settings: add the same server URL, sign in to Athean, and select Allow.
Ask your assistant to work in Athean
- Describe the result you want and who it's for. For example, ask for a prospecting plan for an account, with sources and proposed next steps.
- Review the records, recipients, and changes the assistant proposes, and say exactly which actions it should take.
- After it acts, check the result it reports, including any items that failed.
- When the assistant returns an Athean link, open it to review the saved list, document, draft, run, or other record in Athean.
- Actions are real. They can change records, send messages, start outreach, book meetings that send invitations right away, and use credits. Athean doesn't ask for its own approval, so review the scope before you authorize an action.
- Calendar availability and booking: you need an active scheduling link and a connected Google or Microsoft calendar that Athean can add events to. Athean uses your scheduling link's Timezone, working hours, Meeting durations, Buffer (min), Min notice (hrs), and Max days ahead, and checks only your primary calendar, not your guests' calendars. A booking adds a Zoom meeting when your organization's Zoom scheduling covers you, and appears under Bookings in Settings → Scheduling link. Athean can't reschedule or cancel meetings; change them in your calendar. See Scheduling links.
- Each action needs only its own permission. For example, you can research accounts through the connection without permission to send outreach.
- Unclear results: if an action times out or its result is unclear, ask the assistant to check the record before it tries again.
- Batches: check each reported result. Items that failed don't undo the ones that succeeded.
Shared context, result links, and browser sign-in
- What the assistant gets: your current user, organization, and settings; guidance you've saved for Athean; and your personal saved workspace files, the same ones your personal chats, agents, and automations use. Project files aren't available (see Projects). It reads the current versions on each request.
- What it doesn't get: your Chat conversations in Athean, or the record open in your browser. Name or link the record you mean.
- Attachments: a file you attach in your assistant isn't attached to a Chat conversation in Athean. Use your assistant's own attachment feature and say what it should do with the file.
- Nothing opens in Athean: MCP work doesn't create a Chat conversation in Athean, and Athean panels and approval cards don't appear in your assistant. Your assistant shows the results itself.
When a result has a page in Athean, such as a list, deck, document, draft, agent, automation, or run, the assistant returns a link to it. The link opens the normal Athean app. You need access to the record to open it, and links to deleted records don't work. Results without a page, such as plans, stay in your assistant's conversation.
Signing in your assistant doesn't sign in your browser. If a link opens the Athean sign-in page, sign in normally or ask your assistant for a browser sign-in link:
- Open the private link. It works once and expires after a few minutes.
- On Sign in to Athean, check the account and organization shown.
- Select Continue to Athean to sign in as that account and open the page, or Use a different account to sign in normally. Continuing replaces any Athean account already signed in on that browser.
If your organization requires single sign-on, the assistant can't create sign-in links; sign in with your organization's SSO instead. If a link has expired or was already used, ask for a new one.
Troubleshoot the MCP connection
- Sign-in fails: reconnect from your assistant's connector settings and check the Athean account and organization. If Athean says This connection request could not be verified, close the tab and start the connection again from your assistant.
- The assistant can't look up your records: check the connector's tool permissions. In Claude, most Athean tools are under Write/delete tools.
- An action is unavailable or refused: check your role (see Permissions and roles) and any connection the action needs, such as your email or LinkedIn account in Settings → Integrations. The MCP connection doesn't add access.
- A result link doesn't open: check that the record still exists and that you have access to it. A link doesn't grant access.
- The connection stopped working: connections stop if your Athean account is deactivated. Otherwise, reconnect from your assistant's settings.
- Credit limits block work: see AI usage and credit limits.
To disconnect, remove the connector in your assistant's settings. For other problems, contact support with your assistant's name, the action, and the error message. Leave sign-in links and credentials out of the message.