How to Add Eddyter MCP to Claude Desktop and Claude Code

How to Add Eddyter MCP to Claude Desktop and Claude Code

Quick answer: Eddyter's MCP server lives at https://mcp.eddyter.com/mcp. In Claude Desktop, open Settings → Connectors → Add custom connector, paste that URL, and sign in with your Eddyter account. In Claude Code, run claude mcp add --transport http eddyter https://mcp.eddyter.com/mcp, then type /mcp and finish the sign-in. That's the whole setup.

The rest of this guide covers what you get once it's connected, the exact steps for each app, and fixes for the errors people actually hit.

What the Eddyter MCP server does

MCP (Model Context Protocol) is the open standard Claude uses to talk to outside tools. Eddyter ships a hosted MCP server, so you don't install anything locally. No Node process, no Docker, no config file to babysit.

Once connected, Claude can work with your Eddyter account directly through five tools:

That last one is the part developers tend to like most. Want to switch off AI chat and tables before a client demo? You ask Claude. The change reaches every user of your editor right away, with no redeploy.

Before you start

You need two things:

1. An Eddyter account with a license key. Create one at eddyter.com/user/license-key. The free plan works.
2. Claude Desktop or Claude Code. Custom connectors work on Claude's Free, Pro, Max, Team and Enterprise plans. The Free plan is limited to one custom connector, so if you're already using it for something else, you'll need to swap.

Sign-in uses OAuth 2.0. You never paste your license key into Claude. The token Claude receives is scoped to a single Eddyter license key, and the server only sends the tool arguments (for example, "turn off enableComments") plus that token. Your documents, chat history and local files stay out of it.

How to add Eddyter MCP to Claude Desktop

Claude Desktop handles remote MCP servers as custom connectors. Five clicks, roughly.

1. Open Claude Desktop and go to Settings → Connectors. (On some newer builds this sits under Customize → Connectors. Same screen.)
2. Click Add custom connector.
3. Fill in the two fields: Name: Eddyter and Remote MCP server URL: https://mcp.eddyter.com/mcp
4. Leave the advanced OAuth fields empty. Eddyter handles client registration on its own.
5. Click Add, then Connect. A browser window opens. Sign in to Eddyter and pick the license key you want Claude to manage.

Back in Claude, start a new chat and open the tools menu (the slider icon under the message box). You should see Eddyter listed with its five tools. If they're there, you're done.

On a Team or Enterprise plan? Members usually can't add custom connectors themselves. An Owner adds it once under Organization settings → Connectors, and then each person connects with their own Eddyter login.

Fallback: the JSON config route

Older Claude Desktop versions without the connectors screen can still reach a remote server through the mcp-remote bridge. Open claude_desktop_config.json (Settings → Developer → Edit Config) and add:

1
2
3
4
5
6
7
8
{
  "mcpServers": {
    "eddyter": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.eddyter.com/mcp"]
    }
  }
}

Save, fully quit Claude Desktop, and reopen it. This needs Node.js installed. If your Claude Desktop has the Connectors screen, skip this and use the method above. It's cleaner and you won't have to update anything later.

How to add Eddyter MCP to Claude Code

In Claude Code it's one command plus a sign-in.

Step 1: Add the server

From your project folder, run:

1
claude mcp add --transport http eddyter https://mcp.eddyter.com/mcp

By default this adds Eddyter for you, in this project only. Two other scopes are worth knowing:

• --scope user makes Eddyter available in every project on your machine. Pick this if you manage one license across several apps.
• --scope project writes the server into a .mcp.json file at the repo root, so everyone who clones the project gets it. Good for teams. Safe to commit, too, because the file holds only the URL and no credentials.

For a team setup, the committed .mcp.json looks like this:

1
2
3
4
5
6
7
8
{
  "mcpServers": {
    "eddyter": {
      "type": "http",
      "url": "https://mcp.eddyter.com/mcp"
    }
  }
}

Step 2: Sign in

Start Claude Code (claude), then type:

1
/mcp

Select eddyter from the list and choose to authenticate. Your browser opens, you log in to Eddyter, pick a license key, and Claude Code picks up the token. You can also do this straight from the shell with claude mcp login eddyter.

Step 3: Confirm it worked

1
claude mcp list

Eddyter should show as connected. Then ask Claude something cheap and read-only, like "Is my Eddyter license active?" If you get your plan name and expiry date back, everything's wired up.

Things to ask Claude once Eddyter is connected

This is where the setup pays off. Some prompts that map cleanly to the tools:

• "Add the Eddyter editor to my Next.js app." In Claude Code, Claude reads your package.json, figures out whether you're on the App Router or Pages Router, fetches the official snippet, installs eddyter with whichever package manager your lockfile says you use, and adds the env variable with a placeholder.
• "How many AI credits do I have left this month?"
• "Which editor features are turned on?" Claude groups them into on, off, and locked by your plan.
• "Turn off AI chat and tables in my editor."
• "Let my team collaborate in the editor." This turns on comments and @mentions.
• "Let users export to PDF and Word."

One thing to keep in mind with the write prompts: update_config changes the live editor for everyone on that license key. Claude checks the current config first and tells you exactly what will change before it changes anything. Features your plan doesn't include stay locked, and Claude will say so instead of failing quietly.

The bit that saves the most time

Server-side rendering. Eddyter runs in the browser, and the most common integration bug we see is the editor getting rendered on the server, which throws window is not defined at build time. The get_integration_snippet tool returns setup code that already wraps the editor in a client-only boundary (dynamic(..., { ssr: false }) for Next.js, a ClientOnly wrapper for Remix). When Claude uses the snippet instead of writing the setup from memory, that bug mostly disappears.

Claude Desktop vs Claude Code: which should you use?

Use both if you can. Desktop is handy for quick account questions in the middle of the day. Claude Code is the one that actually writes the editor component, installs the package and runs your build to check it.

Troubleshooting Eddyter MCP

Eddyter tools don't show up. Remove the connector (or run claude mcp remove eddyter) and add it again so sign-in runs fresh. In Claude Desktop, also check that the Eddyter tools are toggled on in the chat's tools menu.

Sign-in fails or loops. Your Eddyter session has probably expired. Log in at eddyter.com in your browser first, then connect again.

"No active license key found." Your account has no active key. Create one at eddyter.com/user/license-key and reconnect.

A feature won't turn on. It isn't in your plan. Ask Claude "Which features does my plan allow?" and it'll show you what's locked.

The editor shows an auth error after setup. This one's in your app, not the MCP server. The env variable is missing, misnamed, or the dev server wasn't restarted. Next.js needs the NEXT_PUBLIC_ prefix and Vite needs VITE_. Ask Claude to run verify_status to rule out the key itself.

The editor loads with no styling. import 'eddyter/style.css' is missing from your editor component.

Frequently asked questions

Is the Eddyter MCP server free?

The MCP server costs nothing extra. It works with any Eddyter plan, including the free one. What you can toggle depends on your plan.

Do I need to install anything locally?

No. Eddyter's MCP server is hosted at https://mcp.eddyter.com/mcp and connects over HTTPS. The only exception is the mcp-remote fallback for old Claude Desktop versions, which needs Node.js.

Can Claude read my editor content through MCP?

No. The server reads license status, usage and editor configuration from Eddyter's API. It doesn't touch the documents your users write.

Does Eddyter MCP work outside Claude?

Yes. It's a standard remote MCP server, so any MCP client that supports HTTP transport with OAuth can connect to the same URL.

Which frameworks does the guided setup support?

React, Next.js (App Router and Pages Router), Vite and Remix. For Vue, Svelte or Angular, see the framework guides in the Eddyter docs.

Start using Eddyter with Claude

Grab a license key at eddyter.com/user/license-key, add https://mcp.eddyter.com/mcp to Claude, and ask it to drop the editor into your app. Full setup guides for every framework are in the Eddyter docs. Questions or bugs go to Eddyter support or the eddyter-mcp GitHub repo.