How to connect VS Code to Framer

Create a Framer API key, link the project once in Ryze AI, add one MCP URL to VS Code, then ask GitHub Copilot Chat to read, update and publish your Framer CMS items.

Your MCP URL
https://connector.get-ryze.ai/mcp

Paste it into VS Code under Chat: Open Customizations, MCP Servers, Add Server. See the steps

See pricing

By Ira Bodnar, Ryze AI · Updated · Connector tested November 19, 2026

Quick answer

The main way to connect VS Code to Framer is the Ryze AI connector. Create an API key in Framer under Site Settings > General > API Keys and link the project in Ryze AI with its URL and that key. Then, with Copilot as the session target, run Chat: Open Customizations, select MCP Servers and add an HTTP server with https://connector.get-ryze.ai/mcp and the server ID ryze. Trust it and finish the Ryze AI sign-in in your browser. Copilot Chat then has 3 Framer tools for CMS items and publishing. Framer also runs its own MCP server at https://mcp.framer.com/mcp and gives VS Code steps for it.

  1. In Framer open Site Settings, General, API Keys and create a key
  2. In Ryze AI open Integrations, click Connect on Framer, paste the project URL and key, then pick a CMS collection
  3. In VS Code run Chat: Open Customizations, select MCP Servers and add an HTTP server with the connector URL
  4. Trust the server, sign in to Ryze AI and ask Copilot Chat which CMS collections your Framer site has

VS Code to Framer at a glance

FactDetail
Main way to connectThe Ryze AI connector, saved in VS Code as one HTTP MCP server called ryze
Server addresshttps://connector.get-ryze.ai/mcp, the same for every user
Where it goes in VS CodeChat: Open Customizations > MCP Servers > Add Server (+), or the MCP: Add Server command. A personal entry lands in Copilot Global, ~/.copilot/mcp-config.json
Sign-in from VS CodeOAuth to Ryze AI in the browser, run by VS Code. No Framer key is typed into VS Code
How Framer is linkedOnce, in Ryze AI, with a Framer API key from Site Settings > General > API Keys and the project URL that holds the 20-character project id. You then pick 1 CMS collection
Framer tools3: framer__read, framer__write (which also publishes the site) and framer__delete
Can Copilot change the siteYes. It can create, update and remove CMS items and publish. A new VS Code session starts on Manual permissions, which show a call that is not auto-approved before it runs
Other data in the same chatThis guide covers the Framer tools only. Tools for other Ryze AI platforms appear when you connect those platforms in the same workspace
Copilot planGitHub lists MCP in every Copilot plan. Business and Enterprise seats also need the MCP servers in Copilot policy, which ships off
Ryze AI priceSEO Starter is $129 per month with a 3-day free trial. Adding the connector is free
Framer's own option for VS CodeFramer MCP at https://mcp.framer.com/mcp, with VS Code steps on Framer's blog. It is free during its preview, per Framer's pricing page
Last testedThe connector address and its sign-in details, on November 19, 2026. No Framer call and no step inside VS Code were run

Before you start

  • GitHub Copilot in a current VS Code. GitHub's MCP article asks for Copilot access and VS Code 1.99 or later. The steps below save the server to Copilot Global, which arrived in VS Code 1.140, so update an older install first. An eligible GitHub account with no plan is enrolled in Copilot Free when it signs in to VS Code.
  • The MCP policy, when Copilot comes from an organization. On Copilot Business or Copilot Enterprise through an organization or enterprise, the MCP servers in Copilot policy must be on, and GitHub ships it off. Copilot Free, Pro, Pro+ and Max are outside that policy.
  • A local folder, with Copilot as the session target. Microsoft's walkthrough asks for AI features on, a local folder open and Copilot picked in the Session Target dropdown before a server is added.
  • A Framer project with a CMS collection. The key has to reach at least 1 collection, otherwise there is nowhere to publish. Keys are made in Site Settings, General, API Keys. Per Framer's quick start, each key acts as the person who made it and belongs to a single project.
  • A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial and publishes Content Plan articles into the Framer collection you choose. Connecting the connector is free, but the Framer tools need any active Ryze AI plan or trial. Annual billing takes 30% off the first year.

How to connect VS Code to Framer with the Customizations editor

The first two steps happen in Framer and Ryze AI, the other four in VS Code. The connector URL is the same for every user.

  1. Create an API key in Framer

    In the Framer editor click the settings icon at the top right to reach Site Settings. Under General, scroll down to API Keys, generate a new key and copy it into a password manager right away.

  2. Connect Framer in Ryze AI

    Create a Ryze AI account or sign in, open Integrations and click Connect on the Framer card. Copy the Project URL from the editor's address bar (it must contain the 20-character project id, and the bare id is accepted too), paste it with the key from step 1 and click Continue. In the window that opens, choose a collection under Choose a Collection and click Save. The address of the published site is refused as the Project URL.

  3. Open the MCP Servers list in VS Code

    Open a local project folder and pick Copilot in the Session Target dropdown, because the editor lists the servers of the selected harness. Run Chat: Open Customizations from the Command Palette, select MCP Servers and choose Add Server (+) in the User group.

  4. Add the HTTP server

    Choose HTTP (HTTP or Server-Sent Events) and enter https://connector.get-ryze.ai/mcp. Type ryze as the server ID. For a personal setup select Global, then Copilot Global. There is no client ID or secret to enter.

  5. Trust the server and sign in

    Read the trust prompt before you accept it, then finish the Ryze AI sign-in in the browser. If no sign-in page opens, use the ellipsis (...) beside ryze in MCP Servers and choose Authenticate. On the Ryze AI page pick the workspace that holds your Framer connection and click Allow connection.

  6. Ask your first question in Copilot Chat

    Open Copilot Chat and ask: Which CMS collections does my Framer site have, and what are the fields of each one? Expand the tool call in the conversation to confirm the ryze server answered. Microsoft's docs point out that a reply with no tool call proves nothing about the connection.

The Ryze AI help center page for Framer covers the Framer side of the connection, and the VS Code MCP servers documentation covers the editor side.

Sources: VS Code MCP servers, GitHub: extend Copilot Chat with MCP, GitHub Copilot plans, Framer Server API quick start, Ryze AI help center page for Framer. Checked November 15, 2026.

Command Palette and config files

The Customizations editor, the guided command and the config files all end in the same server entry. Pick by how you manage VS Code. Framer needs nothing different for any of them, because the project was linked in Ryze AI before VS Code was involved.

Guided flow

Run MCP: Add Server from the Command Palette and answer the prompts with the same URL and the server ID ryze. It skips the Customizations editor.

Portable config file

To write the entry by hand, use the portable format that the Copilot harness reads. It lives in ~/.copilot/mcp-config.json for you alone ($COPILOT_HOME/mcp-config.json when that variable is set) or in .mcp.json at the workspace root. Both start with mcpServers. Every portable HTTP example in Microsoft's reference carries a tools field, so this one does too:

{ "mcpServers": { "ryze": { "type": "http", "url": "https://connector.get-ryze.ai/mcp", "tools": ["*"] } } }

Older VS Code format

The earlier format uses the key servers in .vscode/mcp.json or the profile mcp.json. It belongs to the Local harness, which VS Code 1.146 deprecated on November 11, 2026, with removal announced for February 2027. Copilot harness sessions do not read these files directly. Older tutorials still show this shape:

{ "servers": { "ryze": { "type": "http", "url": "https://connector.get-ryze.ai/mcp" } } }

In the portable entry, ["*"] makes every tool of the server available and leaves approvals in place. Portable files do not support VS Code input variables, envFile or SecretStorage. A workspace .mcp.json is meant to be committed for a team, and with this connector it holds only the address. The Framer API key stays in Ryze AI and never lands in a file you commit.

Limits of VS Code to know

  • The type field sets the transport: http for Streamable HTTP, stdio for a local command and sse for older endpoints that Microsoft labels legacy. The ryze entry uses http.
  • Trusting a server lets it start, signing in gives it access, and approving covers single tool calls. VS Code treats these as three steps.
  • Copilot Global does not sync to your other machines, and a remote host or Dev Container does not read the local file. Add the server on the machine where the session runs.
  • Settings Sync carries the profile mcp.json only, so it leaves both the Copilot user file and .mcp.json files behind.
  • Microsoft's MCP developer guide says VS Code signs in to providers other than GitHub and Microsoft Entra through Dynamic Client Registration or a pre-registered OAuth client. The connector publishes a registration endpoint, yet Ryze AI was not tried inside VS Code for this guide. If the sign-in does not start, email Ryze AI support with the link at the end of the page.

VS Code, Copilot and MCP in one table

TopicWhat Microsoft and GitHub document
Screen for adding a serverChat: Open Customizations opens the Agent Customizations editor. Its MCP Servers page has Add Server (+). The Chat title bar and the Agents window sidebar open the same editor
Files the Copilot harness reads~/.copilot/mcp-config.json (Copilot Global) for one person and .mcp.json at the workspace root for a shared setup, each with a top-level mcpServers object
Legacy files.vscode/mcp.json and the profile mcp.json, with a servers object, kept for the deprecated Local harness
Transportsstdio starts a command, http speaks Streamable HTTP, and sse reaches older endpoints that lack Streamable HTTP
Sign-inWhen a server asks for OAuth, the Copilot runtime hands the sign-in to VS Code, which stores the credentials. Redirects go to http://127.0.0.1:33418 or https://vscode.dev/redirect. The portable format has a flat oauthClientId field for a pre-registered client
Keys and headersHTTP entries accept a headers object whose values can read environment variables as ${NAME}. The portable files ignore input prompts, envFile and SecretStorage, so VS Code never asks you for a key there
Tool approvalNew sessions start on Manual permissions and show the tool name and its inputs for any call that is not auto-approved. The chat input dropdown also offers Assisted permissions, where an LLM judges each call, and Allow all. Autopilot approves every tool
PlanGitHub includes MCP on Copilot Free, Student, Pro, Pro+, Max, Business and Enterprise. Business and Enterprise seats also need the MCP servers in Copilot policy, off by default
Admin controlsallowedMcpServers and deniedMcpServers in enterprise-managed settings match a server by URL, command or name, and a local file cannot lift a block. chat.mcp.access set to none turns MCP off
Managing a serverEach entry in MCP Servers has a toggle and an ellipsis menu with Start, Stop, Enable or Disable, Uninstall and Show Output, plus Authenticate when a sign-in is pending. MCP: List Servers offers the same actions
Tool cap128 enabled tools per chat request. Past that, VS Code answers Cannot have more than 128 tools per request.

Sources: VS Code MCP servers, VS Code MCP configuration reference, VS Code: manage MCP servers, VS Code MCP developer guide, VS Code tool approvals, VS Code agent harnesses, VS Code enterprise AI settings, GitHub: extend Copilot Chat with MCP, GitHub Copilot plans. Checked November 15, 2026.

Other editors and assistants

The same URL works in other MCP clients. The site is connected once in Ryze AI, so nothing changes on the Framer side.

Cursor

Cursor keeps its servers in its own mcp.json, with mcpServers and a url field. The same Ryze AI connection serves it. How to connect Cursor to Framer.

Claude and Claude Code

Claude takes the same URL under Customize, Connectors, and Claude Code takes it from the command line. How to connect Claude Code to Framer.

ChatGPT

ChatGPT takes the same URL as a custom MCP app. Its plan rules differ from Copilot's, so follow its own guide. How to connect ChatGPT to Framer.

Framer access and what a key reaches

Framer never talks to VS Code directly. Ryze AI holds the Framer API key, and VS Code signs in to Ryze AI with OAuth. Four things decide what Copilot Chat can change.

Who creates the key
A person who can open the project's Site Settings makes it under General, API Keys. Framer's quick start says a key acts as its creator, so generate it from an account whose reach you are happy to hand over.
Which project
Framer ties each key to a single project, and a Ryze AI workspace holds one Framer connection. Moving to another project means opening View on the Framer card, using the trash icon and connecting again.
Which collection
Right after the key is accepted you pick the collection that receives published articles. If the key cannot access any CMS collection, publishing has no destination.
What VS Code asks first
A new session starts on Manual permissions, so a CMS edit, a delete or a publish shows its tool name and inputs before it runs, unless you trust the whole ryze server or switch to Allow all or Autopilot.

What Framer allows

Framer's quick start gives no scope list for API keys. This table maps each job to what it needs on the Framer side.

Action in Ryze AIFramer access
List collections, fields and itemsThe project's key, plus a CMS collection that key can reach
Create or update a CMS itemSame key. When the slug already exists the item is updated in place
Remove a CMS itemSame key. The removal reaches the live site after a publish
Publish the siteSame key. This is the step that shows CMS changes to visitors
Edit pages, custom code or redirectsNot available through the Ryze AI tools. Framer's own MCP server covers page work

What a Framer API key reaches, and the part Copilot Chat gets

Framer's quick start describes no scopes, no read-only key and no permission options for an API key, and Framer says its Server API can do what the Plugin API does. The table puts that reach beside the small part Copilot Chat gets through Ryze AI.

Part of FramerWhat Framer says a Server API key can doIn VS Code through Ryze AI
CMSSync CMS collectionsframer__read lists and reads, framer__write creates and updates, framer__delete removes items by id
Publishingpublish() makes a new preview link and deploy() promotes it to productionframer__write can publish the site so changes go live. Ryze AI's documentation does not say which of the 2 Framer calls it makes
CanvasUpdate the canvasNot offered
Project settingsChange project settingsNot offered
BranchesManage branches, a Plugin API feature since version 4.1.0Not offered
Whose rights, which projectActs as the user who made the key, inside the 1 project it is bound to1 Framer project per Ryze AI workspace

Copilot Chat gets none of the following through Ryze AI: page, layout and component edits, custom code, redirects, localization, branches, project settings, or a second Framer project in the same workspace. The Framer card in the Ryze AI app mentions pages, custom code and redirects, yet the 3 tools reach only CMS items and publishing. On publishing rights, Framer's roles page says that with staging off only members with Deploy permission can publish straight to the live site. Its Server API pages do not say how that applies to a key.

Sources: Framer Server API quick start, Framer Server API introduction, Framer Server API reference, Framer developer changelog, Framer member roles and permissions, Ryze AI help center page for Framer. Checked November 15, 2026.

Removing access

To stop access from VS Code, open Chat: Open Customizations, select MCP Servers and disable or uninstall the ryze server from its ellipsis menu. Stop is weaker: it ends the current run and a later request can start the server again. To end Framer access, open View on the Framer card in Ryze AI and press the trash icon. Keys are created under Site Settings, General, API Keys in Framer, but none of Framer's developer pages opened for this guide explains how to delete or rotate one.

What Copilot Chat can do in Framer

The Ryze AI connector exposes 3 Framer tools: 1 read, 1 write and 1 delete. All of them deal with CMS collections and site publishing. Reads, writes and deletes are separate tools, so VS Code can ask about each one on its own.

ToolTypeWhat it does
framer__readReadReturns the connected site's CMS collections, the fields of one collection, its items, or a single item with its field data.
framer__writeWriteCreates or updates CMS items in a collection, matched by slug or id, with an existing slug updated in place. Can also publish the site so changes go live.
framer__deleteDeleteDeletes CMS items from a collection by id. The removal goes live with the next publish.

The tools do not edit Framer pages, custom code or redirects. They work only while the Ryze AI workspace has an active plan or free trial, and publishing needs at least 1 CMS collection that the key can access.

A new VS Code session uses Manual permissions unless a setting or an organization default says otherwise, so a Framer call that is not auto-approved shows its tool name and inputs before it runs. Watch Chat: Manage Tool Approval, because the top-level checkbox for ryze trusts every tool on the server, framer__delete and the publish action of framer__write included. Setting a tool to false in chat.tools.eligibleForAutoApproval keeps it on manual approval, while Allow all and Autopilot approve everything. The Ryze AI chat itself starts on Skip all approvals and can switch to Approve write & delete or Manual approve. Article publishing from a Content Plan follows Publishing mode in SEO > Preferences > Publishing, which is Automatic by default or Manual.

Limits in numbers

Framer's Server API pages publish no request quota, and the Server API's keys are the kind Ryze AI asks for. The rows below are the numbers that do exist: Framer's plan caps on the CMS, its Server API FAQ, Ryze AI's own limits and VS Code's tool cap. That records what the pages say. It is not a statement by Framer that no request limit exists.

LimitFigureSource
Framer Server API requestsNo rate limit or quota published on the introduction, quick start, reference or FAQ pageFramer Server API FAQ
CMS collections in one project2 on Basic. 10 on Pro, then $40 for every 10 more, up to 40. 10 for Free plan projects. Custom on EnterpriseFramer pricing
CMS items in one project1,000 on Basic. 2,500 on Pro, then $20 for every 10,000 more, up to 40,000. Custom on EnterpriseFramer pricing
Fields in a plugin-managed collection30 custom fields, each with an id of up to 64 charactersFramer CMS developer guide
Server API after a cold startThe first commands take a second or two. Framer keeps the instance warm for a set time after a disconnectFramer Server API FAQ
Framer MCP requestsNo quota or rate limit published by FramerFramer MCP page
Framer connections per Ryze AI workspace1. A connection link is refused while one existsRyze AI facts, checked November 8, 2026
Content Plan articles on SEO StarterUp to 90 per billing cycle and up to 3 per weekdayRyze AI facts, checked November 8, 2026
VS Code128 enabled tools per chat requestVS Code tools

Sources: Framer pricing, Framer Server API FAQ, Framer CMS developer guide, Framer MCP page, VS Code tools, Ryze AI help center page for Framer. Checked November 15, 2026.

First 3 prompts to run

These prompts use only what the 3 tools document. What comes back is your own Framer content, so no sample output is shown.

1. Map the CMS

List the CMS collections in my Framer site. For the blog collection, show its fields and the items it holds.

Tools used: framer__read

What comes back: The collection names, the field names of the blog collection and a list of its items, shown in Copilot Chat. Nothing in Framer is changed.

2. Update one item

Open the Framer CMS item with the slug your-slug and show me its field data. Then change its title field to the text I give you.

Tools used: framer__read, framer__write

What comes back: The item's current field data, then a write that updates the item with that slug in place once you approve the call in VS Code. Nothing is live until the site is published.

3. Publish the site

Publish my Framer site so the CMS changes go live.

Tools used: framer__write

What comes back: A publish call that makes the CMS changes public. It runs once you approve it in VS Code, unless the tool is already auto-approved.

Replace the slug and the field names with your own. Read each write, delete and publish call before you approve it in VS Code. None of the 3 prompts was run for this guide.

10 jobs to hand to Copilot Chat

Ten jobs to type into Copilot Chat once the ryze server is running, each with the Ryze AI tool behind it. None of them was run for this guide, since no Framer project was connected in the test. The last column says whether the default connection handles the job: a project linked with an API key and 1 chosen collection, on any active Ryze AI plan or trial.

JobAsk CopilotToolOn the default connection
Collection listWhich CMS collections are in my Framer project?framer__readYes
Field names firstPrint every field of the blog collection so the next edits use the exact names.framer__readYes
Slugs of itemsGive me the items of the blog collection, each with its slug.framer__readYes. Framer item objects carry an id, a slug and field data
Gaps in SEO fieldsGo through the blog items and tell me which ones have an empty description or SEO field.framer__readYes, with the field names of your collection
Add a new postAdd a blog post item to the collection with the title and body I paste here.framer__writeYes. Visitors see it after a publish
Edit by slugRead the item your-slug, then change its title field and leave the other fields alone.framer__read, framer__writeYes, after you approve the write in VS Code
Same field, many itemsRewrite the meta description of the items I list and show old and new text before saving.framer__read, framer__writeYes
Go livePublish the Framer site now.framer__writeYes. This makes the changes public, so ask for it as its own step
Retire old itemsLook up the ids of the items I name, remove them, then publish.framer__read, framer__delete, framer__writeYes. Keep the delete tool on manual approval
Rearrange a pageMove the testimonials section on my home page above the footer.NoneNo. Pages are outside the 3 tools. Framer MCP reaches the canvas

4 ways to connect VS Code to Framer

Four ways can bring a Framer project into Copilot Chat in VS Code. They differ in where they run, how they sign in to Framer and how much of the project the assistant can reach. This guide treats the Ryze AI connector as the main way, because the Framer key stays in Ryze AI, VS Code holds 1 hosted address and reads, writes and deletes stay separate tools. Framer's own MCP server names VS Code on its pages. The other rows were read on their own pages on November 15, 2026. None was set up for this guide.

WayRuns whereSetup in VS CodeWhat it reaches in FramerPrice
Ryze AI connector (the main way)Hosted by Ryze AI at one addressChat: Open Customizations > MCP Servers > Add Server (+), HTTP, ID ryze, saved to Copilot Global, or an mcpServers entry in a portable file. Sign in to Ryze AI in the browser. Framer is linked once inside Ryze AI with an API key and the project URLCMS collections, fields and items to read, create, update and remove by id, plus a site publish. No pages, layouts, custom code or redirectsSEO Starter is $129 per month with a 3-day free trial. The connector is free and any active Ryze AI plan or trial runs the tools
Framer MCPHosted by Framer at https://mcp.framer.com/mcp over Streamable HTTP. No local bridge, and the editor does not have to stay openFramer's blog gives these steps: Chat: Open Customizations, MCP Servers, Add Server, choose HTTP, paste the URL, name it framer, sign in and Allow. Paste the full project link into the chat afterwardsThe canvas, components, supported project settings and the CMS in every project your Framer account can open, with that account's permissions. It publishes only when you ask. No localization at launchFree during the preview, per Framer's pricing page. AI usage follows the agent's own plan or credits, which here means Copilot's
Tommy's MCP (Unframer)A Framer Marketplace plugin that must stay open in the Framer app, bridged by a Cloudflare Worker at mcp.unframer.co. Its page says it is not an official Framer pluginOpen the plugin in the project and copy its MCP address, which carries a user ID and a session secret, so keep it out of committed files. Unframer's docs list manual steps for VS Code with GitHub Copilot22 tools for the open project only, among them CMS reads, item upserts and deletes, new collections and pages, color and text styles and React component export. 1 plugin instance per user and a 5-second timeout per requestNo price for the MCP was confirmed for this guide
Composio's Framer toolkitHosted by ComposioA hosted MCP address, https://connect.composio.dev/mcp, which Composio's Framer pages show for ChatGPT. Composio's pages for VS Code were not opened, so no VS Code setup is described here156 Framer tools, from CMS items to pages, code files, redirects, locales and deploys, authorized with your own Framer API keyFree plan with 10,000 tool calls a month. Standard is $18 per seat per month

Framer options that do not fit this job

  • Framer External Agents (@framer/agent). A local CLI bridge with 2 skills, set up with npx @framer/agent setup. Framer's page names Claude Code, Codex, Cursor, Antigravity CLI and Windsurf and does not name VS Code. It is still the route Framer points to for localization.
  • Framer Server API and Plugin API. The Server API (the npm package framer-api) opens a project from a script you write, with its URL and an API key over a persistent WebSocket, and is free during its open beta. The Plugin API runs inside the open Framer editor. Framer names no assistant for either, so in VS Code they are libraries for your own code, with no MCP server for Copilot Chat to call.
  • Zapier MCP. Zapier has no Framer app: its Framer integrations page returned a 404 on November 15, 2026. The nearest path is the third-party Framer plugin Zapier to CMS, which turns records a Zap posts to its webhook into CMS items.
  • ericpjtsai/framer-mcp-server. An open-source local server with 14 tools for the CMS, pages and publishing, set up with a project URL and an API key. Its README covers Cursor and Claude Code, not VS Code, and the npm registry had no package called framer-mcp-server on November 15, 2026, so the README's npx command has nothing to install.
  • Sheshiyer/framer-plugin-mcp. The most-starred Framer MCP repository a GitHub search found, with 37 stars on November 15, 2026 and a last push on March 21, 2025. It creates and builds Framer plugin projects, is set up for Claude Desktop or Cline, and never reads or edits a Framer site or its CMS.

Which one to pick

Ryze AI is the best way to connect VS Code to Framer for CMS content work, with one caveat: its tools stop at CMS items and site publish, so pages, layouts, custom code and redirects need another route. It is also the route that feeds Ryze AI SEO, because Content Plan articles land in the collection you picked, and the same connection serves Claude, ChatGPT and other MCP clients. When the job is building or reshaping pages from VS Code, add Framer MCP, which signs in with your Framer account and reaches the canvas. VS Code can hold both servers at once, and caps a chat request at 128 enabled tools, so switch off servers you do not use. Tommy's MCP suits a designer who keeps the project open in Framer and wants its style tools and React export. The Ryze AI [Framer tools reference](/framer-mcp) lists the 3 tools in full.

Sources: Framer help: getting started with Framer MCP, Framer MCP page, Framer blog, November 10, 2026, Framer pricing, Framer Marketplace: Tommy's MCP, Unframer MCP connect docs, Composio Framer toolkit, Composio pricing, Framer External Agents, Framer Server API quick start, Zapier MCP, ericpjtsai/framer-mcp-server, Sheshiyer/framer-plugin-mcp, Ryze AI help center page for Framer. Checked November 15, 2026.

Framer, Copilot and MCP: dates that matter

DateWhat happened
April 4, 2025VS Code 1.99, the March 2025 release, came out with MCP server support in agent mode.
August 4, 2025Tommy's MCP, a third-party plugin from Unframer, went up on the Framer Marketplace. Its page shows a last update on October 20, 2026.
February 12, 2026Framer announced its Server API, free while in open beta. Its API keys are the kind Ryze AI asks for.
June 9, 2026The first @framer/agent release, 0.0.0, reached npm. It is the CLI behind Framer External Agents.
August 4, 2026Framer Plugin API 4.1.0 brought publishing calls, among them publish and deploy, and branching.
September 30, 2026VS Code 1.140 added Copilot Global and the workspace .mcp.json as destinations in MCP: Add Server.
October 22, 2026Framer MCP appeared on Framer's updates page. The same day VS Code 1.143 made the Copilot harness the default for new sessions.
October 30, 2026Framer last edited its 2 help articles on Framer MCP.
November 4, 2026@framer/agent 0.0.48 came out. Nothing newer was on npm by November 15, 2026.
November 10, 2026Framer's blog posted MCP setup steps for 8 tools, VS Code among them.
November 11, 2026VS Code 1.146 deprecated the Local harness that reads .vscode/mcp.json, with removal announced for February 2027.

Sources: VS Code 1.99, VS Code 1.140, VS Code 1.143, VS Code 1.146, Framer help: getting started with Framer MCP, Framer MCP page, Framer developer changelog, @framer/agent on npm, Framer Marketplace: Tommy's MCP. Checked November 15, 2026.

How this guide was tested

The only thing run for this guide was a check of the Ryze AI connector's public address on November 19, 2026, from outside VS Code and with no Framer project attached. The 2 rows below are those checks. Everything else comes from pages that were read: Microsoft's and GitHub's documentation on November 14, 2026, then Framer's pages, the npm registry and GitHub on November 15, 2026.

What was runWhat came back
A POST to the connector address with no sign-inHTTP 401 with a WWW-Authenticate header that points to the protected resource metadata, and the message Missing or invalid access token.
The 2 discovery documents on the connector's hostBoth loaded. Between them they name the authorize, token and register endpoints, the authorization code and refresh token grants, the code challenge methods plain and S256, and 2 scopes, mcp:read and mcp:write.

Not run: any call to Framer. No Framer test account was connected in Ryze AI, so framer__read, framer__write and framer__delete were never called, and their names were never seen in a live tool list. No request went to Framer MCP at https://mcp.framer.com/mcp or to the Framer Server API. Nothing was run inside VS Code either: the ryze server was not added to Copilot Global, no trust prompt or sign-in was seen and Copilot Chat sent no tool call. The VS Code steps follow Microsoft's documentation pages dated November 11, 2026 and GitHub's Copilot docs, both read on November 14, 2026. That is why this page has no table of tested calls and no error messages captured from a Framer call.

Errors and fixes

No error message was captured from a Framer call for this guide, because none was run. The only response seen was the 401 from the connector described above. The fixes below follow the documentation of Ryze AI, Framer, Microsoft and GitHub, without a test behind them.

The MCP server does not start in VS Code
On Copilot Business or Enterprise, ask an administrator to enable the MCP servers in Copilot policy, which ships off. Admins can also block a server with deniedMcpServers or turn MCP off with chat.mcp.access set to none, and a local file cannot override either. Check the version too: MCP needs VS Code 1.99 or later and Copilot Global needs 1.140.
The sign-in never opens
Trust and sign-in are separate steps, so trust the server first. Then choose Authenticate from the ellipsis menu of ryze in MCP Servers, or run MCP: List Servers to see its state. Show Output in the same menu opens the log. Email Ryze AI support if it stays stuck.
An older tutorial does nothing
Tutorials built on .vscode/mcp.json target the Local harness. New sessions have used the Copilot harness since VS Code 1.143, which reads ~/.copilot/mcp-config.json and the workspace .mcp.json. Add the server again through Chat: Open Customizations.
Ryze AI says the Framer project URL is not valid
Take the link from the Framer editor's address bar, since it carries the 20-character project id. Pasting the id alone also works. The address of the published site is refused.
The API key is rejected
Generate a fresh key in the same project's Site Settings under General, API Keys and paste it again. A key from another project fails because Framer binds keys to one project.
No collection to choose or publish into
Publishing requires 1 CMS collection that the key can access. Create a collection in Framer, then run the connection again.
A connection link is refused
Only 1 Framer connection fits in a workspace. Remove the existing one with the trash icon behind View on the Framer card, then connect again.
No Framer tools appear in Copilot Chat
If Framer was linked in Ryze AI after the ryze server was added, remove the server, add it again and start a new chat so the tool list refreshes. The Framer tools also need an active Ryze AI plan or trial.
Copilot cannot edit a page or add custom code
These tools stop at CMS collections and publish. Page and layout work belongs to Framer's own MCP server.
An edit does not show on the live site
Writes and deletes stay staged until a publish. Ask Copilot to publish the site or press Publish in Framer.
Framer MCP picks the wrong project
Framer's advice is to give the agent the full project link in the chat.
Framer MCP never finishes the sign-in
If you closed the Framer sign-in window, Framer says to retry the authentication.
Cannot have more than 128 tools per request.
VS Code allows 128 enabled tools in one chat request. Deselect tools or whole MCP servers in the tools picker of the Chat view until the count drops.

Terms on this page

Agent Customizations editor
The VS Code screen opened by Chat: Open Customizations. Its MCP Servers page adds, lists and manages servers.
Copilot Global
The personal MCP destination in VS Code, ~/.copilot/mcp-config.json, read in every workspace.
Framer API key
Made in a project's Site Settings, General section. Framer says it acts as the person who created it and works for that 1 project only.
CMS collection
A group of structured items in a Framer project, blog posts for example. Framer plans cap how many collections and items one project can hold.
Slug
A CMS item's text identifier, kept beside its id and field data. framer__write uses the slug or the id to find the item it updates.
Publish and deploy
In Framer's Server API, publish() creates a preview link and deploy() promotes that link to production. With staging off, only members with Deploy permission can publish straight to the live site.
Framer MCP
Framer's own hosted MCP server at https://mcp.framer.com/mcp. You sign in with a Framer account, and it works on pages, layouts and the CMS with that account's permissions.

Sources: VS Code MCP servers, VS Code MCP configuration reference, Framer Server API quick start, Framer CMS developer guide, Framer help: getting started with Framer MCP, Framer member roles and permissions. Checked November 15, 2026.

Frequently asked questions

How do I connect VS Code to Framer?

Create an API key in Framer Site Settings and connect Framer in Ryze AI under Integrations with the project URL and that key. In VS Code, with Copilot as the session target, run Chat: Open Customizations, select MCP Servers, choose Add Server, pick HTTP, enter https://connector.get-ryze.ai/mcp and the server ID ryze, trust the server and finish the Ryze AI sign-in.

Is there a Framer MCP server for VS Code?

Yes. Framer runs an official server at https://mcp.framer.com/mcp and its blog gives VS Code steps for it, with sign-in through your Framer account. The Ryze AI connector at https://connector.get-ryze.ai/mcp exposes 3 Framer tools for CMS collections and publishing.

What is the Framer MCP server URL for VS Code?

For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every user. Framer's own server is at https://mcp.framer.com/mcp. In VS Code both are added as HTTP servers.

Which Framer server should I use in VS Code?

For CMS items and publishing, or for tying the Framer CMS to Ryze AI Content Plan articles, use the Ryze AI connector, which needs a Ryze AI plan or trial. For page, layout and component work, use Framer's own server, which acts with your Framer account. VS Code can hold both.

How do I add Framer MCP to VS Code?

Framer's blog gives these steps: run Chat: Open Customizations, open MCP Servers, choose Add Server and HTTP, paste https://mcp.framer.com/mcp, name it framer, then sign in to Framer and click Allow. Paste the full project link into the chat afterwards so the agent picks the right project.

Is Framer MCP free in VS Code?

During its preview, yes. Framer's pricing page lists the MCP server as free on Basic, Pro and Enterprise and includes it on the Free plan card. The AI usage itself follows the agent's own plan or credits, which in VS Code means your Copilot plan.

Is there a Copilot connector for Framer?

Framer was not checked against GitHub's list of supported Copilot connectors for this guide. Whatever that list says, you can add Framer by server address, either the Ryze AI connector or Framer's own server.

Which Copilot plan do I need?

Any plan. GitHub's plans tables include MCP on Copilot Free, Student, Pro, Pro+, Max, Business and Enterprise, and GitHub's MCP article asks for VS Code 1.99 or later. Copilot Free, Pro, Pro+ and Max are outside the MCP policy. On Business or Enterprise through an organization, an administrator must enable the MCP servers in Copilot policy, which is off by default.

Can Copilot Chat edit Framer pages with Ryze AI?

No. The Ryze AI tools work with CMS collections and site publish. They do not edit Framer pages, custom code or redirects. Use Framer's own MCP server for that work.

Can Copilot Chat change or delete Framer CMS items?

Yes. With Ryze AI it can create or update items by slug or id and delete items by id, and a publish makes the result visible. New VS Code sessions start on Manual permissions, so a call that is not auto-approved shows its tool name and inputs first. Allow all, Autopilot or a server-wide approval skips that check.

Can Copilot Chat publish my Framer site?

Yes, framer__write can publish the site so CMS changes go live. Framer MCP can publish too, but Framer says it does so only when you ask. Keep the ryze server on manual approval if you want to review each publish.

Why does Ryze AI reject my Framer project URL?

It needs the 20-character project id, which sits in the Framer editor's address bar. The bare id is accepted as well. A published site address is not.

Can I connect more than one Framer project?

One connection per workspace. To change projects, use View on the Framer card in Ryze AI, remove the connection with the trash icon and connect the other project.

How do AI tools publish articles to Framer?

Ryze AI publishes Content Plan articles into the Framer CMS collection you pick after connecting. SEO Starter allows up to 90 articles per billing cycle and up to 3 a weekday. Publishing mode in SEO > Preferences > Publishing is Automatic by default or Manual.

How much does it cost to connect VS Code to Framer?

The connector is free to add. The Framer tools need an active Ryze AI plan or free trial: SEO Starter is $129 per month with a 3-day free trial, and annual billing is 30% off the first year.

How do I disconnect Framer from VS Code?

In VS Code, open Chat: Open Customizations, select MCP Servers and disable or uninstall ryze from its ellipsis menu. To cut the link to Framer, open View on the Framer card in Ryze AI and remove the connection with the trash icon.

Connect Framer to VS Code with Ryze AI

One Ryze AI connector URL carries the 3 Framer tools to GitHub Copilot Chat in VS Code. SEO Starter is $129 per month with a 3-day free trial; annual billing takes 30% off the first year.

Framer MCP server

Need help? Read the Ryze AI help center page for Framer or email Ryze AI support.