By Ira Bodnar, Ryze AI · Updated · Test record: what was and was not run
Quick answer
The main way to connect Microsoft Copilot to Framer is the Ryze AI connector. Microsoft's pages show no Copilot chat window with a field for an MCP address, so the connector goes onto an agent: connect your Framer project in Ryze AI with its project URL and an API key, then on a Copilot Studio agent add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool with OAuth 2.0 and Dynamic discovery. The agent then holds 3 Framer tools, 1 read, 1 write and 1 delete, which cover CMS collections and publishing.
- In Framer open Site Settings, go to General and create an API key under API Keys
- In Ryze AI open Integrations, click Connect on the Framer card, paste the project URL and the key, then pick a CMS collection
- In Copilot Studio switch to the classic experience, open your agent, then Tools, Add a tool, New tool, Model Context Protocol
- Enter the server details, pick OAuth 2.0 with Dynamic discovery, sign in to Ryze AI, add the tool and ask about your CMS in the test chat
Microsoft Copilot to Framer at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector: a hosted MCP server that a Copilot Studio agent takes as a tool. A Microsoft 365 Copilot declarative agent can take it as an action, a route not yet confirmed for Ryze AI |
| Server address | https://connector.get-ryze.ai/mcp, the same for every user |
| Where it goes in Copilot | On an agent. Classic experience: Tools > Add a tool > New tool > Model Context Protocol. New experience: Build tab > Tools > Add > Model Context Protocol (MCP). No chat window has a documented field for it |
| Sign-in | Copilot signs in to Ryze AI with OAuth 2.0 and Dynamic discovery. Framer is joined once inside Ryze AI with a project URL and an API key, so no Framer key is typed into Copilot |
| Framer tools | 3: 1 read, 1 write and 1 delete |
| Can the agent change the site | Yes, in CMS collections: the write tool creates and updates items and publishes the site, and the delete tool removes items. Pages, layouts, custom code and redirects are outside the tools |
| Other data in the same chat | Other platforms connected in the same Ryze AI workspace are served by the same URL |
| Copilot plan | Microsoft's MCP pages name none. A Copilot Studio trial cannot publish an agent, and the Copilot Studio for Teams plan lacks generative orchestration and Power Platform connectors |
| Ryze AI price | SEO Starter is $129 per month with a 3-day free trial. Adding the connector costs nothing; the Framer tools need an active plan or trial |
| Framer's own option for Copilot | Framer MCP at https://mcp.framer.com/mcp, free during preview. Framer's pages name other assistants and no Microsoft product, so a Copilot Studio sign-in to it is untested |
| Last tested | Nothing was run through the connector against Framer and nothing was run inside a Microsoft product. Microsoft pages read November 14, 2026, Framer pages read November 15, 2026 |
Before you start
- A Copilot Studio agent or a Microsoft 365 Copilot declarative agent. This is a builder task, usually done by an agent maker or admin in a work or school tenant. Microsoft says Copilot Studio is open to all Microsoft 365 users for creating agents and actions. A Copilot Studio trial lets you create and test agents but cannot publish them, and Microsoft asks for a work or school account to sign up for it.
- A Copilot Studio plan that carries MCP. Microsoft documents that MCP access in Copilot Studio relies on Power Platform connectors, and its licensing page marks Power Platform connectors and generative orchestration as not available in the Copilot Studio for Teams plan. No Microsoft sentence says whether MCP tools run on the Teams plan, so test before you promise it to anyone.
- A Framer project and a Framer API key. Create the key in Site Settings > General > API Keys. Framer says a Server API key acts as the user who created it and works for one project only, so create it while signed in as a member whose role can do what you want the agent to do. Framer lists no scopes for a key.
- At least one CMS collection in the project. Ryze AI asks you to pick a collection after you paste the key, and publishing needs a collection the key can reach.
- A Ryze AI workspace on a plan or free trial. SEO Starter is $129 per month with a 3-day free trial and covers Content Plan articles that publish into a Framer CMS collection, up to 90 per billing cycle. Annual billing takes 30% off the first year. Connecting the connector is free, and the Framer tools need an active plan or trial.
How to connect Microsoft Copilot to Framer
Two steps happen in Framer and Ryze AI, three in Copilot Studio, and the last is your first question. The connector URL is the same for every user.
Create a Framer API key
Open the project in Framer, open Site Settings with the settings icon at the top right, go to General and scroll to API Keys. Create a key and copy it. Also copy the project URL from the address bar of the Framer editor. It must contain the 20-character project id; the address of the published site does not work.
Connect Framer in Ryze AI
In Ryze AI open Integrations, click Connect on the Framer card, paste the project URL (or just the project id) and the API key, then click Continue. In the window that opens, pick the CMS collection under Choose a Collection and click Save. Do this before you add the connector to Copilot.
Open the agent and start a new MCP tool
These steps are for the classic experience (the standard harness). New agents from the Copilot Studio home page run on the Microsoft Copilot harness, so switch first: select the three dots at the bottom of the home page side bar, then Open classic experience, which lasts for the session. Open your agent and go to its Tools page. Select Add a tool, then New tool, then Model Context Protocol in the Create new section. The MCP onboarding wizard opens.
Fill in the server details and choose the sign-in
Server name: Ryze AI. Server description: a plain note on what the tools do, for example Reads and edits Framer CMS collections and publishes the site. Microsoft says the agent orchestrator uses this description to decide when to call the server. Server URL: https://connector.get-ryze.ai/mcp. Set the authentication type to OAuth 2.0 and the OAuth type to Dynamic discovery, which is meant for servers that support dynamic client registration, so no client ID, secret or callback URL is typed. Select Create, then Next.
https://connector.get-ryze.ai/mcpCreate the connection and add the tool
On Add tool, select Create a new connection and complete the Ryze AI sign-in, or pick an existing connection. Microsoft's page stops at that button and does not show the sign-in window, and this step was not run for this guide. Then select Add to agent.
Ask about your CMS in the test chat
Open the agent's test chat and try: List the CMS collections in my Framer project and show the fields of the blog collection. Copilot Studio turns on all of the server's tools by default, so decide before you publish the agent whether framer__write and framer__delete should stay on.
The Ryze AI help center page for Framer covers the Framer side of the connection. There is no Ryze AI help center page for Microsoft Copilot.
Sources: Microsoft, connect an existing MCP server to an agent, Microsoft, switch between experiences, Ryze AI Framer guide. Microsoft pages checked November 14, 2026.
Microsoft 365 agents and other routes
Microsoft 365 Copilot declarative agent
If your colleagues work in Microsoft 365 Copilot and not in Copilot Studio, the same URL can ride in a declarative agent as an MCP action. Microsoft documents this route in its Agents Toolkit walkthrough. It was not run for Ryze AI.
- In Visual Studio Code open Microsoft 365 Agents Toolkit, version 6.12.0 or later, and select Create a New Agent/App, then Declarative Agent.
- Select Add an Action, then Start with an MCP Server, and enter https://connector.get-ryze.ai/mcp.
- Choose OAuth with dynamic registration, then pick a project location and an agent name.
- In the Accounts pane sign in to Microsoft 365 and confirm that Custom App Upload Enabled and Copilot Access Enabled show, then select Provision in the Lifecycle pane.
- At m365.cloud.microsoft/chat open the agent, whose name ends in dev, ask a question and select the sign-in button when Copilot asks.
Microsoft says Agents Toolkit sets a new MCP plugin to dynamic tool discovery, so Copilot reads the server's tool list at run time and you add no tools by hand. Sideloading needs Upload custom apps switched on by an admin in the Teams admin center. For dynamic registration Microsoft also requires that the authorization server issues a client secret, which was not checked for Ryze AI. The first time the agent uses the plugin, Copilot asks the person to allow or cancel. After that, tools that only read do not ask again, and tools that change data do.
Other places Microsoft accepts an MCP address
Microsoft documents more places that accept an MCP address than the two above. Each changes who does the setup and how sign-in works.
| Route | What Microsoft documents |
|---|---|
| Copilot Studio, new experience (Microsoft Copilot harness) | Open the agent, go to the Build tab, select Tools, then Add next to the search bar, then Model Context Protocol (MCP). The Add MCP server page asks for a name, a description, the server URL and an authentication choice. Microsoft's page for this flow is labeled preview and does not list its sign-in choices, so this guide does not say that it offers Dynamic discovery. |
| Microsoft 365 admin center, custom federated connector | An admin goes to Copilot > Connectors > Gallery, creates a new connector and enters a base URL. The sign-in choices are Microsoft Entra SSO, OAuth 2.0 with a client registered by hand, or no authentication. Dynamic client registration is not among them, and the Ryze AI facts name no fixed client ID and secret, so this route is not confirmed for Ryze AI. |
| Plugin package or Agent 365 CLI | A developer can name a remote MCP server in a plugin package manifest, or register it with the Agent 365 CLI for admin approval. Both are developer routes that were not checked against the Ryze AI connector. |
| Copilot chat window and personal Copilot | No Microsoft page shows a field in a Copilot chat window for typing an MCP address. Personal Copilot at copilot.com lists four fixed connector services and documents no way to add your own. |
Copilot and MCP: the facts in one table
| Topic | What Microsoft's documentation says |
|---|---|
| Where servers are added | On an agent: the Tools page in Copilot Studio, Add an Action in Agents Toolkit, or the Connectors gallery for admins |
| Transports | Copilot Studio supports Streamable only. SSE support ended after August 2025 |
| Sign-in choices in Copilot Studio | None, API key (header or query parameter) or OAuth 2.0 with Dynamic discovery, Dynamic or Manual |
| Who signs in | Each person signs in to the server with their own account. A Copilot Studio tool uses end user credentials by default, and maker-provided credentials is the other choice |
| Tool approval | Copilot Studio turns on all tools of a new MCP server. Microsoft 365 declarative agents ask on first use and before tools that change data |
| Tools per agent | With generative orchestration the standard harness takes up to 128 tools per agent, and Microsoft suggests 25 to 30. Each MCP server counts as one tool |
| Admin controls | A Power Platform data policy on connectors also governs the MCP server. In the Microsoft 365 admin center, Agents > Tools > Registry can block a server |
| Local servers | No field for a command that starts a server on your computer. Every route takes an HTTPS address that Microsoft's service can reach |
Sources: Microsoft, build MCP plugins, Microsoft 365 Copilot extensibility prerequisites, Microsoft, custom federated connectors, Microsoft, plugins overview, Microsoft, add tools to an agent, Copilot Studio licensing. Checked November 14, 2026.
Claude and ChatGPT
The same connector URL works in other MCP clients, and your Framer project stays connected once in Ryze AI. Guides for Framer:
Claude
Add https://connector.get-ryze.ai/mcp as a custom connector under Customize > Connectors, pick the workspaces and start a new chat. How to connect Claude to Framer.
ChatGPT
Add the same URL as an app under Settings > Apps, pick the workspaces and start a new chat. How to connect ChatGPT to Framer.
Framer access and scope
Two sign-ins are involved, and each limits what the agent can reach.
- Which Framer project
- The project whose URL and key you pasted into Ryze AI. A Ryze AI workspace holds one Framer connection, and a connection link is refused while one already exists.
- Which Framer permissions apply
- Framer says a Server API key authenticates as the user who created it. That user's role in the project therefore matters. Framer does not state on its Server API pages whether a key made by a member without Deploy permission can publish, so check this before you rely on it.
- What Copilot does first
- Copilot Studio turns on every tool of a new MCP server. Nothing waits for your click unless you switch the tools off or build a declarative agent, where Copilot asks before tools that change data.
Access behind each action
Framer API keys have no scopes. The table lists what Ryze AI documents for each kind of action and what Framer ties it to.
| Action in Ryze AI | Framer access |
|---|---|
| List collections, read a collection's fields and items, read one item | framer__read, through the key of the connected project |
| Create items or update them in place by slug or id | framer__write, through the same key |
| Publish the site so CMS changes go live | framer__write. Framer says only members with Deploy permission can publish straight to the live site when staging is off |
| Remove items by id | framer__delete. A publish afterwards makes the removal live |
| Edit pages, layouts, components, custom code or redirects | Not covered by the Ryze AI tools |
The Framer API key behind the connection
The connection is a Framer Server API key plus the project URL. Framer describes the key this way, and the table sets that against what the Ryze AI tools use.
| Item | What Framer says | With Ryze AI |
|---|---|---|
| Key type | Framer Server API key, created in Site Settings > General > API Keys | Pasted once into Ryze AI |
| Who it acts as | The user who created the key | That user's role limits the agent |
| Project | Bound to one specific project | One Framer connection per Ryze AI workspace |
| What the key could reach | The Server API shares the Plugin API's abilities: CMS sync, publishing, canvas changes and project settings | The Ryze AI tools use only CMS read, write, delete and publish |
| Scopes or read-only keys | Framer's quick start describes none | Not offered, so the key cannot be narrowed from the Framer side |
Not included in the Ryze AI tools: Framer pages, layouts, components and canvas edits, custom code, redirects, localization, branches and project settings. The Framer app card in Ryze AI mentions pages, custom code and redirects, yet the agent tools cover CMS collections and site publish only.
Sources: Framer Server API quick start, Framer Server API reference, Framer member roles and permissions. Checked November 15, 2026.
Removing access
To take Framer away from a Copilot Studio agent, open its Tools page in the classic experience, hover over Ryze AI, select the three dots and Delete. To cut Framer off from Ryze AI, open the Framer card, click View, and disconnect with the trash icon. The Framer pages read for this guide do not describe deleting or rotating an API key, so this guide does not give steps for it.
What Copilot can do in Framer
The Ryze AI connector exposes 3 Framer tools: 1 read, 1 write and 1 delete. Writes and deletes are separate tools, so a Copilot agent can be set up to treat them differently.
| Tool | Type | What it does |
|---|---|---|
| framer__read | Read | Reads the connected Framer site's CMS: lists collections, a collection's fields, its items, or one item with its field data. |
| framer__write | Write | Creates or updates CMS items in a collection, matched by slug or id, or publishes the site so changes go live. |
| framer__delete | Delete | Removes CMS items from a collection by id. A publish afterwards makes the removal live. |
Some limits apply in every client. The tools work only with CMS collections and site publish. Publishing needs at least one CMS collection in the project that the API key can access. The published site address does not work as the project URL.
In Copilot Studio, a new MCP server arrives with every tool turned on (Allow all), and Microsoft does not describe a confirmation prompt for MCP tools there. To keep a person in the loop, turn Allow all off and switch off framer__write and framer__delete in the server's tool list on the Tools page, or use a declarative agent, where Copilot asks on first use and before tools that change data. Separately, the Ryze AI chat has a Tool approvals picker that starts on Skip all approvals; you can switch it to Approve write & delete or Manual approve in the message box, and article publishing follows Publishing mode under SEO > Preferences > Publishing, which is Automatic by default.
Limits in numbers
| Limit | Figure or rule | Source |
|---|---|---|
| CMS collections per Framer project | Basic 2, Pro 10 and then $40 per 10 up to 40. Free plan projects 10. Enterprise is custom. | Framer pricing |
| CMS items per Framer project | Basic 1,000, Pro 2,500 and then $20 per 10,000 up to 40,000. Enterprise is custom. | Framer pricing |
| Pages per Framer site | Basic 30, Pro 150 and then $20 per 100 up to 700. Free plan 1,000. | Framer pricing |
| Server API rate limit | None published. Four Framer developer pages give no request quota. | Server API FAQ |
| Server API cost | Free during open beta. Framer says it will likely charge per use with a monthly free allowance. | Server API FAQ |
| Server API cold start | The first commands after a cold start take a second or two. | Server API FAQ |
| Partial failures | Framer says the Server API is not transactional, so a run can fail part way through. | Server API FAQ |
| Ryze AI Content Plan | Up to 90 articles per billing cycle and up to 3 a weekday on SEO Starter. | Ryze AI plan facts |
| Tools per Copilot Studio agent | Up to 128 with generative orchestration in the standard harness. Each MCP server is added as one tool. | Microsoft, add tools to an agent |
| Transport in Copilot Studio | Streamable only. | Microsoft, connect an existing MCP server |
Sources: Framer pricing, Framer Server API FAQ, Microsoft, add tools to an agent. Checked November 15, 2026 and November 14, 2026.
First 3 prompts to run
Nothing was run through the connector against Framer for this guide, so no prompt below has a real result. Each one lists the tool it uses and what the tool is documented to return.
1. List collections and learn the field names
List the CMS collections in my Framer project, then show the fields of the blog collection so I can use the right field names later.
Tools used: framer__read
What comes back: The collections of the project and the fields of the one you named. Nothing is changed.
2. Find items with an empty description
Read the items in my blog collection and list the ones whose description or SEO field is empty. Show the slug of each.
Tools used: framer__read
What comes back: The items with their slugs, with the empty fields marked. The agent reads the items and checks the fields, so the field names depend on your collection. Nothing is changed.
3. Update one item by its slug, then publish on request
Read the item with the slug my-post-slug, change its description to the text I give you, and show me the field before and after. Do not publish yet.
Tools used: framer__read, framer__write
What comes back: A read of the item, then an update in place because the slug already exists. Changes go live only after a separate publish, which you can ask for as the next step.
The second and third prompts need your own collection and slugs. Replace the names with yours, and check the item in Framer before you ask for a publish.
10 jobs to hand to a Copilot agent
Ten jobs to hand to a Copilot agent with the Ryze AI tool, each matched to its tool. None was run from Copilot or against a Framer project for this guide. The ones that change the site need a tool you chose to leave on.
| Job | Ask the agent | Tool | Works on the default connection |
|---|---|---|---|
| List collections | List every CMS collection in the Framer project. | framer__read | Yes |
| Learn the fields | Show the fields of the blog collection. | framer__read | Yes |
| List items | List the items in a collection with their slugs. | framer__read | Yes |
| Read one item | Read the full field data of one item before I edit it. | framer__read | Yes |
| Find gaps | Find items whose description or SEO field is empty. | framer__read | Yes |
| Create an item | Create a new item, such as a blog post, in a collection. | framer__write | Yes. Changes go live only after a publish |
| Update in place | Update an existing item by its slug. | framer__write | Yes. It reads the item first |
| Rewrite a field | Rewrite one field across several items, for example meta descriptions. | framer__write | Yes. It reads the items first |
| Publish | Publish the site so the CMS changes go live. | framer__write | Yes. Ask for it as a separate step |
| Remove old items | Remove outdated items by id, then publish. | framer__delete | Yes. It finds the ids with the read tool and publishes with the write tool |
4 ways to connect Microsoft Copilot to Framer
Four ways can bring a Framer project to a Copilot agent. This guide uses the first, the Ryze AI connector, as the main way: one hosted address that a Copilot Studio agent takes as a tool, with Framer joined by a key you paste into Ryze AI once. The others were checked on the dates in the Sources line. None of the four was run from a Microsoft product.
| Way | Runs where | Setup in Copilot | What it reaches in Framer | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted. One address for every user | A Model Context Protocol tool on a Copilot Studio agent with OAuth 2.0 and Dynamic discovery, or an action in a declarative agent | CMS collections, fields and items, to read, create, update and remove, plus a site publish. Pages, code and redirects are outside it | SEO Starter is $129 per month with a 3-day free trial |
| Framer MCP (Framer's own) | Hosted by Framer at https://mcp.framer.com/mcp, Streamable HTTP, OAuth with a Framer account | The same Server URL field on an agent. Framer's pages name ChatGPT, Codex, Claude, Claude Code, Cursor, Grok Bot and VS Code, and no Microsoft product, so whether Copilot Studio finishes the sign-in is untested | Pages, layouts, components, supported project settings and the CMS, with the permissions of the signed-in Framer account. It can publish when asked. Localization is not available at launch | Free during preview on the plans Framer lists. Your AI usage follows the agent's plan or credits |
| Composio, Framer toolkit | Hosted | A custom MCP server at https://connect.composio.dev/mcp. Composio's pages show setup for ChatGPT and other clients and none for Microsoft Copilot | 156 Framer tools listed: CMS collections and items, pages, components, code files, branches, redirects, locales, publish and deploy. It uses your Framer API key | The free plan stops at 10,000 tool calls a month. Standard is $18 per seat per month |
| Tommy's MCP (Unframer), Framer Marketplace plugin | A plugin that must stay open in Framer, with a bridge server at mcp.unframer.co | A URL that carries a user id and a session secret. The docs list Cursor, Claude, VS Code with GitHub Copilot and Codex, and no Microsoft Copilot product | 22 tools listed, including CMS reads and writes, page creation, styles and React component export, for the project that is open | No price shown for the plugin. The page says it is not an official Framer plugin |
With a hosted way your Framer content passes through that vendor, and Microsoft says a Power Platform data policy applies to any MCP server added to Copilot Studio. Framer MCP signs in as you, so it can reach more of the project than a Ryze AI key does, within your own permissions.
Options that do not fit this job
- Framer External Agents (@framer/agent). A local command line bridge and skills for Claude Code, Codex, Cursor and similar tools. Microsoft's pages show no field for a command that starts a server on your computer, so it does not fit a Copilot agent. Framer says it still supports it and that Framer MCP is now the recommended route.
- Local open-source servers. One repository builds Framer plugins and does not read or edit a site. Another runs a Node process with the Server API, and its package was not found in the npm registry on November 15, 2026. Both need a command, which Copilot has no field for.
- Zapier MCP. Zapier has no Framer app page, so it has no direct Framer actions. The page returned HTTP 404 on November 15, 2026.
- The Framer Server API on its own. It runs over a persistent WebSocket, and Framer's FAQ says a REST layer has to be built on top for HTTP use. It is a route only if you build a service in front of it.
Which one to pick
Ryze AI is the best way to connect Microsoft Copilot to Framer for CMS content work that an agent maker sets up, with one caveat: the tools cover CMS collections and publishing only, so page layouts, components, custom code and redirects need another route. Framer MCP is the better fit when an agent should work on pages and layouts, and the first thing to test if your Copilot Studio tenant accepts its sign-in, because Framer documents that server for other assistants and not for Copilot. Composio makes sense when your team already uses it for other apps. The Unframer plugin suits a person who keeps Framer open all day.
Sources: Framer, getting started with Framer MCP, Framer, what you can do with Framer MCP, framer.com/mcp, Framer External Agents, Framer Server API FAQ, Composio Framer toolkit, Composio pricing, Tommy's MCP on the Framer Marketplace, Unframer MCP docs, Zapier Framer page, ericpjtsai/framer-mcp-server, Sheshiyer/framer-plugin-mcp, Ryze AI Framer guide. Checked November 15, 2026 and November 14, 2026.
Framer, Copilot and MCP: dates that matter
| Date | What happened |
|---|---|
| May 29, 2025 | Microsoft announced general availability of MCP in Copilot Studio, with a streamable transport. SSE stayed in public preview at that point. |
| August 2025 | Copilot Studio stopped supporting SSE for MCP. Streamable is the only supported transport. |
| December 15, 2025 | Microsoft announced general availability of MCP support in declarative agents for Microsoft 365 Copilot. |
| February 12, 2026 | Framer introduced the Server API, free during open beta. |
| July 2026 | Copilot Studio news listed adding an MCP server as a tool for agents on the Microsoft Copilot harness, as a preview. |
| September 2, 2026 | Microsoft's blog said workflows and MCP servers can be added as tools on the harness now called the Microsoft Copilot harness. Microsoft's how-to page for that flow still carried a preview label on November 14, 2026. |
| October 22, 2026 | Framer introduced Framer MCP on its updates page. Framer's pricing page lists it as a preview that is free. |
| October 27, 2026 | Microsoft 365 Copilot release notes said admins can create custom MCP connectors in the Microsoft 365 admin center. |
| October 30, 2026 | Framer's help articles on getting started with Framer MCP and on what you can do with it were last updated. Localization is not available in Framer MCP at launch. |
| November 4, 2026 | @framer/agent 0.0.48 was published, the newest version on November 15, 2026. |
Sources: Microsoft Copilot blog, May 29, 2025, Microsoft, connect an existing MCP server, Microsoft 365 Developer Blog, December 15, 2025, Copilot Studio what's new, Microsoft Copilot blog, September 2, 2026, Microsoft 365 Copilot release notes, Framer updates, Server API, Framer updates, Framer MCP, @framer/agent on npm. Checked November 14, 2026 and November 15, 2026.
How this guide was tested
This guide is built from Microsoft's and Framer's own pages and from the Ryze AI facts for the Framer integration. No call was made to Framer through the connector, so there are no tested reads or sample results here.
| What was done | What it gave |
|---|---|
| Microsoft's documentation | Copilot Studio, Microsoft 365 Copilot, Agents Toolkit and admin pages were read on November 14, 2026. The steps above follow them. |
| Framer's documentation | Framer MCP help articles, the pricing page and the Server API pages were read on November 15, 2026. |
| The connector address and sign-in details | The connector's two OAuth discovery files were requested once each on November 14, 2026 and answered. No client was registered and no sign-in was started. |
| The Framer tools | The names framer__read, framer__write and framer__delete come from the Ryze AI facts, which took them from the app source. No workspace had Framer connected, so the tool list was not seen live. |
| Search demand | Search Console returned no queries for Framer between August 15 and November 12, 2026, so the FAQ uses the question wording of the target searches. |
Not run for this guide: every step inside Copilot Studio, Microsoft 365 Copilot, the Microsoft 365 admin center and Agents Toolkit. No agent was created, no server was added, no sign-in was done and no tool was called from a Microsoft product. No Framer test project was connected, so no read, write, publish or delete was run and no error message was captured. For that reason this guide has no table of tested reads and no table of exact error messages.
Copilot and Framer errors and fixes
No error message was captured for this guide, so the entries below are problems the documentation and the Ryze AI facts lead to, not messages seen in a test.
- Ryze AI does not appear when I look for the tool
- Ryze AI was not found on Microsoft's public MCP server lists, and the in-product lists were not opened. Use New tool, Model Context Protocol and type the address yourself instead of searching the MCP tab.
- I cannot find New tool or the Model Context Protocol option
- New agents open in the new experience, where the path is Build > Tools > Add > Model Context Protocol (MCP). The steps in this guide are for the classic experience. Switch with the three dots at the bottom of the home page side bar.
- The Framer tools do not appear after I add the server
- Connect Framer in Ryze AI first, then add the server again or start a new test chat. Microsoft says tool changes on a server show up dynamically, and says that after a republished custom connector new or renamed tools can take about 12 to 24 hours.
- Dynamic discovery fails at sign-in
- Microsoft documents Dynamic discovery for servers that support dynamic client registration, and the Ryze AI server does, but the sign-in was not run from Copilot. Try the Dynamic or Manual OAuth type, or ask Ryze AI support.
- Framer does not accept the project URL
- Paste the URL from the address bar of the Framer editor. It must include the 20-character project id. You can paste only the id. The address of the published site does not work.
- Publishing fails or finds no collection
- Publishing needs at least one CMS collection that the API key can access. Check the key in Site Settings > General > API Keys, and that the member who made it has the right role.
- The agent cannot edit a page or change the layout
- The Ryze AI Framer tools cover CMS collections and site publish only. Framer MCP reaches pages and layouts, with your Framer account's permissions.
- Framer is already connected elsewhere
- A Ryze AI workspace holds one Framer connection, and a connection link is refused while one exists. Open the Framer card, click View, disconnect with the trash icon and connect again.
- The tools reply that a subscription is required
- The Framer tools need an active Ryze AI plan or free trial. Start the trial, then retry.
- Nobody else can use the agent
- A Copilot Studio trial can create and test agents but not publish them. Publishing needs a standalone license, and an admin may need to allow the connection under a Power Platform data policy.
Terms on this page
- MCP
- The Model Context Protocol, an open standard for connecting AI applications to outside systems. Copilot Studio, Claude and ChatGPT support it.
- MCP server
- A program that offers tools over MCP. The Ryze AI connector is an MCP server that runs on Ryze AI's side, so there is nothing to install.
- Declarative agent
- An agent for Microsoft 365 Copilot that you build with Agents Toolkit and give actions. An MCP server can be one of its actions.
- Harness
- The engine a Copilot Studio agent runs on. The standard harness is shown as the classic experience, and the Microsoft Copilot harness is the new experience.
- Framer CMS collection
- A set of structured content items in a Framer project, such as blog posts. Each item has an id, a slug and its field data.
- Slug
- The text identifier of a CMS item. The Ryze AI write tool matches items by slug or id, so an item with an existing slug is updated in place.
- Framer API key
- A Server API key made in a project's Site Settings, General section. It acts as the user who created it and works for one project.
Sources: modelcontextprotocol.io, Framer CMS documentation. Checked November 15, 2026.
Frequently asked questions
How do I connect Copilot to Framer?
Create a Framer API key in Site Settings > General, connect Framer in Ryze AI with the project URL and the key, then add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool on a Copilot Studio agent with OAuth 2.0 and Dynamic discovery. Sign in to Ryze AI and add the tool to the agent.
Is there a Framer connector for Copilot?
Microsoft's and Framer's pages list no ready-made Framer connector for Microsoft Copilot, so the route is an MCP tool you add to an agent. The Ryze AI connector at https://connector.get-ryze.ai/mcp has 3 Framer tools for CMS collections and publishing. Framer's own server and Composio are other options, untested in Copilot.
Is there a Framer MCP server for Copilot?
Yes, two kinds. Framer runs its own at https://mcp.framer.com/mcp, signed in with OAuth, free during preview, but Framer's pages name no Microsoft product for it. The Ryze AI connector gives a Copilot Studio agent 3 Framer tools for the CMS. You add either with the Server URL field of an MCP tool.
What is the Framer MCP server URL?
Framer's own server is at https://mcp.framer.com/mcp and uses Streamable HTTP with OAuth. The Ryze AI connector uses https://connector.get-ryze.ai/mcp, the same for every user, and you connect Framer inside Ryze AI with a project URL and an API key.
Which should I use, Ryze AI or Framer MCP?
Use the Ryze AI connector for CMS content jobs that an agent maker sets up, and Framer MCP when the agent must work on pages, layouts and components. Framer MCP signs in as you, so it reaches more, and its sign-in with Copilot Studio is untested. Both can sit on one agent.
Can Microsoft Copilot edit my Framer pages?
Not through the Ryze AI tools, which cover CMS collections and site publish only. Framer says Framer MCP can edit layouts and components, and Framer's pages name no Microsoft product for it. The External Agents route needs a local command, which Copilot has no field for.
Can Copilot create or update Framer CMS items?
Yes, through framer__write, which creates items or updates them in place when the slug or id exists. Changes go live only after a publish, which you can ask for as a separate step. Copilot Studio turns on all tools by default, so switch the write tool off if you want read-only access.
Can Copilot delete Framer items?
Only through the separate framer__delete tool, which removes items by id. A publish afterwards makes the removal live. In Copilot Studio you can switch that tool off in the server's tool list, and a declarative agent asks before tools that change data.
Can I type the MCP URL into the Copilot chat window?
No Microsoft page shows such a field. An MCP address goes on an agent in Copilot Studio, in a declarative agent built with Agents Toolkit, or in a custom connector made by an admin. Personal Copilot at copilot.com lists four fixed connector services.
Which Copilot plan do I need?
Microsoft's MCP pages name no plan. Copilot Studio is open to all Microsoft 365 users, a trial cannot publish agents, and the Copilot Studio for Teams plan lists Power Platform connectors and generative orchestration as not available. Declarative agents need an admin to allow custom app upload.
Do I need a Framer plan or an API key?
You need an API key from the project's Site Settings, under General and API Keys, and at least one CMS collection. Framer's Server API is free during open beta, and Framer MCP is listed as free during preview. Framer's plans cap CMS collections and items per project.
Can I connect more than one Framer project?
Not in one Ryze AI workspace. A workspace holds one Framer connection, and a connection link is refused while one exists. To switch projects, click View on the Framer card, disconnect with the trash icon and connect the other project.
Why do the Framer tools not show up in Copilot Studio?
Connect Framer in Ryze AI before you add the server, then start a new test chat. If the tools still do not show, check that the connection was created and the tool was added to the agent. Microsoft says tool changes can take about 12 to 24 hours to show after a republished custom connector.
How much does it cost to connect Copilot to Framer?
Adding the connector costs nothing, but the Framer tools need an active Ryze AI plan or free trial. SEO Starter is $129 per month with a 3-day free trial, Paid Ads is $89 per month, Agency is $279 per month and Shopify CRO is $1,499 per month. Annual billing takes 30% off the first year. Microsoft bills Copilot Studio use separately.
How do I disconnect Framer from Copilot?
Delete the Ryze AI tool from the agent's Tools page in Copilot Studio, or disconnect Framer from its card in Ryze AI with the trash icon. Framer's pages read for this guide do not describe deleting or rotating an API key.