Guru MCP

Guru MCP connects an assistant to Guru, the company knowledge platform where teams keep verified answers as cards organized into collections and boards. The server is hosted remotely and uses OAuth, so connecting opens a browser sign-in and the agent then inherits the collections and cards that individual account is allowed to see. Permissions are not flattened, and private collections stay private to the people who already had access. On the retrieval side, an agent can search the knowledge base by keyword with filters, and open a specific card to get its full body along with its owner, collection, tags, and verification state. That last part matters, because Guru's model is built on periodic verification by a named expert, so the agent can weigh whether an answer is still trusted rather than treating every document equally. Guru's knowledge agents can also be queried through the same connection, returning a synthesized answer assembled across cards and connected sources instead of a list of documents. The write side covers card drafting and updates, so an assistant can turn a resolved support thread or a decision from a meeting into a draft that a subject matter expert reviews and publishes. Typical users are support, sales enablement, and internal operations teams that want the assistant answering from approved internal documentation rather than from open web content.