Connect your AI Agents to Guru in minutes

What is a Guru MCP?

A Guru MCP is a server that exposes your Guru knowledge base to AI agents as callable tools. Your agents can invoke these tools to search and retrieve cards, create new knowledge entries, verify trusted content, browse collections, and more.

Guru offers an official MCP server, but you can also connect to a Guru MCP through a third-party platform like Merge Agent Handler.

How can I use the Guru MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Contextual knowledge retrieval during support: When a support ticket arrives and is tagged with a specific issue type, an agent can search Guru for matching cards, extract the relevant content, and include it in a draft response for the support rep to review

• Automated verification reminders: An agent can query Guru for cards past their verification date, compile a list of card owners and titles, and post a structured reminder to a Slack channel so the right people know what content needs review

• Onboarding knowledge delivery: When a new hire is added to a connected HR system, an agent can search Guru for onboarding-tagged cards in the relevant department collection and deliver them directly to the new employee via email or messaging tool

• Decision capture from project tools: When a discussion in a project management tool reaches a defined decision state, an agent can create a new card in Guru under the appropriate collection, capturing the context, decision summary, and owner for future reference

What are popular tools for Guru's MCP server?

Here are some of the most commonly-used tools:

• <code class="blog_inline-code">search_cards</code> searches Guru cards by keyword or phrase and returns matching results with metadata. Useful for agents that need to surface relevant knowledge in response to a trigger from another system

• <code class="blog_inline-code">get_card</code> fetches a single Guru card by ID, including its full content, tags, and verification status. Call this when an agent needs the complete text of a specific card before generating a response or summary

• <code class="blog_inline-code">create_card</code> creates a new card in Guru under a specified collection or board. Good for workflows that capture decisions, meeting notes, or external context into the knowledge base automatically

• <code class="blog_inline-code">update_card</code> modifies the content, title, or metadata of an existing Guru card. Use this when an agent detects that a card is outdated and needs to reflect new information from another system

• <code class="blog_inline-code">verify_card</code> marks a Guru card as verified, confirming its content is current and trusted. Helpful when an agent needs to close out a review workflow after approval conditions are met

• <code class="blog_inline-code">list_collections</code> returns all collections in a Guru workspace with their names and IDs. Use this when an agent needs to identify the right collection before creating or routing new cards

What makes Merge Agent Handler's Guru MCP server better than alternative Guru MCP servers?

Here is what sets Merge Agent Handler's Guru MCP server apart from alternatives:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Guru, this means internal process documentation, proprietary company knowledge, and sensitive team information can be masked even when the agent has broad card access

• Managed authentication and credentials: Merge stores and refreshes Guru credentials on your behalf. You never pass API tokens directly to an agent or build logic to handle credential rotation

• Real-time observability and audit trail: Every tool call against Guru is recorded with timestamp, tool name, input parameters, and response metadata. Knowledge management and ops teams get a complete log of what the agent read, created, or modified without any custom instrumentation

• Tool Packs and controlled access: Tool Packs let you define exactly which Guru tools an agent can use, and combine them with tools from other connectors in a single scoped MCP endpoint. A retrieval agent gets search and read tools. A content maintenance agent gets update and verify tools. Each is scoped to its specific function

How can I start using Merge Agent Handler's Guru MCP server?

You can take the following steps:

1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).

2. Create a new Tool Pack (a collection of connectors and tools that maps to a use case) and enable the Guru connector. Select which tools to include. Search and read tools cover most knowledge retrieval workflows, while write tools are available if your agent needs to create cards, update content, or manage folders.

3. Add a Registered User to the Tool Pack. This defines the identity context your agent operates under, and Merge generates a unique MCP URL tied to that user.

4. From the Registered User detail page, complete the Guru credential flow. Merge takes over credential storage and refresh from that point forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key under Settings. You will need both to connect your agent.

6. Add the MCP server configuration to your agent or IDE using the MCP URL and API key. Your Guru tools are accessible through that endpoint immediately.