Klue
by Klue
Search your company's curated competitive intelligence, battlecards and win-loss evidence from your AI assistant — and edit cards without leaving the conversation. 24 tools, OAuth sign-in, eight scopes.
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 Klue via MCP
https://mcp.app.klue.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Klue Tools & Capabilities (24)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Seven of the 24 tools have no published description. The five
deals_*tools,klue-content_report_data_gapandklue-content_search_klue_contentappear in Anthropic's directory and nowhere in Klue's own documentation. Their parameters, limits and exact behaviour are unknown to us. - No tool schemas could be read. The endpoint requires OAuth, so parameter-level detail and every safety annotation are unavailable. Nothing on this page derives from a live
tools/list. - Role gates the surface, not just the scopes. Klue restricts win-loss transcripts and reports to admin-level access and card creation to curators and admins, so two accounts with identical grants can see different tools work.
- The
alpha:readandalpha:editscopes are unlabelled. Klue's resource descriptor advertises them and publishes no explanation of what surface they cover. - Deletion recoverability is undocumented.
klue-cards_delete_cardsandklue-cards_delete_battlecardsare named for batch operations and no published source describes whether deleted content can be restored. - No rate limits or metering are published. We found no figures, which is not the same as there being none — treat unbounded throughput as unverified rather than granted.
- The transport is
sse. Anthropic's directory records Server-Sent Events rather than streamable HTTP for this connector, which older or minimal MCP clients may not support. - Klue's own content accuracy is its customers' responsibility. Klue describes a human-curated governance layer in which only published content is visible; the connector inherits whatever that layer has approved, including anything stale.
Frequently asked questions
Does the Klue MCP server let an agent read intelligence about other companies?
It reads your own Klue workspace, which is where competitor material lives. Klue's platform documentation describes building that library from CRM records, call recordings, win-loss interviews, uploaded internal documents and public web sources including competitor sites, pricing pages and news. So the subject matter concerns other companies, but the read surface is your organisation's curated copy, not a live third-party feed.
Can the Klue connector publish or change a battlecard that my whole sales team sees?
Yes. Six of the 24 tools create, update or delete cards and battlecards, and Klue's launch post describes creating cards, updating them after a duplicate check and enriching battlecards through an admin endpoint. A battlecard is the artefact a sales organisation is told to work from, so a single successful edit changes guidance for everyone reading it, not one document for one person.
What OAuth scopes does the Klue MCP server actually request?
Eight, all of them application scopes and none of them identity claims. Six end in read and two end in edit, so the edit surface is narrow and separately grantable. Klue's authorization server advertises 23 scopes in total; the MCP resource asks for only those eight, declining crm:edit, transcript:edit, scim:read, scim:edit, service_write and impersonate among others. Both documents were read live.
Does Klue MCP charge credits or meter tool calls?
No metering is documented anywhere we could reach. Klue publishes no per-call pricing, no credit balance, no rate-limit figures and no quota language for the MCP server across its connector page, launch post and security page. The commercial gate we can see is different in kind: access follows your Klue subscription and your role inside it, so entitlement rather than consumption is what limits you.
Who can use the write tools in the Klue connector?
Curators and admins only, by Klue's own description. Klue's connector page splits access three ways: search and read for all roles, create and manage cards and battlecards for curators and admins, and win-loss transcripts and reports for admins only. Access maps to the roles your team already has in Klue, so an ordinary seller connecting the server gets a read-only surface.
How do I connect Klue to Claude, and do I need an admin?
Add the connector, then complete the Klue sign-in. Klue documents two authentication routes: OAuth 2.0 for individual users connecting their own account, and a personal access token for server-side or internal agent integrations that an admin configures centrally. The OAuth route needs no admin for you personally, but what the connection can reach is bounded by the role your Klue account already holds.
Does third-party content reach my agent's context through Klue?
Yes, by design and in two forms. Klue states its intelligence is built partly from public web sources — competitor sites, pricing pages and news — and win-loss transcripts carry buyer speech verbatim. Both arrive in the model's context as text Klue's own curation layer reviewed but your organisation did not author, which is the ordinary prompt-injection exposure any retrieval connector carries.
Why does Anthropic's directory list a Klue tool the vendor's own guide does not describe?
Seven of the 24 are undescribed in Klue's published skill, and one vendor tool is missing from the directory. The five deals tools, report_data_gap and search_klue_content appear only in the directory, while the guide documents a search_agent_insights that the directory omits. Neither list is complete, so treat the 24 as the connectable surface and the vendor guide as the behaviour reference.
Sources
- Klue, Claude Integration (retrieved 2026-08-21) · retrieved 2026-08-21
- Klue, Introducing Klue's MCP Server (retrieved 2026-08-21) · retrieved 2026-08-21
- Klue, official agent guide published as a Claude Skill (release v1.0.3, 2026-05-01; retrieved 2026-08-21) · retrieved 2026-05-01
- Klue, structured company information for AI assistants (retrieved 2026-08-21) · retrieved 2026-08-21
- Klue, Security (retrieved 2026-08-21) · retrieved 2026-08-21
- Klue, privacy policy (retrieved 2026-08-21) · retrieved 2026-08-21
- Klue, Microsoft 365 integration (retrieved 2026-08-21) · retrieved 2026-08-21
- Klue, on analysing sales call transcripts (retrieved 2026-08-21) · retrieved 2026-08-21
- Live RFC 9728 resource metadata at
mcp.app.klue.com/.well-known/oauth-protected-resource/mcp, authorization server metadata atapp.klue.com/.well-known/oauth-authorization-server, and awww-authenticatechallenge from an anonymous initialize (2026-08-21) · retrieved 2026-08-21 - Anthropic Connectors Directory entry (snapshot 2026-08-16; tool names, tier, endpoint, transport) · retrieved 2026-08-16
- Klue support — support@klue.com
klue.com/robots.txtallows all paths for general user agents and publishes noContent-Signaldirective (retrieved 2026-08-21) · retrieved 2026-08-21
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
- Klue
- Tools
- 24
- Domain
- mcp.app.klue.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.