Does the MCP server edit my code?

No. The server reads your license, usage and config, returns setup snippets, and changes editor config on your key. Your AI agent writes the code in your project, using the snippet it gets back.

Which frameworks does the setup snippet cover?

The frameworks Eddyter supports: React, Next.js, Vue 3, Angular, Svelte and Vanilla JS. See the docs for versions.

The tools don't appear after connecting.

Remove and re-add the connector so your client runs the sign-in again. If sign-in fails, sign in at eddyter.com first, then reconnect. Still stuck? Open an issue.

Yes. The server is MIT licensed on GitHub and published to npm as eddyter-mcp.

Model Context Protocol

10 minutes?
Make it two.

Connect Eddyter to your AI agent. Check your license, get SSR-safe setup code for your framework, and switch editor features on or off by chat, with no redeploy. Available in Cursor, Claude Code, Claude Desktop and Claude.ai.

→ Hosted server: mcp.eddyter.com/mcp · OAuth sign-in · MIT licensed

Add to Cursor Add to Claude

Using Claude Code, Codex or another client? See the MCP setup ↓

Cursor — agent MCP

you › Add Eddyter to my Next.js app

Signed in to the Eddyter MCP server

verify_status · license key active

get_integration_snippet · Next.js, SSR-safe

Installed eddyter and created Editor.tsx

Eddyter is ready — run npm run dev

Watch: installing Eddyter in Cursor via MCP

Install with your AI agent

CursorDirectoryClaudeDirectoryClaude CodePluginCodexRemote MCP

Any other MCP client? Run it locally with npx.

Watch it work

See it. Then do it.

Short clips for each client and task. Pick one and watch it, then set it up in your own client.

Cursor Directory

One-click plugin install. Cursor connects to the hosted server and asks you to sign in on first use. No npm install, no key pasting.

Add to Cursor

claude.ai/directory/eddyter

Claude Directory

Add Eddyter as a connector in Claude.ai or Claude Desktop, sign in with your Eddyter account, and approve the license key to connect.

Add to Claude

github.com/EddyterAI/eddyter-mcp

Open source on GitHub

MIT licensed. Also published to npm as eddyter-mcp for clients that run servers locally.

View the source

How it works

Three steps.
No config files.

01

Install from the directory

Pick Eddyter in the Cursor Directory or the Claude Directory. Your client wires up the hosted server at mcp.eddyter.com.

02

Sign in with Eddyter

An OAuth window opens. Sign in, choose the license key to connect, and approve. Each connection is scoped to that one key.

03

Ask your agent

"Add Eddyter to my app." "Is my key valid?" "Turn off AI chat." Your agent calls the right tool and does the rest.

What your agent can do

Five tools. One license key.

The MCP server is the admin side of Eddyter. Config lives on your license key, so a change applies to every editor that uses that key, instantly.

Read

verify_status

Is the key valid and active? Returns plan, expiry, subscription, BYOK status and any warnings.

Read

get_config

Which editor features are enabled, which are off but allowed, and which are locked by your plan.

Read

get_usage

AI credits remaining, usage this billing period, and days until your credits reset.

Read

get_integration_snippet

SSR-safe, copy-paste setup code for your framework, so your agent writes the integration correctly the first time.

Write

update_config

Switch editor features on or off by chat, for example turning AI chat off. Clamped to your plan and live with no redeploy.

Try asking

Talk to your editor setup

Click a prompt to copy it

MCP setup

Set up in your client

Server URLhttps://mcp.eddyter.com/mcp Hosted · OAuth

Claude.ai and Claude Desktop

Install from the Claude Directory, or add it by URL as a custom connector. Sign-in is handled by OAuth.

1Open Settings → Connectors → Add custom connector.
2Paste the URL https://mcp.eddyter.com/mcp.
3Sign in with your Eddyter account and approve the license key to connect.
4Ask: “Check my Eddyter license status.”

Claude Code

Install the plugin in one step. It connects to the hosted server and asks you to sign in on first use, with no environment variables.

/plugin marketplace add EddyterAI/eddyter-mcp
/plugin install eddyter@eddyter

Cursor

Install Eddyter from the Cursor Directory, or add the remote server by hand in .cursor/mcp.json:

{
  "mcpServers": {
    "eddyter": {
      "type": "http",
      "url": "https://mcp.eddyter.com/mcp"
    }
  }
}

Codex

Codex supports remote OAuth servers directly. You will be asked to sign in on first use.

codex mcp add eddyter --url https://mcp.eddyter.com/mcp

Run locally with npx

For clients without remote-server support. Get your license key from the dashboard, then add this to your client config (for Claude Desktop: Settings → Developer → Edit Config):

{
  "mcpServers": {
    "eddyter": {
      "command": "npx",
      "args": ["-y", "eddyter-mcp"],
      "env": { "EDDYTER_LICENSE_KEY": "YOUR_API_KEY" }
    }
  }
}

Locally, writes are off by default. Set EDDYTER_ALLOW_WRITES=true to let the agent use update_config.

Privacy and control

Your code stays yours

Sent

What is sent

Tool arguments, such as a feature to toggle or a framework name.
Your OAuth token, scoped to one Eddyter license key.
Over HTTPS to mcp.eddyter.com, which calls api.eddyter.com.

Never sent

What is never sent

Your documents or editor content.
Your conversation history.
Local files or environment variables.

Guardrails

Guardrails on writes

Only update_config changes anything.
Every change is clamped to your plan's limits.
The MCP never creates license keys. You do, in the dashboard.

Read the privacy policy and terms.

FAQ

Questions

An Eddyter account with an active license key. Create one from your dashboard, then connect from Cursor or Claude and pick that key during sign-in.

Changes are clamped to your plan, so a feature your plan locks stays off. Ask your agent to run get_config to see what your plan allows, or compare plans.

Start from here

Let your agent set up Eddyter

Install from your client's directory, sign in once, and ask.

Add to Cursor Add to Claude Get your API key

10 minutes?Make it two.

See it. Then do it.

Cursor Directory

Claude Directory

Open source on GitHub

Three steps.No config files.

Install from the directory

Sign in with Eddyter

Ask your agent

Five tools. One license key.

Talk to your editor setup

Set up in your client

Claude.ai and Claude Desktop

Claude Code

Cursor

Codex

Run locally with npx

Your code stays yours

What is sent

What is never sent

Guardrails on writes

Questions

What do I need before connecting?

Does the MCP server edit my code?

Which frameworks does the setup snippet cover?

I asked to turn a feature on and nothing changed.

The tools don't appear after connecting.

Is it open source?

Let your agent set up Eddyter

10 minutes?
Make it two.

Three steps.
No config files.