Guru MCP Server

The Guru Remote MCP Server is the official, Guru-hosted Model Context Protocol endpoint that connects AI assistants and agent platforms (Claude, Cursor, ChatGPT, and other MCP clients) to an organization's Guru knowledge base. Communication happens entirely over the MCP framework against the streamable HTTP endpoint at https://mcp.api.getguru.com/mcp, so there is nothing to self-host. The repository at guruhq/remote-mcp-server mainly publishes the server.json manifest pointing clients to the hosted server.

The server exposes Guru's Knowledge Agents and Card operations to LLMs while preserving Guru's existing governance: all responses are cited, permission-aware, and respect SSO and workspace permissions. Agents can list available Knowledge Agents, ask natural language questions and receive verified answers, search Cards and connected sources, draft new Cards from a conversation, and suggest updates to existing Cards. Questions and activity are logged in Guru's AI Agent Center with the requester attached.

Authentication is supported via OAuth 2.0 (pre-approved for clients like Claude and Cursor, with other apps available on request) or via API token using an Authorization: Bearer EMAIL:TOKEN header for iPaaS and automation use cases.

Tools

Prerequisites

• An active Guru workspace with Knowledge Agents configured
• An MCP-compatible client (Claude Desktop, Cursor, ChatGPT, etc.)
• OAuth credentials (pre-approved for Claude and Cursor) or a Guru API token from Admin settings

Server endpoint

The server is hosted by Guru. Point your MCP client at:

https://mcp.api.getguru.com/mcp

Protocol: streamable HTTP (Server Sent Events is not supported).

Cursor / Claude configuration

Add the following to your MCP client config (e.g. mcp.json in Cursor under Settings → Cursor Settings → Tools & MCP):

{
  "mcpServers": {
    "Guru": {
      "url": "https://mcp.api.getguru.com/mcp"
    }
  }
}

On first use the client will trigger an OAuth flow to authorize access to your Guru workspace.

API token authentication (optional)

For automation or iPaaS workflows, you can authenticate with an API token instead of OAuth by sending:

Authorization: Bearer EMAIL:TOKEN

where EMAIL is your Guru account email and TOKEN is generated from Guru's Admin → API Access settings.

Notes

• All access respects Guru's existing user, group, and Collection permissions.
• Activity is logged in the AI Agent Center, attributed to the requesting user.
• To call a specific Knowledge Agent, you will need its agentId from the agent's API tab in Guru.

• Let engineers ask "what's our deploy rollback procedure?" from Cursor or Claude and get a cited answer from internal runbooks in Guru.
• Surface customer-facing policies (refund, SLA, escalation) inside a support agent without copying content out of Guru.
• Draft new Guru Cards directly from a chat session, for example summarizing a Slack incident postmortem into a knowledge Card.
• Keep documentation fresh by asking an agent to propose updates to an existing Card with new product details or Q4 roadmap milestones.
• Route questions to a specific Knowledge Agent (e.g. "Sales Enablement Agent") and get permission-aware answers with source citations.

• "List the Guru Knowledge Agents available in my workspace."
• "Ask Guru what our refund policy is for annual subscriptions."
• "Search Guru for 'new hire onboarding checklist' and summarize the top result."
• "Draft a new Guru Card titled 'Q4 Launch Runbook' from the notes I just pasted."
• "Update the 'Product Roadmap' Card with these Q4 milestones."

• Official, Guru-hosted remote MCP server, no self-hosting or local install required.
• Permission-aware: answers respect Guru's existing user, group, and Collection permissions and SSO.
• Returns verified, cited answers via Knowledge Agents rather than raw document dumps.
• Supports both OAuth (for Claude, Cursor) and API token auth for automation and iPaaS use cases.

• Requires an active Guru workspace with Knowledge Agents configured; not useful without an existing Guru deployment.
• OAuth is pre-approved only for a limited set of clients (Claude, Cursor); other apps must be whitelisted by Guru Support.
• Streamable HTTP only, no SSE support, which can limit some older MCP clients.

• Notion MCP server for teams whose knowledge base lives in Notion.
• Confluence MCP integrations (Atlassian Remote MCP) for Atlassian-hosted documentation.
• Glean MCP server for enterprise search across multiple connected SaaS apps.