Skip to main content
Guru is an internal knowledge platform. This page shows how to connect Guru to Corunner as an MCP server so agents can search cards and read collections for grounded, verified answers.

Connect with Guru

Open the MCP Servers tab in the Corunner web app.

​
Server details

​
Connect Guru

1
Sign in to Corunner at app.corunner.ai.
2
Open Integrations in the left sidebar.
3
Select the MCP Servers tab.
4
Find the Guru card in the grid.
5
Turn on the Connect toggle. The Connect Guru modal opens.
6
Verify the prefilled Server name (Guru by default; rename if you run multiple instances).
7
Verify the prefilled Server URL. Value: https://your-guru-mcp.example.com/mcp. If Corunner manages the endpoint, the field shows a Managed by Corunner hint and is read-only.
8
Click Test URL to confirm the endpoint format is valid and the server responds.
9
Select the authentication method (prefilled API key).
10
Click Advanced (Optional) to expand it. This panel contains two fields: Custom headers (extra HTTP headers Corunner sends to the server, one key/value pair per row) and Usage guidance (a free-text instruction that tells agents when and how to use this server). Corunner appends the guidance to every tool description sent to the agent, so it directly influences when the agent picks Guru over another source.
11
In the Usage guidance field (placeholder: Tell agents when and how to use this server…), describe when this server should be used, which cards or collections to prefer, what needs human approval, and what must not be accessed. Keep it short and imperative. Max 2000 characters. See the next section for a copyable example.
12
Click Connect.
13
If OAuth is used, Corunner redirects the current tab to the provider’s authorization page. (Skip step for non-OAuth servers.)
14
Review and approve the requested permissions in the provider consent screen.
15
After approval, return to Corunner automatically.
16
Confirm a green Connected badge and an enabled Connected toggle on the Guru card.

​
Configure Usage Guidance

Usage guidance tells Corunner when and how to invoke Guru. A good prompt answers six questions: When should this server be used? What can it do? Which capabilities are permitted? Which require human approval? What must not be accessed? How should results be presented?
Never enter secrets or credentials into the Usage guidance field. Treat it as a policy prompt, not a vault.
Copy and adapt this example:

​
Verify the Connection

After connecting, the Guru card shows:
  • A green Connected status pill on the name row
  • An enabled Connected toggle
  • A Connected to <workspace> meta line with relative time
  • A <N> capabilities button that expands into the capability list

​
Capabilities

  • search cards
  • read collections

​
Check Connection Health

Click the Test connection icon (Wi-Fi glyph, next to the Connected toggle) to run a live probe. A green check means the endpoint is reachable and the API key is valid. A red warning means the probe failed. If it fails, open Edit configuration to refresh the API key or update the Server URL.

​
Edit Configuration

Click the Edit configuration icon (settings glyph) on the Guru card to change:
  • Server name
  • Server URL (only if not managed by Corunner for this server)
  • Authentication method and credentials
  • Custom headers (non-OAuth only, under Advanced)
  • Usage guidance
Creating, editing, and connecting MCP servers is admin-only. Members can view status and capabilities but cannot change settings.
Click the Observation consent icon (brain glyph) to control whether Corunner passively reads Guru resources into organizational memory. Observation is separate from tool connection: scopes with Mode set to Shadow or Active feed memory, while the capability list exposed to agents is unchanged. Each scope has a Mode (Disabled / Shadow / Active) and a Sensitivity (Standard / Restricted / Excluded). Excluded scopes cannot be enabled.
Observation is separate from connecting a tool. Only resources listed here are eligible for passive intelligence, and excluded scopes cannot be enabled.
The precise effect on Memory & Learnings for advanced modes should be confirmed with the Corunner product team if you plan to depend on it in policy.
Changing observation consent is admin-only.

​
Disable or Disconnect

Disconnecting deletes stored credentials for this connection. Provider-side OAuth tokens should also be revoked from the provider account if you want to eliminate them entirely.

​
Connect Guru

Connect with Guru

Ready to go? Open the MCP Servers tab and turn on the Guru Connect toggle.

Integrations overview

Browse all Corunner integrations and connection types.

Memory & Learnings

Understand how Corunner builds organizational memory from connected sources.

Governance

Review policies, access controls, and admin-only settings.