coda-mcp-readonly
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Coda API key. You can generate one from your Coda account settings. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| coda_list_documentsB | List or search available documents |
| coda_list_pagesC | List pages in the current document with pagination |
| coda_get_page_contentB | Get the content of a page as markdown |
| coda_peek_pageA | Peek into the beginning of a page and return a limited number of lines |
| coda_resolve_linkB | Resolve metadata given a browser link to a Coda object |
| coda_list_tablesB | List tables in a document |
| coda_list_columnsB | List columns in a table |
| coda_list_rowsB | List rows in a table with optional filtering and sorting |
| coda_get_rowA | Get a single row from a table |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
The tools are mostly distinct, but coda_get_page_content and coda_peek_page serve similar purposes—both retrieve page content with slight differences in format and length. This overlap could cause confusion, but all other tools clearly target different resources or actions.
All tool names follow a consistent coda_ prefix followed by a verb_noun pattern (e.g., list_documents, get_page_content, resolve_link). The naming is uniform, using snake_case throughout, making it easy to predict tool functions.
With 9 tools, the server is well-scoped for a read-only Coda API. Each tool serves a clear purpose in reading documents, pages, tables, and rows, without unnecessary bloat or missing essential operations.
For a read-only server, the tool surface covers the core lifecycle of reading Coda objects: documents, pages, tables, columns, and rows. Minor gaps exist, such as no separate tool to fetch a single column or table metadata, but these can be worked around with existing list endpoints.