How to connect Coda to Muse

Connect Muse to Coda MCP. Duplicate your project tracker document, add a new permission for this doc, and more using natural language, with authentication handled for you.

Coda logoCoda
Api Key

Coda is a collaborative workspace that turns documents into powerful tools for teams. It's designed to boost productivity by combining docs, spreadsheets, and apps in a single platform.

109 Tools4 Triggers

Introduction

Muse is Meta's AI assistant. It can connect to outside tools through custom connectors, which use the Model Context Protocol (MCP).

This guide explains how to connect Coda to Muse using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a custom connector once, then ask Muse to work with Coda in plain language.

Also integrate Coda with

Why use Composio?

  • Cross-app workflows across 1,500+ apps from a single plugin layer.
  • On-demand tool loading so Muse only loads the tools needed for the current task.
  • Programmatic tool calling through a remote workbench for complex, multi-step workflows.
  • Multi-account support so users can connect and switch between multiple accounts for the same app.
  • Shared account access so teams or agents can work through common business accounts and service connections.
  • Managed authentication with OAuth handling, credential storage, and token refresh managed by Composio.
  • Safer credential handling so app credentials stay outside the model context and tool responses.
  • User-level account isolation so actions run against the correct connected account instead of mixing user access.

Connecting Coda to Muse

You add Composio to Muse once as a custom connector, then connect Coda from the chat.

1. Ask Muse to connect to Composio

Start a new Muse chat and send this message. Muse builds the connector and shows a button to add your API key.

bash
Create a Custom Connector for the Composio remote MCP server and connect to it:
- Name: Composio
- Transport: remote streamable HTTP
- URL: https://connect.composio.dev/mcp
- Auth: API key sent in the x-consumer-api-key header
Open the secure credentials store so I can enter the API key there, not in this chat. Then list its tools to confirm the connection works.

2. Copy your API key

Open the Muse page in your Composio dashboard and copy your API key. It starts with ck_.

Don't paste it into the chat. It goes in Muse's secure credentials store in the next step.

3. Add your API key in the secure credentials store

Tap the button Muse shows to open Add custom connector, paste your API key, then tap Add. Muse lists the Composio tools once it connects.

Muse secure credentials store with the connect.composio.dev URL, an API Key field, and the Add button

4. Connect your Coda account

Back in the chat, ask Muse to connect to Coda or give it any Coda task.

For example, ask it to:

  • "Duplicate your project tracker document"
  • "Add a new permission for this doc"
  • "Export the content of the roadmap page"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Muse, and your Coda account is ready to use.

What is the Coda MCP server, and what's possible with it?

The Coda MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Coda account. It provides structured and secure access to your docs, pages, tables, folders, permissions, and Packs, so your agent can create documents, organize content, update table rows, manage access, and export pages on your behalf.

  • Document and page creation: Have your agent create or copy Coda docs, add new pages, review page details, and remove pages or content you no longer need.
  • Table data management: Direct your agent to add or update table rows, inspect specific rows and columns, and delete individual or multiple rows.
  • Workspace organization: Let the agent create folders for projects, remove outdated folders, and delete documents that are no longer needed.
  • Access and permission control: Instruct your agent to review document access settings, grant new permissions, or revoke existing access.
  • Exports and Pack administration: Have your agent start and monitor page exports, create Pack releases, manage Pack makers and categories, and control Pack permissions.

Way Forward

Now that Coda is connected, extend your setup by connecting the other apps you already use every day, so Muse can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single connection, Muse can coordinate multiple tools safely and reliably in one conversation.

Troubleshooting

1. Why doesn't Muse show a button to add my API key?

Muse shows the button only when you ask it to open the secure credentials store.

  • Start a new chat.
  • Send the message from step 1 exactly as written.
  • If Muse asks for the key in the chat, do not paste it. Ask Muse to open the secure credentials store.

2. Why does the Composio connection fail after I add my API key?

The key or the connector settings are not correct.

  • Copy the full key from the Composio dashboard. It starts with ck_.
  • Make sure the URL is https://connect.composio.dev/mcp and the header is x-consumer-api-key.
  • Remove the Composio connector in Muse settings, then do steps 1 to 3 again.

3. Why doesn't Muse use the Composio tools for Coda?

Muse may not pick the Composio connector for the request.

  • Ask Muse to list its Composio tools.
  • Name Composio and Coda in your request, for example: Use Composio to connect to Coda.
  • If it still does not work, start a new chat and try again.

4. Why does Muse ask me to connect Coda again?

Your Coda connection expired or was removed.

  • Open the link Muse gives you and sign in to Coda again.
  • Check that the Coda connection shows as ACTIVE in the Composio dashboard.

5. What do I do if I pasted my API key into the chat?

Treat the key as exposed.

  • Create a new API key in the Composio dashboard and delete the old one.
  • Add the new key in Muse's secure credentials store, not in the chat.
TOOLS & TRIGGERS

Supported Tools and Triggers

Every Coda action and event your agent gets out of the box.

Add a category for pack

Add a publishing category for a given pack.

Add a maker for pack

Add a maker to a Pack.

Add a permission for pack

Create or modify permissions for a given Pack.

Add custom domain

Add a custom domain to a published doc.

Add permission

Adds a new permission to the doc.

Begin content export

Initiate an asynchronous export of page content in HTML or Markdown format.

Content export status

Check the status of a page content export operation.

Copy Document

Creates a copy of an existing Coda document.

Create a new pack release

Creates a new Pack release based on an existing Pack version.

Create a page

Create a new page in a doc.

Create doc

Creates a new Coda doc, optionally copying an existing doc.

Create Folder

Creates a new folder in a Coda workspace.

Create Pack

Creates a new Pack in Coda.

Create Pack Invitation

Create an invitation for a user to access a Pack.

Delete a category for pack

Delete a publishing category for a given pack.

Delete a maker for pack

Removes a maker from a Pack's maker list.

Delete a page

Deletes the specified page.

Delete a permission for pack

Delete user, workspace, or global permissions for a given Pack.

Delete doc

Permanently deletes a Coda doc.

Delete Folder

Tool to delete a folder in Coda.

Delete multiple rows

Deletes multiple rows from a Coda table or view.

Delete pack

Delete a given Pack.

Delete Pack listing draft

Delete the listing draft for a Pack, discarding any unsaved changes.

Delete Page Content

Tool to delete content from a Coda page.

Delete permission

Deletes an existing permission from a Coda document.

Delete row

Deletes the specified row from the table or view.

Deletes a custom domain

Deletes a custom domain from a published doc.

Fetch grouped logs by pack org root ingestion id

Retrieve the grouped logs of a Pack ingestion for debugging purposes.

Fetch ingestion executions for pack

Retrieve the ingestion execution ids of a root ingestion for debugging purpose.

Get acl settings

Returns settings associated with ACLs for this Coda doc.

Get a column

Returns detailed information about a specific column in a Coda table.

Get a control

Returns info on a control.

Get a formula

Returns info on a formula.

Get analytics last updated day

Returns days based on Pacific Standard Time when analytics were last updated.

Get a page

Returns details about a page.

Get a row

Retrieves detailed information about a specific row in a Coda table, including all cell values, metadata (creation/update timestamps), and parent table information.

Get Pack details by ID

Retrieves detailed information about a specific Coda Pack by its ID.

Get a table

Returns details about a specific table or view.

Get detailed listing information for a pack

Get comprehensive public listing information for a Coda Pack.

Get doc analytics summary

Returns aggregated analytics summary data across documents, including session counts, installs, copies, reads, and conversions.

Get doc categories

Retrieves the list of all available doc categories in Coda.

Get folder

Tool to get metadata about a Coda folder.

Get info about a doc

Retrieves comprehensive metadata for a specific Coda document.

Get mutation status

Checks whether an asynchronous mutation operation has been applied to a Coda document.

Get pack analytics summary

Returns summarized analytics data for Packs the user can edit.

Gets custom doc domains providers

Identifies the domain registrar/provider for a given domain name by performing a DNS lookup.

Get sharing metadata

Returns metadata associated with sharing for this Coda doc.

Gets the json schema for pack configuration

Retrieves the JSON Schema that defines the configuration options available for a specific Coda Pack.

Get the difference between two pack versions

Gets information about the difference between the specified previous version and next version of a Pack.

Get the next valid version for a pack

Get the next valid version number for a Pack based on the proposed metadata.

Get the source code for a pack version

Retrieves temporary download URLs for the source code files of a specific Pack version.

Get user info

Returns basic info about the current user.

List available docs

Returns a list of Coda docs accessible by the user, and which they have opened at least once.

List categories for pack

List all publishing categories associated with a specific Coda Pack.

List columns

Returns a list of columns in a table.

List controls

Returns a list of controls in a Coda doc.

List custom doc domains

List all custom domains configured for a published Coda doc.

List doc analytics

Returns analytics data for accessible documents.

List featured docs for a pack

Returns a list of featured docs for a Pack.

List Folders

Tool to list folders accessible by the user.

List formulas

Returns a list of named formulas in a Coda doc.

List makers for pack

List makers for a given pack.

List pack analytics

Returns analytics data for Packs the user can edit.

List pack formula analytics

Returns analytics data for Pack formulas.

List packs

Get the list of accessible Packs.

List page analytics

Returns page-level analytics data for pages within a document.

List Page Content

Tool to list page content.

List pages

Returns a list of pages in a Coda doc.

List permissions

Returns a list of permissions for this Coda doc.

List permissions for a pack

Get user, workspace, and/or global permissions for a given Pack.

List table rows

Retrieves rows from a specific table within a Coda document.

List tables

Returns a list of tables in a Coda doc.

List the pack listings accessible to a user

Get listings of public Packs and Packs created by you.

List the releases for a pack

Get the list of releases of a Pack.

List the versions for a pack

Get the list of versions of a Pack.

List User Pack Invitations

Tool to get pending Pack invitations for the authenticated user.

List workspace roles

Returns a list of the counts of users over time by role for the workspace.

List workspace users

Returns a list of members in the given workspace.

Pack asset upload complete

Notify Coda that the Pack asset upload to S3 is complete.

Pack source code upload complete

Notify Coda that the Pack source code upload to S3 is complete.

Pack version upload complete

Mark a Pack version upload as complete to finalize the Pack version creation.

Patch the system connection credentials of the pack

Patch the system connection credentials of the Pack.

Publish doc

Update publish settings for a doc.

Push a button

Pushes a button on a row in a table.

Register pack version

Registers a new Pack version and obtains a signed upload URL.

Resolve browser link

Given a browser link to a Coda object, attempts to find it and return metadata that can be used to get more info on it.

Retrieve the grouped logs of a pack

Retrieve grouped execution logs for a Pack in a specific Coda document.

Retrieve the information for a specific log

Retrieve detailed information for a specific log entry from a Pack ingestion.

Retrieve the logs of a ingestion

Retrieve the logs of a Ingestion for debugging purpose.

Retrieve the logs of a pack

Retrieve the execution logs of a Pack within a specific document for debugging purposes.

Retrieve the oauth configuration of the pack

Retrieve the OAuth configuration of the Pack for display purpose.

Retrieve the system connection metadata of the pack

Retrieve the system connection metadata of a Pack.

Search principals

Search for users and groups (principals) that a Coda document can be shared with.

Set the oauth configurations of the pack

Set OAuth2 client credentials (client ID, secret, redirect URI) for a Pack.

Set the system connection credentials of the pack

Set the system connection credentials of the Pack.

Trigger automation

Triggers a webhook-invoked automation in a Coda doc.

Unpublish doc

Unpublishes a Coda document, removing it from public access.

Update acl settings

Update access control list (ACL) settings for a Coda document.

Update an existing Pack release

Update the release notes of an existing Pack release.

Update a page

Update properties for a page.

Update doc

Updates metadata for a Coda document, including its title and icon.

Update featured docs for a pack

Create or replace the featured docs for a Pack.

Update Folder

Tool to update folder metadata in Coda.

Update pack

Update an existing Pack for non-versioned fields.

Updates a custom domain

Updates properties of a document's custom domain.

Updates user role

Updates the workspace user role of a user that matches the parameters.

Upload a pack asset

Request a signed s3 URL to upload your Pack asset.

Upload pack source code

Request a signed s3 URL to upload your Pack source code.

Insert/Update Rows in Coda Table

This tool allows you to insert new rows into a Coda table or update existing ones based on specified key columns.

FAQ

Frequently asked questions

Yes. Muse supports custom connectors that use the Model Context Protocol (MCP). Composio connects as one custom connector over remote streamable HTTP at https://connect.composio.dev/mcp, and gives Muse access to Coda and 1,500+ other apps.

Copy it from the Composio dashboard. It starts with ck_. Enter it only in Muse's secure credentials store, never in the chat.

Yes. Composio supports multiple connected accounts for the same app. Give each Coda connection a name, such as work or personal, and tell Muse which one to use.

Tokens, keys, and configuration are encrypted at rest and in transit. Your Composio API key stays in Muse's secure credentials store, not in the chat or the model context. Composio is SOC 2 Type 2 compliant.

Start with Coda.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Coda tool your agent needs.Free to start.

Start building