Tenor MCP: connect coding agents
Connect Codex, Claude, or Cursor to Tenor’s authenticated MCP endpoint. Inspect shared React components and continue with permitted canvas and version tools.
Endpoint and authentication
Tenor’s canonical MCP endpoint is https://tenor.design/api/mcp. It uses HTTP transport and browser-based OAuth authorization with PKCE. Use the connection setup offered by Tenor for your client; no public marketplace installation is implied by this guide.
Authorize the account and permissions needed for the task. Grants are bound to the exact Tenor environment: production credentials do not authorize a staging endpoint, or vice versa. Never paste credentials into a prompt or component source.
Connect your account
Open Settings → Connections for the setup offered for your client. Tenor uses MCP to let supported coding agents work with its tools.
Sign in to the correct Tenor account and grant the permissions needed for the task.
Choose the access you need
Reading shared components, creating imports, and managing canvas work are separate capabilities. A read-only connection does not automatically gain write access.
The mcp:tools scope permits shared-component tools. Importing adds mcp:components:create. Importing into an existing canvas and managing owned canvas work also requires mcp:canvases:manage. Approval of a scope does not turn on component sharing.
Enable Agent access on a component for shared discovery. A connection with canvas-management permission can access the authorized canvas more broadly.
Give the agent a concrete task
Name the component or project and the repository location where it belongs. Describe the behavior, styling, and application patterns to preserve.
When importing work into Tenor, ask the agent to inspect the rendered result. Saving code alone does not verify its appearance.
Use this Tenor settings panel in the repository’s project settings route. Preserve its layout and states, use the existing form primitives, and connect Save to the current settings action. Show me the changes before release.
Discover capabilities before changing work
An agent should call tenor_get_capabilities and inspect the returned support and limits before preparing an import. Self-contained React is supported; arbitrary package-backed builds are currently unavailable.
Use tenor_list_components and tenor_get_component for shared discovery. Authorized canvas workflows use tenor_list_canvases, tenor_get_canvas, and tenor_get_component_history. tenor_get_edit_workspace prepares supported saved work for local editing.
tenor_update_component requires the expected saved version and timestamp. If the source has changed, read the latest canvas/history and reconcile the conflict before retrying. Do not substitute the current time or overwrite blindly.
Ordinary component-management tools do not delete content. A separately consented embedded editor can edit and delete owned canvas content when configured; existing MCP grants do not gain that permission. MCP does not change sharing. Inspect the rendered result and verify interactions after an edit.
If the connection needs attention
Check the connected account and permissions when an agent cannot find a component. Reconnect if the client requests a permission required for the task.
You can also use Copy for AI or Download .tsx from Share to continue manually.