Skip to main content
The Coda MCP server lets Corunner agents access structured planning docs and tables in your Coda workspace. This page covers how to connect it, configure usage guidance, verify capabilities, and manage the connection.

Add Coda Server

Open the MCP Servers tab in the Corunner web app.

​
Server Details

​
Connect Coda

1

Sign in to Corunner

Go to app.corunner.ai and sign in.
2

Open Integrations

Click Integrations in the left sidebar.
3

Select the MCP Servers tab

Choose the MCP Servers tab.
4

Find the Coda card

Locate the Coda card in the grid.
5

Turn on the Connect toggle

The Connect Coda modal opens.
6

Verify the Server name

The prefilled name is Coda. Rename it if you run multiple instances.
7

Enter the Server URL

Coda does not have a Corunner-managed URL. Paste the URL of your Coda MCP server (for example, https://your-coda-mcp.example.com/mcp).
8

Click Test URL

Confirm the endpoint format is valid and the server responds.
9

Select the authentication method

Prefilled: API key.
10

Paste your API key

Enter the API key you generated from your Coda account.
11

Click Advanced (Optional)

Expand the Advanced (Optional) panel. It contains two fields: Custom headers (add 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 you enter to every tool description sent to the agent, so it directly influences when the agent picks Coda over another source.
12

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 docs or tables 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.
13

Click Connect

Corunner saves the configuration and connects to your Coda server.
14

Confirm connection

Confirm a green Connected badge and an enabled Connected toggle on the Coda card.

​
Configure Usage Guidance

Usage guidance tells Corunner when, how, and what boundaries to apply when agents use this server. The six purposes are:
  1. When to use it
  2. What to do with it
  3. Which resources are permitted
  4. Which resources require approval
  5. What must not be accessed
  6. How to present results
Never enter secrets, tokens, or credentials into the Usage guidance field. It is stored as plain text and visible to all workspace members.
Copy and adapt the following example:

​
Verify the Connection

After connecting, the Coda card shows:
  • A green Connected status pill next to the name
  • An enabled Connected toggle
  • Connected to <workspace> with a relative timestamp (e.g., “2 minutes ago”)
  • A <N> capabilities button that expands into the capability list

​
Capabilities

The Coda server exposes the following tools:
  • read docs
  • read tables

​
Check Connection Health

Click the Test connection icon (Wi-Fi glyph) on the Coda card to run a live probe. A green check means the endpoint is reachable and credentials are valid. A red warning means the probe failed. If the test fails:
  • Open Edit configuration to refresh your API key or update the Server URL

​
Edit Configuration

Click the Edit configuration icon (settings glyph) on the Coda card. Admins can update:
  • Server name
  • Server URL
  • Authentication method and credentials
  • Custom headers (under Advanced)
  • Usage guidance
Create, edit, disconnect, and observation-consent changes are admin-only. Members can view status and capabilities but cannot modify settings.
Click the Observation consent icon (brain glyph) to open the consent drawer and configure what Coda resources Corunner can observe for organizational memory. Observation is separate from tool connection: it controls whether Corunner passively reads resources into memory, while capabilities (tools agents can call) are unaffected.
  • Mode: Disabled / Shadow / Active
  • 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 observation 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 tokens should also be revoked from the provider account if you want to eliminate them entirely.

​
Connect Coda

Add Coda Server

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

Integrations Overview

Browse all available integrations and MCP servers.

Memory & Learnings

Learn how Corunner builds organizational memory from connected sources.

Governance

Review access controls and policies for integrations.