Retable

@Retable show me all rows in the 'Q1 Campaign Tracker' table where status is 'In Progress' and budget is over $5000

Found 7 rows matching your criteria in the Q1 Campaign Tracker table. Each row includes campaign name, owner, budget ($5,200–$12,800 range), start date, and current status. The results show stable column IDs alongside human-readable field names. Note that Retable returns up to 50 rows per request; if your table has more matching rows, you'll need to paginate or refine filters.

This demonstrates read-heavy querying across a workspace table. You'll need the workspace ID and table ID before filtering rows—use List Workspace Projects and Get Table first if you don't have them. The MCP returns raw column IDs, so prompts that reference column titles work best when the AI has already fetched table metadata.

@Retable add a new row to the 'Product Roadmap' table: Feature name 'Dark mode toggle', Priority 'High', Owner 'Sarah Chen', Target Q2 2025

Successfully inserted 1 row into the Product Roadmap table. The new row received ID ret_row_8x3k9m and contains the four fields you specified. Retable assigned a creation timestamp automatically. The row is now visible in all table views and can be referenced by its stable ID in future updates or deletions.

This showcases the Insert Rows tool for write operations. You must match column types exactly—text fields accept strings, but date or number columns will reject mismatched data. If your prompt references column titles instead of IDs, the AI needs to fetch table metadata first, adding one extra request to the workflow.

@Retable review all tables in the 'Marketing' workspace and summarize which ones have rows updated in the last 7 days, then draft a weekly sync email

Scanned 5 tables across the Marketing workspace. Three tables show recent activity: 'Campaign Tracker' (12 rows updated), 'Content Calendar' (8 rows updated), and 'Lead Scoring' (3 rows updated). The 'Budget Allocation' and 'Vendor Contacts' tables had no changes this week. Based on this, here's a draft sync email highlighting the active campaigns, upcoming content deadlines, and new high-priority leads—formatted for your team's Monday standup.

This synthesis example chains List Workspace Projects, Get Table metadata, and Get Rows across multiple tables, then uses the AI to interpret patterns and generate a summary. Be aware that fetching rows from many large tables can hit rate limits quickly. Retable's API doesn't expose row-level timestamps by default, so 'last updated' logic may require custom date columns in your schema.

When Retable beats a full ticketing system for 3-person support

A 3-person support team handling 40 tickets a day can use Retable's Insert Rows and Get Rows tools to log incoming requests in a shared table, tag them by urgency, and pull the next batch without paying for Zendesk. The MCP's 11 tools cover the full CRUD cycle—add columns for new ticket fields, delete rows when spam comes in, update status in real time. The threshold: once you hit 200+ tickets a day or need SLA automation, Retable's manual column management (you call Add Columns every time you want a new field) becomes a bottleneck. Below that line, this MCP turns a spreadsheet into a lightweight ticket system that your AI can read and write without leaving the chat. If your team already lives in Retable for other workflows, this is the fastest path to support triage in Switchy.

Retable for agile teams who hate Jira's weight

A 5-person dev team running two-week sprints can use List Project Tables and Get Table to pull the current backlog, then Insert Rows to add stories during planning and Delete Rows to archive completed work. Retable's column-type system (the Add Columns tool supports text, number, date, select) maps cleanly to story points, assignees, and due dates. The trade-off: Retable has no native burn-down charts or velocity tracking, so if your PM needs those reports, you'll export to a BI tool or stick with Linear. But if your team wants a flexible table they can reshape mid-sprint—adding a "blocked by" column one week, a "customer impact" tag the next—Retable's MCP gives you that control without Jira's 47-click configuration flows. Best for teams under 10 who value speed over process.

When Retable handles registration better than a form tool

A 2-person events team running monthly meetups (50-80 attendees each) can use Insert Rows to log RSVPs as they come in, Get Rows to pull the latest list for name tags, and Delete Columns to strip out fields they no longer need after the event. The MCP's List Workspace Projects tool lets the AI discover which table holds this month's event without hard-coding table IDs. The limit: Retable's API key auth means every team member shares one credential, so if someone leaves, you rotate the key and update Switchy. For a small team that's fine; for a 15-person org with high turnover, you want OAuth. Below that threshold, Retable beats Airtable's per-seat pricing and gives your AI direct write access to the source of truth. If your team already tracks attendees in a table, this MCP closes the loop.