> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corunner.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Coda as an MCP Server in Corunner

> Connect Coda as an MCP server in Corunner for memory and structured doc retrieval. Use an API key and a custom server URL to link your Coda workspace.

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.

<CardGroup cols={1}>
  <Card title="Add Coda Server" icon="coda" href="https://app.corunner.ai/integrations?tab=mcp">
    Open the MCP Servers tab in the Corunner web app.
  </Card>
</CardGroup>

## Server Details

| Property | Value |
| - | - |
| Server URL | User-provided (e.g., `https://your-coda-mcp.example.com/mcp`) |
| Authentication | API key |
| Category | knowledge |
| Used for | memory, structured doc retrieval |
| Auth link | [coda.io/account](https://coda.io/account) |

## Connect Coda

<Steps>
  <Step title="Sign in to Corunner">
    Go to [app.corunner.ai](https://app.corunner.ai) and sign in.
  </Step>

  <Step title="Open Integrations">
    Click **Integrations** in the left sidebar.
  </Step>

  <Step title="Select the MCP Servers tab">
    Choose the **MCP Servers** tab.
  </Step>

  <Step title="Find the Coda card">
    Locate the **Coda** card in the grid.
  </Step>

  <Step title="Turn on the Connect toggle">
    The **Connect Coda** modal opens.
  </Step>

  <Step title="Verify the Server name">
    The prefilled name is **Coda**. Rename it if you run multiple instances.
  </Step>

  <Step title="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`).
  </Step>

  <Step title="Click Test URL">
    Confirm the endpoint format is valid and the server responds.
  </Step>

  <Step title="Select the authentication method">
    Prefilled: **API key**.
  </Step>

  <Step title="Paste your API key">
    Enter the API key you generated from your [Coda account](https://coda.io/account).
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Click Connect">
    Corunner saves the configuration and connects to your Coda server.
  </Step>

  <Step title="Confirm connection">
    Confirm a green **Connected** badge and an enabled **Connected** toggle on the **Coda** card.
  </Step>
</Steps>

## 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

<Warning>
  Never enter secrets, tokens, or credentials into the Usage guidance field. It is stored as plain text and visible to all workspace members.
</Warning>

Copy and adapt the following example:

```text theme={null}
Use Coda for structured planning docs and tables such as roadmap trackers, OKR rollups, and vendor lists. Prefer read tables when the user asks about status, owner, or dates; use read docs for narrative sections. Do not read from tables tagged Confidential-HR. Present tabular answers as compact tables with the source doc name.
```

## 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

<Note>
  Create, edit, disconnect, and observation-consent changes are admin-only. Members can view status and capabilities but cannot modify settings.
</Note>

## Manage Observation Consent

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

<Warning>
  Observation is separate from connecting a tool. Only resources listed here are eligible for passive intelligence, and excluded scopes cannot be enabled.
</Warning>

<Note>
  The precise effect on [Memory & Learnings](/admin/memory) for advanced observation modes should be confirmed with the Corunner product team if you plan to depend on it in policy.
</Note>

## Disable or Disconnect

<Warning>
  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.
</Warning>

| Action | Effect |
| - | - |
| Turn off Connected toggle | Opens the **Disconnect Coda?** dialog |
| Confirm Disconnect Coda | Removes connection + credentials + Usage guidance + headers; you can reconnect any time |
| Revoke on provider | Provider invalidates the token; next call fails and card enters error state, prompting reconnect |
| Temporarily disable | Not a separate state today; disconnect and reconnect |
| Delete configuration | Same as Disconnect; there is no separate delete |

## Connect Coda

<CardGroup cols={1}>
  <Card title="Add Coda Server" icon="coda" href="https://app.corunner.ai/integrations?tab=mcp">
    Ready to go? Open the MCP Servers tab and turn on the Coda Connect toggle.
  </Card>
</CardGroup>

## Related

<CardGroup cols={3}>
  <Card title="Integrations Overview" icon="plug" href="/integrations/overview">
    Browse all available integrations and MCP servers.
  </Card>

  <Card title="Memory & Learnings" icon="brain" href="/admin/memory">
    Learn how Corunner builds organizational memory from connected sources.
  </Card>

  <Card title="Governance" icon="shield" href="/admin/governance">
    Review access controls and policies for integrations.
  </Card>
</CardGroup>