How to connect Plasmic to Claude

Connect Claude Web, Desktop and Cowork to Plasmic MCP. Generate global context config for react app, update authentication provider in plasmic project, and more using natural language, with authentication handled for you.

Plasmic logoPlasmic
Api Key

Plasmic is a visual builder for the web that lets teams create and manage web pages and components without code. It's perfect for quickly iterating and launching beautiful sites without waiting on developers.

1 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Plasmic account to Claude via Composio Connect, enabling it to generate global context config for React app, update authentication provider in Plasmic project, add analytics context to Plasmic loader setup, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Plasmic with

Connecting Plasmic to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Plasmic account

Back in Claude, ask it to connect to Plasmic or give it any Plasmic-related task.

For example, ask Claude to:

  • "Generate global context config for React app"
  • "Update authentication provider in Plasmic project"
  • "Add analytics context to Plasmic loader setup"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Plasmic account is ready to use.

What is the Plasmic Claude Connector, and what's possible with it?

The Plasmic MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Plasmic account. It provides structured and secure access to your Plasmic environment, so your agent can generate global configuration snippets, automate design system setup, and streamline your web project workflows on your behalf.

  • Generate global context configuration: Instantly create the configuration snippets needed for your Plasmic loader, saving time and reducing manual errors.
  • Automate design system integration: Let your agent set up and update global contexts for your React providers, ensuring consistent theming and behavior across your app.
  • Simplify onboarding for new projects: Quickly bootstrap new Plasmic projects with pre-configured global settings, making it easy for teams to get started.
  • Maintain and update component contexts: Effortlessly refresh or change global context settings as your design system evolves, keeping your web components in sync.

Troubleshooting

1. Why does Claude not use the Composio connector for Plasmic?

The connector can show as connected, but Claude must use it in each Plasmic conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Plasmic again.

2. Why does Claude show an MCP server error before Plasmic connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Plasmic.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Plasmic.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Plasmic authorization link not work?

The Composio connector is one server. Your Plasmic account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Plasmic connection.
  • Composio creates a fresh Plasmic authorization link.
  • Open that link in your browser and finish the Plasmic sign-in.

4. Why do Plasmic actions fail after they worked before?

The Plasmic connection can expire or lose permission.

  • Ask Claude to inspect the Plasmic connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Plasmic account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Plasmic.
  • If the action still fails with a permission error, check that the connected account has that permission in Plasmic itself.

5. How do I switch to a different Plasmic account?

Claude can manage the Plasmic connection for you.

  • Ask Claude to disconnect or delete the current Plasmic account.
  • Ask Claude to connect Plasmic again.
  • Open the new Composio authorization link for Plasmic.
  • Sign in with the other Plasmic account in the browser.
  • After the account connects, ask Claude to retry the Plasmic task.

6. Why is my Plasmic connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Plasmic connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If Plasmic tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Plasmic.
TOOLS

Supported Tools

Every Plasmic action and event your agent gets out of the box.

Plasmic Global Actions Provider

Tool to generate the globalContexts configuration snippet for Plasmic loader.

FAQ

Frequently asked questions

With a standalone Plasmic MCP server, the agents and LLMs can only access a fixed set of Plasmic tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Plasmic and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Plasmic tools.

Yes, absolutely. You can configure which Plasmic scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Plasmic data and credentials are handled as safely as possible.

Start with Plasmic.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Plasmic tool your agent needs.Free to start.

Start building