How to add an MCP server to Claude Code with one command

# Add Zyflow to Claude Code with one command

Zyflow’s MCP server is remote, so Claude Code needs only a name and a URL. Run this once in your terminal, not inside a claude session. It works the same in macOS and Linux shells, PowerShell and Command Prompt.

claude mcp add --transport http --scope user zyflow https://app.zyflowcrm.com/mcp

There's nothing to install: no npm package and no local process. To check that Claude Code saved the server, run:

claude mcp list

The list shows zyflow with “! Needs authentication”, which is expected until you sign in. Anthropic’s Claude Code MCP reference lists every flag.

# Sign in with /mcp

Zyflow uses a browser sign-in, like “Sign in with Google”, so you never paste a password or key into the terminal. There’s no app to register and no client secret to copy. Zyflow supports dynamic client registration and client ID metadata documents, with OAuth 2.1 and PKCE, so Claude Code finds the sign-in by itself.

1. Start claude, type /mcp, select zyflow and choose Authenticate.

2. Your browser opens Zyflow. Log in or create your free account, pick the one workspace Claude Code may use, and approve within 10 minutes.

3. Back in Claude Code, zyflow shows as connected, and Zyflow’s Connect page lists it under Connected apps.

No browser on this machine?

On a remote machine over SSH, sign in from your shell. Connect with ssh -t so the terminal accepts a paste, then run:

claude mcp login zyflow --no-browser

Open the link it prints in a browser on your own computer and approve. Then copy the full address from that browser’s address bar and paste it back into the terminal.

One connection reaches one workspace. To switch, choose Clear authentication in /mcp and sign in again. Disconnect under Connected apps cuts off access from Zyflow’s side at once.

# Local, project or user scope: which to pick

Pick user scope for Zyflow. Your customers aren’t tied to one repo, and user scope makes Zyflow available in every project on this machine. Claude Code’s default, local scope, works only in the folder where you ran the command, so in any other folder /mcp can say “No MCP servers configured”.

Share it with your team

Add it with --scope project, or commit this .mcp.json:

{
  "mcpServers": {
    "zyflow": { "type": "http", "url": "https://app.zyflowcrm.com/mcp" }
  }
}

The file holds only the URL, not your sign-in, so it’s safe to commit. Claude Code asks each teammate to approve the server once. Then each person signs in to their own Zyflow account, and History labels every change with their name.

# Use Zyflow from the terminal

Ask Claude Code in plain words. Claude Code chooses which Zyflow tools to call, and Zyflow keeps the record; Zyflow runs no AI of its own. A new workspace is empty, so start by adding a customer.

• Add Maya Chen at Northwind as a customer. Her email is maya@northwind.example.
• Had a call with Maya at Northwind. She wants the revised quote by Friday.
• What do we know about Northwind?
• File the notes in ./notes/northwind-call.md to Zyflow. Show me the list first.
• What’s on my plate today?

The fourth prompt works from your repo: Claude Code reads the file, shows you the list of what it will file, then saves it on the customer you already have. Zyflow sends each date back so Claude Code can confirm it with you: Fri, 9 Oct. When a name could mean two people, Zyflow sends Claude Code the candidates, and Claude Code asks you which one you mean.² Each change is labeled with the app and comes with an Undo.¹

Live labels and Undo buttons appear in any open Zyflow tab. Every change is also in History.

Let lookups run without asking

By default, Claude Code asks before it runs a Zyflow tool. To let lookups run without a prompt, add these allow rules in /permissions and save them to your user settings. Claude Code still asks before every write.

mcp__zyflow__get_*
mcp__zyflow__list_*
mcp__zyflow__search
mcp__zyflow__fetch
mcp__zyflow__describe_workspace

Read the MCP reference

# Building on Zyflow: the REST API and API keys

For scripts, CI and machines where nobody can sign in, use a named API key from Zyflow’s Connect page. Pass it as a header on the same command:

claude mcp add --transport http --scope user zyflow https://app.zyflowcrm.com/mcp --header "Authorization: Bearer <your API key>"

{
  "mcpServers": {
    "zyflow": {
      "type": "http",
      "url": "https://app.zyflowcrm.com/mcp",
      "headers": { "Authorization": "Bearer ${ZYFLOW_API_KEY}" }
    }
  }
}

Zyflow shows each key once. Keys don’t expire on their own, and you can revoke one on the Connect page. Any key, read-only included, can export the workspace, so keep keys out of repos and logs.

The REST API at /api/v1 has the same operations as the MCP server, and its OpenAPI reference is at /api/docs. There are no webhooks or SDKs.

Thinking of building your own CRM in Claude Code? Plenty of people start there. The Claude Code CRM guide compares building with connecting.

Read the REST API docs

# Troubleshooting Zyflow in Claude Code

Run claude mcp list in your shell, or /mcp inside Claude Code. The status next to zyflow tells you which fix you need.

# Questions about Claude Code and Zyflow

Read the security page