Tables API items in Miro MCP accessible OAuth apps

Hi ​@David Greenwood 

thanks so much for taking the time to submit this Wish List idea. Our team will review this and it’s open for votes and comments. 

For those coming across this idea, if you feel this would be helpful for you or your business, please be sure to vote for it and leave a comment about your use case to help our team scope this request!

Thank you again for helping make Miro better!

​@Horea Porutiu Is this a simple change?

Hey ​@David Greenwood 

Great question -- and thanks for the thoughtful Wish List idea.To answer directly: no, this isn't a simple change, but it's a fair request and something we're tracking.Today, the table tools (table_create, table_list_rows, table_sync_rows) were built specifically for the MCP server and use its OAuth 2.1 authentication flow. They aren't currently exposed as standard REST API endpoints available to OAuth apps. Making them available via the public REST API would require building new endpoints with proper scoping, pagination, rate limiting, and documentation -- plus navigating the differences between the MCP auth layer (OAuth 2.1) and the public API auth layer (OAuth 2.0).

We're aware of the gap between what's possible through MCP tools versus the public API, and expanding our public REST API surface area is something we're actively evaluating as part of our post-GA roadmap. I can't commit to a specific timeline, but I've flagged this with the team. If others in the community find this valuable, upvotes and use-case comments here really do help us prioritize. Thanks again for pushing on this, David.

Much appreciated ​@Horea Porutiu and hopefully delete being added soon!