Summary

A doc stops being something you have to open in order to change.

Markdown goes in and comes out, so drafting and revising a page happens where the writing is already happening, and coda_peek_page keeps a long page from arriving whole when you only need its opening. coda_push_button is the piece an export-and-edit approach cannot reach: it fires the doc's own automation instead of only changing its data.

What it is

A Coda client of 19 tools over documents, pages and tables: page content moves as markdown in both directions, and rows can be listed, upserted, updated, deleted or have a button column pushed.

What you get

Document and page discovery — list or search documents, list pages with pagination, and resolve a browser link back to the object it points at
Page content as markdown: read a whole page, peek at a set number of lines, replace it, or append to it
Page management: create under a parent page, duplicate, rename
Table structure: the tables in a doc, the columns in a table, and rows listed with filtering, sorting and column names instead of IDs
Row writes — read one row, insert or upsert against key columns, update named cells, delete one row or a list of them
Button columns pushed on a specific row, which reaches the automation side of a doc

Requirements

A Coda API key, and the document ID that every page and table call takes. npx on your PATH.

Setup effort

One command plus a key — npx -y coda-mcp@latest, then supply credentials