Skip to content

Connect Tenor

Connect Claude, Codex, ChatGPT, Cursor or any MCP client to Tenor, then ask it to build on your canvases.

3 min read

Server URL

Every app connects to the same Tenor MCP server and signs in with your Tenor account in the browser. You never copy a key.

https://tenor.design/api/mcp

Claude

Claude Code

Run this in your terminal. It adds Tenor for every project. Then run /mcp in Claude Code, choose tenor and follow the sign-in in your browser.

claude mcp add --scope user --transport http tenor https://tenor.design/api/mcp

Claude Desktop or claude.ai

In Claude, open Customize, then Connectors. Choose Add, then Add custom connector, and paste this URL. Claude opens Tenor to approve access.

https://tenor.design/api/mcp

Codex

Codex app

Codex installs the Tenor plugin and opens Tenor in your browser to approve the connection.

Install in Codex

Codex CLI

Run these in your terminal. Codex in the terminal and the Codex app share ~/.codex/config.toml, so this connects both. The second command opens Tenor in your browser to approve access.

codex mcp add tenor --url https://tenor.design/api/mcp
codex mcp login tenor

Or edit config.toml

Add this to ~/.codex/config.toml yourself, then run codex mcp login tenor.

[mcp_servers.tenor] url = "https://tenor.design/api/mcp"

ChatGPT

In ChatGPT, open Plugins, choose +, then Add custom MCP server. Paste this URL, choose OAuth and install. ChatGPT opens Tenor to approve access. Whether you can add one depends on your ChatGPT plan and workspace.

https://tenor.design/api/mcp

Cursor

Opens Cursor’s install page in a new tab, which opens Cursor. Cursor asks to install Tenor, then opens Tenor in your browser to approve access. Approve canvas management to edit components in Design Mode.

Add to Cursor

Manual setup

If Cursor isn’t on this device or the button doesn’t open it, add this server yourself: paste it into ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one. Cursor lists it with your other MCP servers in Customize, which opens from the sidebar.

{ "mcpServers": { "tenor": { "url": "https://tenor.design/api/mcp", "auth": { "scopes": [ "mcp:tools", "mcp:components:create", "mcp:canvases:manage" ] } } } }

Other MCP clients

Any MCP client

Add Tenor as a Streamable HTTP server. Clients that support OAuth open Tenor in your browser to approve access.

https://tenor.design/api/mcp

Approve permissions on one screen

The first time an app connects, it opens Tenor in your browser. Sign in, then approve everything on one screen. Reading the components you share is always included. Every other permission is a checkbox that starts unticked, so the app gets only what you tick.

To change what an app can do, connect it again: the screen shows what it has now, and anything you untick is removed. Disconnect an app at any time in Settings › Customize › Connectors.

  • Allow the Tenor editor. Open your private canvases here. Read, create, edit and delete canvas content, save versions, and generate with your Tenor usage. Does not change sharing or billing. You can disconnect at any time.
  • Allow canvas management. Read your canvases, component code and history, including components with Agent access off. Create and rename canvases, move and rename components, and save new component versions. Does not publish, delete, or change sharing permissions.
  • Allow new component imports. Creates a new private canvas with version history. Cannot overwrite your existing components. Imported code runs in the canvas preview when you open it.
  • Allow requests to Tenor's agent. The connected agent can have Tenor's agent read and edit any of your canvases it names, including components with Agent access off: create and edit components, save new versions, and set that canvas's guidance and default library from libraries you already installed. It cannot install or remove libraries or skills on your account. This uses your plan's generation allowance or credits. Does not change sharing or billing.

Try it

Tenor’s own agent builds the components. Your app sends the request, Tenor designs and saves the components on your canvas, and your app reads back the reply with links to open them. This needs Allow requests to Tenor’s agent and uses your plan’s generation allowance.

Ask your app as you would ask a teammate. Name the canvas, or ask it to make a new one. For example:

  • Make a pricing section on my Tenor canvas “Launch site” with three plans, a monthly and yearly switch, and the Pro plan highlighted.
  • List my Tenor canvases and show me the components on the most recent one.
  • Bring the settings panel from src/components/settings-panel.tsx into a new Tenor canvas so I can refine it there.

Help and privacy

Questions about connecting, or a connection that stopped working? Email us and include the app you’re using.