6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search a company knowledge base and write back to it.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Guru MCP server connects a Guru knowledge base to Claude, ChatGPT and any MCP-compatible agent. It lets an agent search company knowledge, ask a Knowledge Agent for a cited answer across connected systems, retrieve a specific Card — and write back, by drafting a new Card or updating an existing one. Sign-in is OAuth or an email-and-token header.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
permissions field, so the listing gives no signal that two of six tools write.default scope cannot express read without write. Restricting the agent means restricting the Guru account, not the grant.readOnlyHint or destructiveHint annotations were readable. Tool names are Anthropic's; behaviour is Guru's documentation.update_card are undocumented. Guru describes the draft-then-publish flow for its web UI and does not state which half an MCP write performs.prompts/list to confirm what the server actually serves — the empty list is the directory's claim, not our observation.answer_generation can see is set by the Knowledge Agent's connected sources, which an agent Owner or workspace admin controls.Not by itself. Guru documents editing as a two-step flow: an edit auto-saves into a private draft, and a separate publish action makes it live. Guru also keeps revision history with a compare-and-revert option on every Card. Anthropic's directory record carries no permissions label at all, so the agent's write reach is not described there.
The field is absent from the record entirely, not set to read-only. Anthropic's 2026-08-16 snapshot lists six Guru tools including `create_draft` and `update_card`, both of which write into a shared knowledge base, with no permissions string of any kind. Other connectors in the same snapshot do carry one, so this is a missing label rather than a format difference.
Everything the chosen Knowledge Agent is wired to, not just Guru Cards. Guru documents Knowledge Agents as searching across connected sources including Google Drive, Slack, Confluence and Salesforce, then returning a cited answer. One tool call therefore fans out across whichever systems an administrator connected, which makes the agent configuration the real permission boundary.
One, named `default`. We fetched Guru's RFC 9728 descriptor and its RFC 8414 authorization-server metadata on 2026-08-19 and both advertise a `scopes_supported` list whose only member is `default`. There is no read scope separate from a write scope, so a consent screen cannot offer read-only access — approving the connector approves the writing tools too.
Yes, for questions routed through Knowledge Agents. Guru's MCP documentation states those questions appear in the AI Agent Center with the person making the request recorded as the asker, and that they are also tracked in Analytics. Guru separately documents a Quality Log recording every verification event, though that log respects source permissions.
Either works, and the token path is the one that always works. Guru documents an Authorization header carrying your account email and an admin-generated API token joined by a colon. For OAuth, Guru says some popular applications are pre-approved while others need whitelisting, and points clients hitting an invalid redirect_uri error at Guru Support.
No. Guru's documentation states plainly that only HTTP streaming is supported and Server-Sent Events are not. Anthropic's directory records the same transport, streamable HTTP, for this connector. A client configured for the older SSE transport will fail to connect, so point it at the streamable HTTP endpoint instead.
.md suffix) · retrieved 2026-08-19/mcp-appended form returns a byte-identical body, and the /mcp/-inserted form returns 401) · retrieved 2026-08-19www-authenticate: Bearer resource_metadata=…; no tool schemas readable · retrieved 2026-08-19help.getguru.com/robots.txt allows /docs/, disallowing only editing, login and internal API paths; no Content-Signal header is present, and no llms.txt or sitemap.xml is served on that host (both 404, fetched 2026-08-19) · retrieved 2026-08-19Connect Guru once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.