Running profiles from an AI agent
If you already have a command-line agent on your machine — Claude Code, Gemini CLI, Cursor, a local model — Morfiade connects to it, and profile work can be handed off in plain words.
The MCP bridge lives inside the program itself: a separate exe starts with the --mcp flag, and the client sees the tools. Nothing gets downloaded from the internet, nothing goes through someone else's server.
What this looks like in practice
shop, hand them proxies from the library, turn on antidetect, and launch the first five."The second example is something competitors do not have even inside the program itself, let alone through an agent: distributing values across windows. The list is split across profiles line by line, and the value pinned to a profile does not change on a repeat call. Otherwise an account would end up registered on one email and verified with another.
What the agent can do
Eighteen operations:
- profiles — list, create, launch, stop, move to trash and restore from it;
- proxies — assign to a profile, check one at a time or in bulk;
- organization — tags and notes;
- state — how the manager is doing and which scripts sit in its folder (names only, never the contents);
- distributing values across open windows.
This is also our answer to the "no-code scenarios" that Dolphin and AdsPower offer. We answer it not with a block-based builder but with direct access for the agent: describing a task in words is faster than assembling it with a mouse.
What stays off limits, and this is the important part
An agent is not a trusted party. It acts on whatever it has read, and it can read text from a page you opened for it just as easily. So access is built out of locks, not a default permission.
The local API is off until you turn it on. Without it the MCP server honestly refuses to start, instead of staying silent about the problem.
Profiles are marked by hand. The "API" column is unchecked by default: the agent sees exactly the profiles you have ticked. The rest do not exist as far as it is concerned.
The manager has to be running. The bridge itself does nothing on its own — it only translates the agent's requests into calls to the program.
⚠️ A separate note on the direct browser-control key: it gives the agent more than a list of profiles, and turning it on is worth doing with the consequences in mind. The details are in the manual, in the section on AI agent access.
How this differs from what others offer
| Morfiade | AdsPower, GoLogin | |
|---|---|---|
| Where the bridge lives | inside the program, --mcp | a separate package from the internet |
| Works without a network | yes | no |
| Distributing values across windows | yes | not even inside the program itself |
| Access to profiles | only to the ones ticked | full, by API key |
This is not "they're bad, we're good": for cloud services a cloud bridge makes sense, because their profiles live in the cloud too. It is just that if you keep your profiles on your own machine, managing them through someone else's server is an odd choice.
What you need to try it
Morfiade for Windows, the local API turned on, and an MCP client. Its settings need the path to the program and the flag:
`` "morfiade": { "command": "C:\\Program Files\\Morfiade\\Morfiade.exe", "args": ["--mcp"] } ``
In Claude Code this is added with the claude mcp add command; other clients use their own settings file — check their docs for the exact spot, since those change more often than ours.
Automation is included in every license and does not require a higher tier: with some competitors the API and Selenium only unlock on the top plans.