NicoChatNicoChatDocsSearch the docs…
Sign in
NicoChat MCP/Claude Code - Connect the MCP

Claude Code - Connect the MCP

One command in the terminal registers the server; authorization happens in the browser during the first session.

2026-09-08

In Claude Code, the NicoChat server is added with a single command and authorized from the terminal itself. After that, any Claude Code session in that scope has the NicoChat tools available, and you can mix running your account with working on code: for example, reading a channel flow and generating its documentation in your repository.

Before you start

  • Server URL: https://mcp.nicochat.com/mcp. It is the only information the client asks for; there is no API key to copy.
  • A NicoChat account with a workspace on a paid or trial plan, and you as its owner or admin.
  • Claude Code installed and authenticated (claude opens in the terminal).

Step by step

1
Register the server
In the terminal, run the command below. The transport is HTTP and the name nicochat is how the server will appear in the tools.
2
Authorize
Open Claude Code and type /mcp. Select nicochat and choose to authenticate: the browser opens the NicoChat authorization page. Log in, choose permissions and expiration, and confirm.
3
Confirm
Back in the terminal, /mcp shows the server as connected and lists the available tools, which appear with the mcp__nicochat__ prefix.
bash
claude mcp add --transport http nicochat https://mcp.nicochat.com/mcp

Configuration scope

By default the server stays in the local scope, valid only for the current project. To have it in every project, add --scope user. To share it with your team through the repository, use --scope project: this writes a .mcp.json file at the root, and each person does their own authorization.

bash
claude mcp add --transport http --scope user nicochat https://mcp.nicochat.com/mcp

The authorization screen

Whatever the client, authorization happens in the browser, on the NicoChat page. You log in, choose the permissions (read and analytics is always granted; configuration, contacts, integrations and campaigns are optional) and the connection's expiration: 1, 7, 30 or 90 days, or no expiration. The tools the assistant sees depend on what you checked here — to expand later, just reconnect.

Start with read only
On your first connection, grant only read and analytics and ask for a diagnosis of your channels. Once you are comfortable with what the assistant does, reconnect granting configuration or contacts.

First requests to try

Once connected, ask Claude Code in natural language. Some examples that use read access only:

  • "List my workspaces and the channels in each one."
  • "How many contacts came into the WhatsApp channel in the last 7 days and what is the average first response time?"
  • "Summarize the structure of channel X: flows, triggers, AI agents and kanban boards."
  • "Which keywords are configured in channel X and where does each one lead?"

If you granted configuration, the assistant also creates flows, triggers, tags and AI agents. Everything it creates in a flow stays as a draft until you publish it in NicoChat.

Tool approval
Claude Code asks for confirmation before each write tool the first time. For repetitive read operations, you can approve "always in this project" when it asks.

Disconnect or revoke

  • In the client: run claude mcp remove nicochat. If you registered it in more than one scope, pass --scope.
  • In NicoChat: under Account Settings, revoke the authorization. It takes effect immediately, even if the server is still registered in the client.

Common problems

It was registered earlier in another scope. Run claude mcp list to see where it is, and claude mcp remove nicochat in the right scope before adding it again.
Close and reopen the Claude Code session. If it persists, remove and add the server again: the token stored locally is discarded and the authorization is redone.
Copy the link the client shows and open it manually. If it shows no link at all, remove the server and add it again: the client registration in NicoChat is redone on first access.
That is expected when only the read permission was granted. Disconnect and connect again, checking the write permissions you need.
The server only operates in workspaces on a paid or trial plan where you are the owner or an admin. Check the plan and your role in the workspace in the NicoChat dashboard.
The expiration you chose during authorization has passed. Reconnect and, if you prefer, choose "no expiration".