Skip to main content
The Custom MCP Server flow lets you register any public Model Context Protocol server with Corunner. This page covers how to add a custom server, configure authentication and usage guidance for agents, verify the connection, and manage or disconnect it later.

Add a custom MCP server

Open the MCP Servers tab and choose Add custom MCP server.

​
Server details

​
Connect Custom MCP Server

1

Sign in

Sign in to Corunner at app.corunner.ai.
2

Open Integrations

Open Integrations in the left sidebar.
3

Select MCP Servers tab

Select the MCP Servers tab.
4

Add custom MCP server

In the MCP Servers grid, click Add custom MCP server (or the equivalent CTA at the top of the tab).
5

Modal opens

The Add custom MCP server modal opens.
6

Enter a Server name

Enter a Server name (for example, “Internal Wiki”). This is the label agents and admins will see.
7

Enter the Server URL

Enter the Server URL. It must be a public https endpoint. The URL cannot be localhost, a private IP, or a link-local address; Corunner rejects those during validation before submission.
8

Click Test URL

Click Test URL. The check validates URL format only; the real handshake happens on submit.
9

Choose authentication method

Choose the Authentication method: None, Bearer token, API key, or OAuth. Non-OAuth methods reveal a token field; OAuth uses the standard MCP OAuth 2.0 dynamic-client-registration + PKCE flow.
10

Click Advanced (Optional)

Expand the Advanced (Optional) panel. Depending on the auth method you picked, it contains: Custom headers (only for None, Bearer token, or API key servers, hidden for OAuth) where you add extra HTTP headers Corunner sends to the server as key/value pairs, and Usage guidance, a free-text instruction that tells agents when and how to use this server. Corunner appends what you enter in guidance to every tool description sent to the agent, so it directly influences when the agent picks this server over others.
11

Enter Usage guidance

In the Usage guidance field (placeholder: Tell agents when and how to use this server…), describe when this server should be used, which tools or resources 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 Add server (or Authorize)

Click Authorize (OAuth) or Add server (None / Bearer token / API key).
13

OAuth redirect

If OAuth is used, Corunner redirects the current tab to the provider’s authorization page.
14

Approve permissions

Review and approve the requested permissions in the provider consent screen.
15

Return to Corunner

After approval, return to Corunner automatically.
16

Confirm Connected badge

Confirm a green Connected badge and an enabled Connected toggle on the Custom MCP Server card.

​
Configure Usage Guidance

Usage guidance tells Corunner agents when and how to use this MCP server. Write it as plain text; it is appended to the system prompt. Good guidance covers six purposes:
  1. When to use the server (what user questions or tasks trigger it)
  2. What the server can do (a short summary)
  3. Which operations are permitted without extra approval
  4. Which operations require approval before running
  5. What must never be accessed or modified
  6. How to present results to the user
Never enter secrets in Usage guidance. It is sent in prompts to the LLM and is not a secure store for tokens, passwords, or keys.
Tailor the example to your own server name, tools, and policies.

​
Verify the Connection

After the server is added, the card shows:
  • A green Connected status pill on the name row
  • A Connected to <workspace> meta line with relative connection time
  • An enabled Connected toggle
  • A <N> capabilities button that expands into the capability list
Capabilities are discovered at connection time from the MCP server itself, so the list shown on the card reflects whatever the server registered. Click the capability count on the card to see the current tools.

​
Check Connection Health

On the connected card, click the Test connection icon (Wi-Fi glyph) next to the Connected toggle. It runs a live probe: green check means the endpoint is reachable and credentials are valid; red warning means the probe failed. If the test fails, open Edit configuration to refresh credentials or update the Server URL.

​
Edit Configuration

Click the Edit configuration icon (settings glyph) on the connected card to change settings. Editable fields include:
  • Server name
  • Server URL (only if not managed by Corunner)
  • Authentication method and credentials
  • Custom headers (non-OAuth only, under Advanced)
  • Usage guidance
Creating, editing, disconnecting, and observation-consent changes are admin-only. Members see status and capabilities but cannot toggle the connection or use the action icons.
Click the Observation consent icon (brain glyph) on the connected card. Observation is separate from tool connection: it controls whether Corunner passively reads resources into organizational memory, while capabilities are unaffected. Scopes have Mode (Disabled / Shadow / Active) and 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.

​
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 Custom MCP Server

Start adding a server

Ready to go? Open the MCP Servers tab and click Add custom MCP server.

Integrations overview

How Direct Connections and MCP Servers fit together.

Notion MCP Server

Connect Notion as an MCP server for page and database access.

Governance

Approval policies and controls that apply to MCP tool calls.