Connect SheetAI to other apps with MCP

The Model Context Protocol (MCP) is the open standard AI apps use to talk to tools. SheetAI supports it both ways: this page covers connecting other apps to the SheetAI assistant; adding SheetAI as a connector inside another AI app is covered in SheetAI MCP Server. Everything lives under Settings → Connectors.

Open Settings → Connectors → Discover for a curated directory of official servers (Notion, Stripe, Airtable, Linear, Jira and Confluence, monday.com, Supabase, PayPal, Attio, Apollo, PostHog, Mixpanel, Hex, ThoughtSpot, Ramp, Mercury, Neon, Prisma Postgres, Klaviyo, Webflow, Fireflies, Todoist and Egnyte, plus GitHub and Zapier with an API key). Every one-click entry was verified from SheetAI itself; some vendors (Slack, Dropbox, HubSpot, Asana, Canva and others) only allow partner-listed clients today, so they are not listed until they open up. Any other remote MCP server works too: add its URL, choose how to authenticate, and SheetAI lists the tools it offers. The same directory is public at sheetai.co/connectors, with a Connect button on every card. In chat, those tools appear next to the spreadsheet tools, so you can ask for things like “pull this quarter’s open issues from Linear into a new tab”. If a request needs an app you have not connected yet, the assistant shows a Connect card for it in the reply; one click starts the sign-in, and you can ask again as soon as it finishes.

Three ways to authenticate: sign in with OAuth (SheetAI registers itself with the server and sends you to approve access), a fixed API key or header (stored encrypted, sent on every request), or none for public servers. Disable a connector to keep it without exposing its tools; remove it to forget its credentials.

• Tools from a connector are named mcp__app__tool in the chat’s tool cards.
• Tools the server marks read-only are available in Ask mode; everything else goes through the same approval flow as sheet edits.
• Results from a connected app are treated as data, never as instructions.
• Use Refresh after the server adds or changes tools.

SheetAI is also an MCP server, so Claude, ChatGPT, Cursor, VS Code, Claude Code or any MCP-compatible app can list, read, query and edit your spreadsheets. That is set up under Settings → MCP server and has its own guide: SheetAI MCP Server.

Type / at the start of a message to open the command menu. It lists the built-in skills you have added (browse all ten under Settings → Skills → Discover) under tabs for All, Skills, Commands and Prompts, every prompt you saved in the Prompt Library (as /its-title), and any prompts a connected app publishes (as /mcp__app__name). Anything you type after the command becomes its arguments: /analyze the Sales tab, by region.

A skill is a named procedure the assistant follows for the rest of the turn. The assistant also knows the list and can pick one itself when your request matches, so you never have to remember the names. Quick commands live in the same menu: /ask, /act and /plan switch modes, /new starts a chat, /connect opens Connectors, /prompts opens the library.

Type @ anywhere to point at something: a tab (@Sales 2024), a connected app (@Notion, which tells the assistant to use that app's tools), or a resource the app exposes (@Notion:Roadmap, whose content is attached to your message). Use the arrow keys and Enter to pick, Esc to close the menu.

• Every app that connects is listed under “Apps with access”; disconnect one to revoke its tokens instantly.
• Grants are scoped: sheets:read for reading, sheets:write for creating and editing.
• Access tokens expire after an hour and refresh silently; a stolen refresh token that gets replayed revokes the whole grant.
• Only connect servers you trust - anything the assistant reads from them can end up in your sheet.