# Guru MCP

> Guru connects your enterprise knowledge base to any AI agent, giving you a single source of truth for company information. Use this MCP to search structured documentation, manage internal wikis, and retrieve verified policies instantly through natural conversation.

## Overview
- **Category:** brain-trust
- **Price:** Free
- **Tags:** wiki, enterprise-search, verified-information, internal-documentation, knowledge-base

## Description

This connector lets your AI client pull answers directly from your organization's core knowledge repository. Instead of digging through multiple departmental folders or outdated shared drives, you ask the agent a question—say, about vacation policy or product specs—and it finds the correct answer card and provides the full content.

It doesn't just search keywords; it understands context across all your verified company cards. You can also use the MCP to manage the knowledge itself: list collections like 'HR Policies' or 'Engineering Specs,' view all available team members, or even create a brand new card when someone writes down an answer they need to save. When you subscribe through Vinkius and connect your client, this MCP becomes the central brain that keeps every single agent talking to the same, verified source of truth.

## Tools

### verify_api_connection
Checks if your connection to Guru is active and working correctly.

### create_knowledge_card
Generates a new knowledge card when you have a piece of information that needs documenting.

### delete_knowledge_card
Removes old or incorrect knowledge cards from the system entirely.

### get_card_details
Fetches all content and extended metadata for a specific, existing card.

### get_collection_details
Retrieves information about a high-level grouping of knowledge cards (a collection).

### list_knowledge_boards
Lists the main board structures used to organize collections by department or project.

### list_knowledge_cards
Retrieves a list of all existing knowledge cards within your workspace.

### list_knowledge_collections
Returns an exhaustive list of every major collection that holds company knowledge.

### list_access_groups
Provides a list of defined user groups within the system, helping map out access rights.

### list_workspace_members
Generates a roster of all team members currently using the knowledge base.

### search_knowledge_base
Runs a powerful search across every card to find answers based on your prompt.

### update_knowledge_card
Modifies the content or metadata of an existing knowledge card when information changes.

## Prompt Examples

**Prompt:** 
```
Search my Guru wiki for 'Remote Work Policy'.
```

**Response:** 
```
Searching knowledge base... I found a card titled 'Global Remote Work Policy' in the HR collection. It was last verified 2 days ago. Would you like the full content?
```

**Prompt:** 
```
List all my knowledge collections in Guru.
```

**Response:** 
```
Retrieving collections... I found 4 active collections: 'Human Resources' (ID: col_123), 'Engineering Wiki', 'Product Roadmap', and 'Sales Playbook'.
```

**Prompt:** 
```
Create a new knowledge card: 'How to setup MCP' in the 'Engineering' collection.
```

**Response:** 
```
Card created! I've successfully added 'How to setup MCP' to the Engineering collection. The card ID is crd_98765 and it is currently in 'Draft' status.
```

## Capabilities

### Searching knowledge across all cards
You can execute deep searches across every knowledge card in your system to isolate specific facts or policies.

### Listing and viewing collections
Retrieve a list of high-level organizational groupings, helping you understand how the company's total knowledge is structured.

### Retrieving specific card content
Fetch the complete details for any single knowledge card, including extended metadata and verification status.

### Managing cards and collections
Create new knowledge cards or modify existing ones when documentation changes. You can also list all available boards and groups to map out your internal structure.

### Auditing user permissions
List specific user groups and team members to verify who has permission to view certain parts of the wiki or knowledge base.

## Use Cases

### Handling an urgent policy question
A customer support agent needs to know the global remote work rules. They prompt their agent, which uses `search_knowledge_base`. The agent finds the 'Global Remote Work Policy' card and provides the full text, noting when it was last verified.

### Onboarding a new product team
An internal operations analyst needs to know which documentation collections are available. They ask the agent to list all collections, and the MCP runs `list_knowledge_collections`, providing immediate access to 'Engineering Wiki' and 'Product Roadmap'.

### Correcting outdated company data
A knowledge manager finds an old procedure in a card. They use the agent to fetch the details, then they use `update_knowledge_card` to correct the steps and ensure it's flagged as verified.

### Checking team access for a project
A lead needs to confirm who can view sensitive financial data. They ask the agent, which runs `list_access_groups`, providing a clear list of user groups and their scope.

## Benefits

- Instead of manually clicking through tabs to find policy details, you simply ask your agent a question. The agent executes `search_knowledge_base` and returns the precise card content immediately.
- You never have to guess where information lives again. You can use tools like `list_knowledge_collections` to get an immediate map of how all company knowledge is grouped by department or product line.
- When policy changes, you don't update a spreadsheet; you use the MCP to `update_knowledge_card` directly in Guru and ensure your agent uses the most current version.
- The ability to list user groups (`list_access_groups`) means your agent can check knowledge permissions before trying to retrieve sensitive data, preventing access errors.
- It gives your AI client a true source of truth. You'll see which cards are verified and when they were last updated by checking the card details via `get_card_details`.

## How It Works

The bottom line is that your AI client reads corporate documentation as if it were plugged directly into its memory.

1. Subscribe to this MCP on Vinkius, then enter your Guru email and API token into your AI client.
2. Tell your agent what you need—for example, 'What is the expense report deadline?'
3. The MCP processes the request by searching all available knowledge cards and sends back a verified answer card.

## Frequently Asked Questions

**How do I start using the Guru MCP with my agent?**
You first need to subscribe to this MCP on Vinkius and provide your Guru API token. Once connected, you can ask your agent any question related to company policy.

**Can the Guru MCP create new documentation cards?**
Yes, if a team discovers new information that needs to be saved, they can use the `create_knowledge_card` tool to generate and document it within the system.

**Does this MCP only search one department's knowledge?**
No. The `search_knowledge_base` tool searches across all your collections, allowing you to find answers regardless of which department originally wrote the documentation.

**If I need to check who can view a specific document, what do I use with Guru MCP?**
Use the `list_access_groups` tool. This lets your agent pull a roster of user groups and helps you verify knowledge permissions before trying to retrieve sensitive data.

**Is this just for reading documents, or can I edit them?**
You can do both. The MCP allows the agent to read content using `get_card_details`, and it also provides tools like `update_knowledge_card` so you can modify the source material.