MCP

The Model Context Protocol (MCP) lets coding agents use tools from outside their sandbox. Every Frontend project comes with MCP servers already configured, and Frontend writes them into Claude Code, Codex and OpenCode before each agent starts. You don’t install or configure anything. (Pi doesn’t support MCP.)

The project’s servers

Server	When it’s added	What agents can do with it
Frontend	Always	Query the project’s database, manage its media library, and generate images and videos
Integrations	When the project connects Shopify, Stripe, Figma or Contentful	Read the store, manage Stripe products and promo codes, read Figma designs, query and edit Contentful entries
Supabase	When the project is linked to a Supabase project	Supabase’s official server for the linked project: database, edge functions, storage, debugging and docs
GitHub	When the team connects GitHub	GitHub’s official server: repositories, issues and pull requests
Your own	When you add them in Settings → MCP Servers	Anything the server offers

See and switch these servers on or off in Settings → MCP Servers.

How servers authenticate

• Frontend and Integrations use the project’s Frontend API key, which every project has in its FRONTEND_API_KEY environment variable. The key identifies the project, so the servers only ever act on it.
• Supabase and GitHub use the access tokens from the project’s connections. Frontend supplies a current token each time an agent starts.
• Your own servers can reference the project’s environment variables in their URL and headers, like Bearer ${LINEAR_API_KEY}.

Credentials stay in Frontend’s configuration; agents call the tools without ever handling the keys behind them.

Using the servers outside Frontend

The Frontend and Integrations servers are regular remote MCP servers, so you can also connect a local agent to them with the project’s API key. See Frontend MCP Server.