I also filled the beta form, looking forward the MCP server beta.
1 Like
Hi , I filled the waiting list doc for beta access to the MCP server what seems like ages ago and still didn’t get access.
1 Like
@Nad I just sent you a DM
1 Like
Same here @Ruggy-Joesten 
1 Like
@Diego_Delfino Sent!
2 Likes
Same Here, please. It is hard to follows Max without MCP. So please 
1 Like
Same here — filled in the waitlist a while back but no access yet. Would love to get into the beta.
We’ve been running the third-party coda-mcp-server with Claude Code for several months now. Works well for table CRUD, row upserts, page content, and formulas — but keen to move to the official MCP for tighter integration and any features the community server doesn’t cover.
@Ruggy-Joesten would appreciate a DM if possible!
1 Like
@Arbor_Advice DM sent!
1 Like
Hey @Oliver_M — just sent you a DM
1 Like
@Ruggy-Joesten would it be possible a dm for the mcp access too?
1 Like
Welcome to the community, @Edrick_Wong! Just sent you a DM.
1 Like
@Ruggy-Joesten I filled out the waitlist form a while ago and haven’t heard anything. Could I please get added?
Also, when will the MCP feature be out of beta? It was announced as “coming soon” nearly 5 months ago — this space is moving fast, and I worry Coda just isn’t keeping up with the competition.
4 Likes
@Ruggy-Joesten I believe I joined the MCP Server waitlist some number of eons ago as well. Is there any way to get my account access to it? I promise to be gentle. 
2 Likes
@Theo_Skye2 Sent you a DM 
2 Likes
Thanks @Ruggy-Joesten , that did the trick.
Hi @Bharat_Batra1 ,
Despite my initial skepticism, I am finding the MCP useful in some cases. Particularly when setting up view of complex sync tables with many sync and coda native columns . I use it to help me list the columns, keep track of progress , flag columns for deletion etc. I use the MCP exclusively from Claude Code CLI (and honestly, I now live in the Claude Code CLI…), so it also has access the code of the backend that is supporting these sync tables, which helps.
After spending some time with the table/view tools, I wanted to flag a few gaps that limit what’s possible:
1. Column reordering — table_view_configure can hide/show columns but can’t set their display order. This means I still need to manually drag columns after programmatically setting up a view.
2. View sorting — There’s no sort configuration on views. My workaround is a formula column (_Order) that users sort by manually, but native sort support would be much cleaner.
3. Placing views on other pages — table_view_add always creates a tab on the base table’s page. There’s no way to programmatically place a view of a table on a different page. This is a common pattern in my docs (e.g., showing a filtered view of a shared table on a domain-specific page).
4. Adding tabs to existing views — Related to the above: if I have a view already placed on another page (created manually), table_view_add can’t add tabs to it — it always resolves back to the base table’s canvas.
5. System column IDs — columnVisibility.hideColumnIds rejects the sync table system column ids (value, synced, connection) with “invalid ID format”. These columns appear in page_read output, so it’d be nice if they could be hidden programmatically too.
What I’d love to see: even just column reordering and sorting would unlock fully programmatic view setup. The rest are nice-to-haves.
Thanks for building this — looking forward to where it goes!
5 Likes
Hey @Nad!
This is exactly the kind of feedback that actually moves things forward. Appreciate you taking the time to lay it out this clearly.
Glad to hear MCP is pulling its weight in your workflow, especially for something as painful as wrangling sync table columns at scale. Pairing it with the Claude Code CLI makes total sense for that use case.
Thanks for calling all of this out, it’s super helpful and a clear snapshot of where table/view tooling starts to get stretched.
I’m flagging all of this for the team. Column reordering and view sorting come up a lot, and I agree that those are the biggest unlocks for making view setup actually programmable. Good to see those are your priorities too.
Good call on the system column ID behavior (#5). That interaction between page_read and columnVisibility.hideColumnIds is worth a closer look on our side.
No promises on timing, but this is getting routed to the right place. Keep it coming.
3 Likes
@Ruggy-Joesten Echoing others; I thought I signed up for the MCP beta ages ago (I totally might not have, though). I re-signed up and wondering if I could get a DM for access. Cheers.
2 Likes
@Nicholas_Wu sent! Check your DMs.
1 Like
All of these gaps can be bridged by using a browser sub-agent in Claude Code. I intentionally baked this into the mcpOS constitution, making Google Antigravity into a complete agentic solution for Coda.
2 Likes
I also sent the form again, looking forward to test it!
1 Like