Sybill
by Sybill
Read sales call transcripts, recordings, deals and CRM accounts from Sybill in your AI assistant, and ask Sybill's own sales reasoning a free-text question. Eight documented tools, three of which the directory does not list. Every tool reads; nothing writes to your CRM over MCP.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Sybill via MCP
https://mcp.sybill.ai/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Sybill Tools & Capabilities (5)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The directory listing is three tools short. Anthropic's snapshot names five; Sybill documents eight.
get_ask_sybill_result,list_accountsandget_accountare documented and unlisted. - The directory record carries no permissions label at all. There is no field to falsify and none to rely on. Read Sybill's tool tables instead.
- We could not verify the tool list or its behaviour ourselves. The endpoint returns HTTP 401 to an anonymous handshake, so no schemas and no safety annotations were readable. Every read-only classification here is Sybill's documentation, restated.
- The dispatcher's reach is not enumerable.
ask_sybilltakes free text and Sybill documents it as covering emails and people that no typed tool exposes. There is no published list of what it can retrieve, so the connector's read surface cannot be bounded by counting tools. - The access claim is Sybill's, not our observation. We did not authenticate, so we could not test what a tool returns when asked for a conversation the user cannot see. Sybill does not document that behaviour either.
- Team sharing widens the corpus without touching the connector. Sybill documents an administrator-set sharing rule that publishes teammates' meetings into a team view, which the signed-in user — and therefore the agent — can then read.
- The API is alpha. Sybill states that endpoints, schemas, rate limits and behaviour may change at any time without prior notice, and recommends against production-critical integrations until a stable release.
- MCP rate limits are undocumented in numbers. Sybill states MCP usage limits are managed separately from REST API key limits and may depend on your plan, without publishing the figures. The REST limits it does publish — 60 requests per minute, 1,000 per hour, 10,000 per day per key — govern the REST path, not this one.
- Deals and accounts need a paid CRM integration. Sybill documents CRM integration as Business and Enterprise only, requiring a Sybill administrator. Four of the eight tools depend on it.
- Recording notice is a setting, and one option is silence. Sybill documents a configuration that sends no notification and prompts for no consent, alongside its own caution about using it.
- Late joiners may see no notice. Sybill states the chat notification is invisible to participants who join after it was sent.
- The scopes carry no data granularity. Four OpenID Connect identity scopes cover the whole connector. Reading a deal and reading a verbatim transcript are the same grant.
- Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, but the gated endpoint blocked our own
prompts/list, so we cannot say whether the server serves any. - Nothing here writes. If you want Sybill to update CRM fields after a call, that is Sybill's own CRM integration, configured in Sybill — not something an agent can reach through this connector.
Frequently asked questions
Whose sales calls can the Sybill MCP connector read?
Only the calls your own Sybill account can already open. Sybill states that MCP reads are scoped to what the signed-in user can access, and draws an explicit contrast with its REST API, whose keys operate with organization-level context instead. What your account sees includes your own meetings plus whatever teammates' meetings an administrator has shared team-wide.
Can the Sybill MCP server write to Salesforce or HubSpot?
No. Sybill's CRM autofill runs inside Sybill's own product on a separate CRM integration, not over MCP. All eight documented MCP tools read. The write verbs in Sybill's API — the POST, PATCH and DELETE endpoints — sit behind a separate Import permission that its documentation maps to REST API keys, and no MCP tool exposes them.
How many tools does the Sybill MCP server actually have?
Sybill's own documentation lists eight, while Anthropic's directory snapshot of 2026-08-16 names five. The three missing from the directory are get_ask_sybill_result, list_accounts and get_account. None of them changes the read-only picture, but a reader sizing the surface from the directory alone will undercount it by three tools.
What does ask_sybill actually have access to?
Sybill describes it as answering questions about your calls, deals, people, companies and emails — a wider reach than the other seven tools combined, since those cover only conversations, deals and accounts. Emails and people are reachable through this one free-text tool and through no other. Sybill recommends allowing it by default and gating the raw data tools.
Does get_conversation return the full call transcript?
Yes, plus more. Sybill's API schema for a conversation detail includes a transcript array of speaker-attributed text with timestamps, an AI summary, participant names and email addresses, CRM linkage, and a recordings object holding video and audio URLs. A single call by identifier returns the whole record, so this is verbatim customer conversation rather than summarised metadata.
Does Sybill tell meeting participants they are being recorded?
It depends entirely on a setting an administrator chooses. Sybill documents three recording-consent options: never notify, notify on external calls only, or always notify. Its help centre states plainly that one available choice sends no notification and prompts for no consent, while adding that some legal jurisdictions require consent to be collected. Sybill does not decide this for you.
Is the Sybill API stable enough to build on?
Not yet, by Sybill's own account. Its introduction page carries an alpha notice saying endpoints, schemas, rate limits and behaviour may change at any time without prior notice, and recommending against production-critical integrations until a stable release. The MCP server sits on that same API surface, so tool shapes and limits can move under a connected agent.
Sources
- Sybill MCP server documentation — https://api.sybill.ai/docs/mcp.html (fetched 2026-08-19; the documentation URL Anthropic's directory publishes for this connector) · retrieved 2026-08-19
- Sybill API introduction, including the alpha notice and the MCP-versus-REST visibility contrast — https://api.sybill.ai/docs/introduction.html (fetched 2026-08-19) · retrieved 2026-08-19
- Sybill API authentication, permissions and scopes — https://api.sybill.ai/docs/authentication.html (fetched 2026-08-19) · retrieved 2026-08-19
- Sybill API rate limiting — https://api.sybill.ai/docs/rate-limiting.html (fetched 2026-08-19) · retrieved 2026-08-19
- Sybill OpenAPI specification — https://api.sybill.ai/docs/openapi.yaml (fetched 2026-08-19; source for the conversation, transcript, participant and recordings schemas and for the REST write operations) · retrieved 2026-08-19
- Use Ask Sybill through the API and MCP — https://help.sybill.ai/en/articles/16497554-use-ask-sybill-through-the-api-and-mcp.md (fetched 2026-08-19) · retrieved 2026-08-19
- Using Sybill in Claude — https://help.sybill.ai/en/articles/16394682-using-sybill-in-claude.md (fetched 2026-08-19) · retrieved 2026-08-19
- Recording Consent Management — https://help.sybill.ai/en/articles/6936693-recording-consent-management.md (fetched 2026-08-19) · retrieved 2026-08-19
- Who has access to my call recordings? — https://help.sybill.ai/en/articles/6137767-who-has-access-to-my-call-recordings.md (fetched 2026-08-19) · retrieved 2026-08-19
- Meeting Visibility across the Team — https://help.sybill.ai/en/articles/8132308-meeting-visibility-across-the-team.md (fetched 2026-08-19) · retrieved 2026-08-19
- How does Sybill's integration with CRM systems work? — https://help.sybill.ai/en/articles/8132410-how-does-sybill-s-integration-with-crm-systems-work.md (fetched 2026-08-19) · retrieved 2026-08-19
- Sybill help centre machine index — https://help.sybill.ai/llms.txt (fetched 2026-08-19; used to locate every help-centre article above by its published
.mdform) · retrieved 2026-08-19 api.sybill.aiserves norobots.txt(404, fetched 2026-08-19).help.sybill.ai/robots.txtallows crawling and carriesContent-Signal: search=yes,ai-train=no,use=reference— noai-inputaxis is expressed, so synthesis is neither granted nor restricted, and the host publishes.mdmachine-readable forms of every article.www.sybill.ai/robots.txtcarries the same signal but disallows several AI crawlers by name, so no marketing-site page was used as a source for this page · retrieved 2026-08-19- Live RFC 9728 protected-resource descriptor — https://mcp.sybill.ai/.well-known/oauth-protected-resource/mcp (fetched 2026-08-19; the root and path-insert forms both return a plain-text 404) · retrieved 2026-08-19
- Live RFC 8414 authorization-server metadata — https://mcp.sybill.ai/.well-known/oauth-authorization-server (fetched 2026-08-19; same four scopes as the resource descriptor) · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19: a POST to the endpoint returns HTTP 401 with
www-authenticatenaminginvalid_tokenand the resource-metadata URL · retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/2273f645-4b1d-4842-a52f-c0032296ccad (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Sybill
- Tools
- 5
- Domain
- mcp.sybill.ai
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.