Visme MCP server

Create an editable Visme presentation from Claude. Connect once, then ask Claude for a presentation: Claude writes the slides, the connector imports them into your Visme workspace, and you get a link that opens the project in the Visme editor.

What it does #

You ask Claude for a presentation. Claude writes it as an HTML document, following the layout rules the connector gives it (1280×720 slides, real text, flat colours). The connector converts that HTML into a Visme project with separately editable text and image objects, saves it in the workspace you picked when connecting, and hands back a link that opens it in the editor.

• Three tools. create_presentation starts the import and answers at once. Claude then checks get_task_status until the project is ready and gives you the editor link. cancel_task stops an import that is still running.
• The project is a normal Visme project afterwards. Edit it, share it, apply your brand kit, export it.
• Nothing is generated by Visme on this path. What you import is what Claude made.

Setup in Claude #

From the connectors directory

Available once Visme is listed in Claude's directory. Until then, use the custom connector steps below.

1. In Claude, open Customize → Connectors, find Visme, and click Connect.
2. Sign in to Visme if you aren't signed in already.
3. The Visme consent screen says Claude wants to access to your Visme Account and lists one permission, Write Project, which is the project:write scope. Under Workspace to connect, pick the workspace Claude should create projects in, then click Allow.

As a custom connector

Use this until Visme is listed in the directory. On Claude's Free plan you can add one custom connector.

1. In Claude, open Customize → Connectors, click + Add, then Add custom connector.
2. Name it Visme and paste the server URL:

   https://mcp.visme.co/mcp

   Copy
   Then click Continue.
3. Keep the authentication settings Claude detects. Under OAuth client, keep Use Claude's published identity (Recommended). Don't pick Register automatically: Visme doesn't support it. Click Add.
4. Click Connect, sign in to Visme, pick a workspace on the consent screen, and click Allow.

Claude finds the Visme sign-in by itself: an unauthenticated request gets 401 with WWW-Authenticate: Bearer pointing at https://mcp.visme.co/.well-known/oauth-protected-resource/mcp. Tools are not listed before you sign in. A token that lacks project:write gets 403 with insufficient_scope.

In Claude Code

1. Add the server:

   claude mcp add \
     --transport http \
     visme https://mcp.visme.co/mcp

   Copy
2. In Claude Code, run /mcp, choose visme, and sign in to Visme in the browser window that opens. Pick a workspace and click Allow.

Admin setup for Claude Team and Enterprise

On Claude Team and Enterprise plans, an Owner adds the connector for the organization once (on Enterprise, also anyone whose custom role includes Manage access to Libraries).

1. The Owner opens Organization settings → Connectors, clicks Add, hovers over Custom, and selects Web.
2. Name it Visme, enter https://mcp.visme.co/mcp, and click Continue. Under OAuth client, keep Use Claude's published identity (Recommended). Click Add.
3. Members then open Customize → Connectors, find Visme, and click Connect. Each member signs in with their own Visme account; there is no shared workspace token.

Nothing needs to be enabled on the Visme side. Any Visme account can be connected once the Owner has added the connector in Claude.

ChatGPT and other clients

ChatGPT is coming soon; setup steps will be added here when it is available. Other MCP clients can use the same URL if they support Streamable HTTP and OAuth 2.0 with PKCE, and register with a Client ID Metadata Document. Dynamic client registration is not supported.

Example prompts #

Ask Claude in plain language once you're connected. Claude can write a new deck for Visme, or import one it made earlier in the conversation.

• Make a 5-slide Visme presentation about our Q3 results.
• Import this deck into Visme.
• Send the presentation above to Visme and give me the editor link.
• Turn the slides you just made into a Visme project called "Q3 board update".

Projects always go to the workspace you picked when connecting. To use another workspace, disconnect and connect again.

Tools #

Three tools. create_presentation and cancel_task write to your workspace; get_task_status only reads.

{
  "task_id": "…",
  "status": "pending",
  "stage": "importing",
  "message": "Still working. Check again with get_task_status in a few seconds."
}

{
  "task_id": "…",
  "status": "done",
  "stage": "done",
  "editor_url": "https://dashboard.visme.co/v2/edit/{project_id}",
  "message": "Your presentation is ready."
}

What converts and what doesn't #

The importer turns the HTML into native Visme objects wherever it can, so you can edit the result rather than just look at it. Here is what to expect.

Limits #

• HTML document at most 2,000,000 bytes (about 2 MB).
• At most 2 presentations being created at once per Visme user. A third request gets too_many_in_flight until one finishes or is cancelled.
• No per-import slide cap from the connector. On the Basic plan, only the first 25 slides are kept.
• Each request creates a new project; there is no update-in-place. Only a retry with the same idempotency_key returns the existing task instead of a second project.
• Task status can be checked for 7 days.
• AI credits are not charged for imports.

Troubleshooting #

Headings in code are the exact text the tool returns. Tool errors come back as code: message. A failed import is not a tool error: get_task_status returns status: failed with an error_class.

Authentication

Creating a presentation

Failed imports

Here get_task_status returns "status": "failed" and an error_class.

Data and privacy #

The connector receives your signed-in Visme user id, the workspace you chose, and the title and HTML you send. The HTML is used only to create your project. The connector deletes it once the import service has accepted it, and the import service deletes its copy when the import starts, after one hour at the latest. The task record (title, status, project id) is kept for 7 days so Claude can check the result. Your Visme sign-in token is never passed to the import service.

See also the Visme privacy policy.