Janusmcp MCP Server

Local multi-account MCP broker — one endpoint, every account. Switch identity without reconnecting. The janusmcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

One-click buttons require the npm package to be published. See RELEASING.md.

• Add N accounts once — for the same service and keep them all available
• Switch identity without reconnecting — — no re-login, no fiddling with config
• Works with any LLM client — — it just speaks standard MCP (stdio + Streamable HTTP)
• Works without an MCP session too — — agents can drive it directly from the CLI
• Runs locally — — your machine, your keychain, your control
• Keeps the context clean — — it exposes only the active account's tools, not N×tools

Its toolset

Everything the assistant can do here goes through one of these:

• ActiveCampaign — ActiveCampaign ships an official remote MCP server with a unique URL per account (ActiveCampaign → Settings → Developer → Remote MCP URL)
• Figma — The proper long-term fix is for JanusMCP to be submitted to and approved for Figma's MCP catalog, so no client_name override is needed. This is

Configuration

You will need 6 environment variables: SUPABASE_ACCESS_TOKEN, JANUS_CONFIG, GOOGLE_OAUTH_CLIENT_ID, JANUS_HTTP_HOST, REPLACE_ACTIVECAMPAIGN_MCP_URL, GOOGLE_OAUTH_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Janusmcp's toolset — ActiveCampaign, Figma — is a fair guide to whether it matches your workflow. It is maintained by Bayway; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Janusmcp's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the janusmcp mcp server does with a few real requests.