Context portability: MCP in Cursor

Most coding assistants still work like a person with sticky notes: you paste in a schema, paste in an error, paste in a screenshot, and hope the model remembers all three. Supabase just documented a cleaner route inside Cursor, where the editor can connect to a live Supabase project through Model Context Protocol and pull context directly from the source. (supabase.com) Model Context Protocol is an open standard Anthropic introduced on November 25, 2024 for connecting artificial intelligence assistants to outside tools and data. The idea is simple: instead of every app inventing its own plug shape, one protocol lets the same assistant talk to databases, file systems, and APIs through a common interface. (anthropic.com) (modelcontextprotocol.io) Cursor is one of the editors that already speaks that protocol. Its own documentation says Cursor can install Model Context Protocol servers, handle authentication, and connect the assistant to outside systems like databases and third-party services from inside the editor. (cursor.com) Supabase is the database side of this story. In its Model Context Protocol guide, Supabase says an assistant connected through the protocol can interact with Supabase projects on a developer’s behalf, and the setup flow lets you choose a platform, a project, and a client such as Cursor. (supabase.com) That changes the basic workflow. Instead of copying a table definition into chat and then copying the answer back into code, a developer can keep working in Cursor while the assistant reads the live project context from Supabase and answers against the current database state. (supabase.com) (cursor.com) Supabase’s open-source server describes the concrete jobs it can do: managing tables, fetching configuration, and querying data. That means the assistant is not limited to the code already open in the editor tab; it can reach into the project’s actual backend surface through a defined tool layer. (github.com) The reason developers care is that modern software work is split across too many windows. A single feature can involve TypeScript in an editor, rows in Postgres, authentication rules in a dashboard, and images in storage, and every manual copy-paste step is a chance to drag stale context into the conversation. (supabase.com) (cursor.com) Supabase is also pushing the protocol from the other direction. Its April 2026 docs now include a guide for deploying your own Model Context Protocol servers on Supabase Edge Functions, using a lightweight framework called mcp-lite, so teams can expose custom tools instead of waiting for a vendor to build them first. (supabase.com 1) (supabase.com 2) There is a catch, and Supabase puts it plainly in the docs: connecting a language model to a live project carries security risks. Its self-hosting guide says the internal Model Context Protocol server does not currently offer OAuth 2.1 authentication and is not intended to be exposed to the public internet, which tells you this is powerful infrastructure, not a toy demo. (supabase.com) So the real news is not that one database company added one integration page. It is that a protocol announced in late 2024 now has a visible path from spec to editor to live backend, which is how standards stop being theory and start becoming part of everyday development. (anthropic.com) (cursor.com) (supabase.com)