NicoChat MCP

NicoChat offers a remote MCP (Model Context Protocol) server that lets you connect your account to AI assistants and other tools that support the protocol. Once connected, the assistant operates your NicoChat account by talking with you: analyzing channels and contacts, building automations, configuring AI agents.

Server details

Any MCP client that supports Streamable HTTP and OAuth 2.0 can connect. There is no need to request application credentials from NicoChat: the client registers itself on first access.

What the server exposes

• Operation analysis — channels, contacts, conversations, support metrics and per-channel performance, agent activity.
• Automations — create and edit flows, keyword triggers, comment triggers on Facebook and Instagram, sequences and kanban boards.
• Artificial intelligence — AI agents, functions, knowledge bases and vector stores.
• Channel catalog — tags, custom fields, labels, events and segments.
• Contacts — create, update, tag, assign to agents and move between stages.
• Team — human agents, agent groups and business hours.
• WhatsApp — official templates, WhatsApp Flows and Cloud API integration.
• Campaigns — broadcasts to lists, tags and segments.

Prerequisites

• A NicoChat account with a workspace on a paid or trial plan.
• Being the owner or an administrator of the workspace you want to operate.

How to connect

The flow is the same in any MCP client:

• Add the https://mcp.nicochat.com/mcp server in your client.
• The client registers itself automatically and opens the authorization page in your browser.
• Sign in to your NicoChat account.
• On the consent screen, choose the permissions you want to grant and how long the authorization lasts.
• Authorize. The client can now see your workspaces.

Example: connecting through Claude

In Claude, add a custom connector with the server URL. The rest of the flow follows the steps above — signing in to NicoChat, choosing the permissions and authorizing.

Permissions

You choose the permissions at the moment of connection. No write happens without the corresponding permission having been granted.

The tools available in the session are filtered by the permissions granted: connecting with read access only, the write tools do not appear. You can broaden it later by reconnecting.

Duration and revocation

When you authorize, you set how long the connection is valid: 1, 7, 30 or 90 days, or no expiry. The authorization can be revoked at any time in the NicoChat panel, under Account settings, or by removing the server in your MCP client. Revocation takes effect immediately.

Security

• Authentication uses OAuth 2.0 with PKCE. Your password is never handed to the MCP client.
• Your identity always comes from the authorized credential, never from anything stated in the conversation.
• Each connection operates only on the workspaces you own or administer. Attempts to reach another workspace are refused.
• Every response passes through a sanitization layer that strips secrets — API tokens, integration keys and credentials are never returned to the client.
• Write operations validate the target workspace before running; when in doubt, the operation fails instead of proceeding.

Known limits

• The server works on workspaces on a paid or trial plan. Free workspaces are not accessible.
• Features contracted separately (such as the CRM) only appear if they are active on your account.
• WhatsApp-specific tools require a Meta-approved business number connected to the channel.
• Flows that are created or edited need to be published before they go live.

Support

Questions or problems with the MCP server: talk to NicoChat support through the usual support channels.