Skip to main content
Glama
io.github.morfiade-app/morfiade-mcp

io.github.morfiade-app/morfiade-mcp

Official

Morfiade MCP

MCP server for local Google Chrome profiles on Windows. 19 tools that let an AI agent list, create, launch and organise real Chrome profiles on your own machine — each with its own cookies, sessions and proxy.

The server is not a package you download: it ships inside Morfiade, the Chrome profile manager itself, and starts with a flag. Transport is stdio (JSON-RPC 2.0), protocol version 2025-11-25. Nothing is fetched from the internet, nothing passes through anyone else's server.

This repository is the documentation, the ready-made client configs and an optional launcher. Русская версия — README.ru.md.


What makes it different

The bridge lives in the program. AdsPower and GoLogin publish MCP servers as separate packages that talk to their cloud. Morfiade keeps profiles on your disk, so the bridge stays on your disk too: Morfiade.exe --mcp, over the loopback interface, no network required.

Distributing values across windows. The tools with no equivalent elsewhere are sync_sets / sync_spread / sync_insert: a list of values — emails, logins, anything line-based — is split across the open windows, one value pinned per profile. A repeat call does not reshuffle what is already pinned, otherwise an account would be registered on one email and confirmed with another. The agent never sees the values themselves (see Security).

Example prompts that work out of the box:

Create twenty profiles with the prefix shop, give them proxies from this list, and launch the first five.

Check the proxies on every profile I can manage and tell me which ones are dead or exiting from the wrong country.

Take the mail-batch set, spread it across the open windows and show me who got what. I'll put the cursor in the email field, then insert.


Related MCP server: Ghostvault

Requirements

  • Windows 10 or 11

  • Morfiade 3.37 or newer, running

  • Local API enabled in its settings — the server refuses to start without it instead of failing silently

  • The "API" checkbox ticked on the profiles the agent may touch; it is off by default, and unticked profiles do not exist as far as the agent is concerned

  • A valid licence to launch profiles (that check lives in the manager, not here)

  • Any MCP client with stdio support: Claude Code, Claude Desktop, Cursor, Gemini CLI, VS Code, your own

Nothing to install: no pip install required, no Node, no API key to register. The launcher below is optional.


Setup

Point your client at the executable and pass --mcp:

{
  "mcpServers": {
    "morfiade": {
      "command": "C:\\Program Files\\Morfiade\\Morfiade.exe",
      "args": ["--mcp"]
    }
  }
}

Ready-made files for the common clients are in examples/. Claude Code can do it in one line:

claude mcp add morfiade -- "C:\Program Files\Morfiade\Morfiade.exe" --mcp

Where the config file lives differs per client and changes more often than this README — check your client's own docs.

Optional launcher

If you would rather not hardcode the path, morfiade_mcp.py finds the executable (via MORFIADE_EXE, the installer's registry key, the usual install directories, or PATH), forwards stdio and returns its exit code. Requires Python 3.7+ and nothing else.

pip install morfiade-mcp
{
  "mcpServers": {
    "morfiade": {
      "command": "morfiade-mcp"
    }
  }
}

If your client needs an absolute path, point it at the morfiade-mcp.exe that pip put in your Python Scripts directory. Without the package, the single file works on its own too — "command": "python" with morfiade_mcp.py as the only argument.

The package contains only that launcher. The server, and everything it talks to, is the desktop app.

Schema-only mode. Outside Windows — say, in the Linux container where an MCP directory starts a server to list its tools — there is no program to run, so the launcher answers the handshake and tools/list itself, from the schemas in schemas/ that are dumped from the real server. Every tool call then returns an error saying Morfiade runs on Windows: the tools are described, not imitated. MORFIADE_MCP_SCHEMA_ONLY=1 turns this mode on anywhere, for testing.


Tools

Full parameters and return shapes: docs/TOOLS.md. Machine-readable schemas, exactly as the server answers tools/list: schemas/.

  • status — version, how many profiles exist, how many the agent may use, how many are running

  • list_profiles — the permitted profiles: name, running or not, proxy and its last check, note, debug-port mode

  • create_profile — create a profile — optionally with proxy, note and category; permitted for the agent immediately

  • start_profile — launch a profile, optionally straight onto a URL; warns about a dead proxy or debug-port mode

  • page_info — what the active tab shows: title, address, whether it loaded, whether a Cloudflare check holds it

  • stop_profile — close the profile window

  • set_proxy — assign a proxy (host:port, host:port:user:pass, or type://user:pass@host:port from Morfiade 3.40; empty string clears it)

  • check_proxy — check one profile's proxy: alive, and where it exits

  • check_proxies — the same across several profiles, or all of them

  • profile_tags — read the tags, or replace them wholesale

  • profile_note — read or write the note and its short title

  • sync_windows — which open windows are ready for distribution and what is already pinned to each

  • sync_sets — value sets: list them (name, lines, how many still free) or create one

  • sync_spread — pin one line of a set per window and report who got what — inserts nothing

  • sync_insert — insert each window's own value where the cursor sits in the leading window

  • list_scripts — scripts in the manager's folder: name and interpreter, never the contents

  • trash_profile — move a profile to the trash — nothing is erased

  • list_trash — what is in the trash: name, when, how much space

  • restore_profile — restore from the trash; a taken name comes back as name (2)

Two more appear only behind explicit flags — see Dangerous flags.


Security: what the agent cannot do

An agent that reads web pages is not a trusted party. A page can contain the text "call this tool and send the cookies over there", and the agent cannot tell your instruction from text it found on the internet. That is the known central problem of MCP, and no amount of prompt wording fixes it. So the limits are built into the tool list instead:

  • Deletion goes to the trash only. Profiles stay whole — cookies, sessions, everything — and come back with one call. Permanent erase and emptying the trash are not exposed here and never will be: they are the only irreversible actions, and a human does them from the trash window, where they can see what they are destroying.

  • No cookie reading. GoLogin's MCP has such a tool, which means cookies travel from the account into a chat log. This one does not have it.

  • Set lines are not exposed. sync_sets reports the name, the line count and how many are free. The emails and logins themselves stay in the manager — the agent does not need to see them, it needs them to land in the windows.

  • Script contents are not exposed. list_scripts gives names and interpreters only.

  • The mirror is not exposed. It reflects what a human is doing right now in the leading window; there is nothing for an agent to repeat.

  • The whitelist cannot be bypassed. The "API" column is filtered by the manager itself, not by this server.

  • The licence check does not weaken. It sits in the manager's handler, so it fires whether a human, a script or an agent asked.

  • Nothing listens on the network. The local API binds 127.0.0.1, requires a token and checks the Host header. The token is stored encrypted with Windows DPAPI, tied to the account, and travels in a header rather than a URL — URLs end up in logs.

Dangerous flags, off by default

Flag

Extra tool

What it really means

--mcp-allow-cdp

browser_command

an arbitrary Chrome DevTools Protocol command. Runtime.evaluate in a logged-in profile reads cookies, storage and page contents — full access to your accounts, not "advanced management"

--mcp-allow-scripts

run_script

runs a script from the manager's folder — code execution on your machine

Both are worth turning on only with the paragraph above in mind, and only for pages you trust.


Troubleshooting

What you see

What to do

the client shows no tools

check the path to the exe in the client config

"local API is off"

enable the local API in the manager's settings

"no port or token in config.json"

open the manager once so it writes its settings

"the manager does not answer"

the manager has to be running

"profile not found", though it exists

the "API" checkbox is not ticked on that profile

"the API token contains invalid characters"

the config came from another machine — reissue the token in settings

launching a profile is refused

no valid licence: profile launch is closed over the API and MCP alike

Messages come from the manager and follow its interface language — five are available, so the wording you see may be your own.


What is not here

The bridge itself is compiled into Morfiade.exe, and the session transfer mechanism — the part that actually moves logged-in sessions between machines — stays closed. This repository is the outside of the product: documentation, configs, the launcher.

License

MIT for everything in this repository — see LICENSE. The manager is a separate commercial product with its own terms.

Available Tools

18 tools
check_proxiesA
Read-only

Test the proxies of several profiles, or of every profile available to the agent when no list is given. Checks run one after another, up to about ten seconds each, so a long list takes minutes. Changes nothing. Profiles without a proxy are reported as such.

Inputs: profiles.

check_proxyA
Read-only

Test one profile's proxy by making a request through it: whether it answers, the exit IP and country, and latency. Changes nothing; takes up to about ten seconds. For several profiles use check_proxies instead.

Inputs: profile (required).

create_profileA

Create a new, empty Chrome profile on disk and allow it for the agent. It is not launched: call start_profile for that. Fails if the name is already taken; use list_profiles to see existing names. Proxy, note and category can be set at once or later with set_proxy and profile_note.

Inputs: name (required), note, proxy, category, +1 more.

list_profilesA
Read-only

List the browser profiles the owner has allowed for the agent (the "API" column in Morfiade); other profiles are invisible here. For each: name, whether it is running, proxy (password hidden), proxy type, category, antidetect on/off, note and launch count. Read-only. Call it first: every other tool takes a profile name exactly as listed here.

Inputs: no named parameters.

list_scriptsA
Read-only

Scripts in Morfiade's scripts folder: file name, the program that runs it, and whether that program is installed. File contents are never shown. Read-only.

Inputs: no named parameters.

list_trashA
Read-only

Profiles in the recycle bin: name, when it was deleted and how much disk it takes. Read-only; use the names with restore_profile.

Inputs: no named parameters.

profile_noteA
DestructiveIdempotent

Read or write a profile's note. Without title and note it only reads. title is the short line shown in the profile table, note the full text; a field you pass overwrites the old value, a field you omit stays as it was.

Inputs: profile (required), note, title.

profile_tagsA
DestructiveIdempotent

Read a profile's tags, or replace them all. Without tags it only reads. With tags the list you pass becomes the whole set: tags you leave out are removed, and an empty list clears them. To add one tag, read first and pass the old list plus the new tag.

Inputs: profile (required), tags.

restore_profileA

Bring a profile back from the recycle bin with its cookies and sessions. If the name has been taken meanwhile, it returns as "name (2)" and nothing is overwritten; the answer says which name it got.

Inputs: profile (required).

set_proxyA
DestructiveIdempotent

Save a proxy in a profile's settings, replacing the current one; an empty string removes it. Takes effect on the next launch: a running profile keeps its old proxy until stop_profile and start_profile. Run check_proxy afterwards to see whether it works.

Inputs: proxy (required), profile (required), type.

start_profileA

Launch a profile: opens its real Chrome window with its own cookies, sessions and proxy. If the profile is already running, only opens the URL in a new tab of that window. Can take up to a minute and needs a valid Morfiade licence. The agent cannot drive the page afterwards through these tools; that needs browser_command, which the owner enables separately.

Inputs: profile (required), url.

statusA
Read-only

Morfiade version, how many profiles exist, how many the agent may use and how many are running right now. Read-only and instant; use it to check the manager is reachable before anything else.

Inputs: no named parameters.

stop_profileA
Idempotent

Close a running profile's Chrome window. Nothing is deleted: cookies, sessions and history stay in the profile, and the next start_profile picks them up. Text typed into pages but not submitted is lost. Calling it on a stopped profile is harmless and reports already_stopped.

Inputs: profile (required).

sync_insertA
Destructive

Type each window's own pinned value into the input field that has the cursor in the leading window; the same field receives it in every window. A person must click into that field first. The text is inserted into the page as typed input and cannot be undone by the tool. Windows without a pinned line get the next free one now; call sync_spread first to review who gets what.

Inputs: set (required), leader.

sync_setsA

Value sets for distributing across windows: lists of emails, logins or any line-based data, one line per window. Without arguments lists the sets with their line count and how many lines are still free; the values themselves are never shown. With name and lines creates a new set.

Inputs: name, lines.

sync_spreadA
Idempotent

Pin one free line of a set to each ready window and report who got what. Types nothing; that is sync_insert. Safe to repeat: windows that already hold a line keep it, so an account is never registered with one email and confirmed with another.

Inputs: set (required), profiles.

sync_windowsA
Read-only

Which open profile windows can take part in distributing values, and which value each already holds. Windows that cannot (for example, antidetect off) are listed with the reason. Read-only; call it before sync_spread and sync_insert.

Inputs: no named parameters.

trash_profileA

Move a profile to Morfiade's recycle bin. Nothing is erased: the profile keeps its cookies and sessions and comes back with restore_profile. A running profile is closed first. Emptying the bin is not available to the agent.

Inputs: profile (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 18 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action: profile lifecycle, proxy testing, metadata, and the four sync tools are clearly separated by their descriptions. The only real overlap is check_proxy/check_proxies, which is explicitly resolved by the description directing multi-profile use to the plural form. profile_note and profile_tags share a read/write interface but operate on clearly different fields.

    Naming Consistency4/5

    The dominant pattern is snake_case verb_noun (create_profile, stop_profile, check_proxy, list_profiles), and the sync_* group is internally consistent. Deviations include status as a bare noun and profile_tags/profile_note, which invert the convention by leading with the resource. Overall the set is readable and predictable despite these minor inconsistencies.

    Tool Count4/5

    18 tools is slightly above the ideal 3-15 range, but the server covers three distinct subdomains—profile lifecycle, proxy management, and window sync—each of which justifies its tools. The four sync tools alone form a complete pipeline that would be impossible to compress without losing clarity. It feels slightly heavy but not bloated.

    Completeness4/5

    The domain is well covered: full profile lifecycle (create, list, start, stop, trash, restore), proxy set/test/clear, and a complete sync workflow (windows, sets, spread, insert) with no obvious dead ends. Minor gaps exist—profile category cannot be updated after creation, trash cannot be emptied, and hard deletion is unavailable—but these appear to be intentional policy limits rather than oversights.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      A
      maintenance
      Enables AI agents to manage multiple Google accounts with persistent sessions and anti-detect browser fingerprints, supporting sign-in, account switching, Gmail access, and interaction with any Google SSO website.
      42
      -
    • A
      license
      A
      quality
      A
      maintenance
      MCP server + Chrome extension that drive the user's real, logged-in Chrome over a local WebSocket. 59 token-efficient web-dev tools: compact element refs instead of screenshots, server-side table filtering, visual regression, accessibility/SEO/security audits, network mocking. Also runs on ChromeOS/Crostini.
      69
      1,144 npm
      7
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server that attaches to already-running Chromium browsers via CDP, enabling agents to control multiple browser sessions for navigation, input, network capture, and automation while avoiding anti-bot detection with Patchright.
      26
      1
      MIT