NicoChat MCP
NicoChat provides a remote MCP (Model Context Protocol) server that lets you connect your account to AI assistants and other tools compatible with the protocol.
NicoChat provides a remote MCP (Model Context Protocol) server that lets you connect your account to AI assistants and other tools compatible with the protocol. Once connected, the assistant starts operating your NicoChat account by talking with you: analyzing channels and contacts, creating automations, configuring AI agents, building apps and testing flows.
https://mcp.nicochat.com/mcpAny MCP client compatible with 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.
The procedure is the same in any MCP client:
- Add the server
https://mcp.nicochat.com/mcpin your client. - The client registers automatically and opens the authorization in your browser.
- Log 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.
Each client has its own place to register the server and its own way of starting the authorization. The guides below cover the most used ones, step by step:
Another client? If it accepts a remote server by URL with OAuth, it works the same way: enter the URL, leave Client ID and Secret blank and authorize in the browser.
- NicoChat account with a workspace on a paid or trial plan.
- Be the owner or administrator of the workspace you want to operate.
There are more than 200 tools, organized by area. Each name follows the group_subject_action pattern (for example, channel_sub_flow_publish), so the prefix tells you what it operates on.
channel_kanban_list, contact_chat_move) is the visual organization of conversations and comes with every plan. The CRM (crm_pipeline_*) is an add-on contracted separately. When you ask for the conversation "funnel" or "board", the assistant uses the kanban.The areas below were added to the server after the first version. If you connected before, reconnect so that the client refreshes its tool list:
- Node-by-node flow editing — create, edit and delete nodes and connections of an existing flow, plus validate, duplicate and move flows between folders.
- My Apps and Mini Apps — build complete custom apps and install Mini Apps from the catalog.
- NicoZap — create instances, generate the connection and follow the status.
- AI tasks and AI provider — create and adjust AI tasks and switch the provider used by the channel.
- Templates and files — create and install templates; upload files for use in flows.
- Sandbox testing — talk to the flow through a test contact and read the reply, without touching real contacts.
- Channel translations and Google Sheets — read and write the bot interface translations; register spreadsheets and inspect tabs and columns.
- Diagnostics — channel error log, event tracing for a contact, human agent activity log and custom event logging.
- Portal and reference — documentation and news from the NicoChat portal, and the authoring reference that teaches the assistant to build flows and agents the right way.
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: if you connect with read access only, the write tools do not appear. You can expand later by reconnecting.
When authorizing, you define how long the connection is valid: 1, 7, 30 or 90 days, or no expiration. 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.
- 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 something stated in the conversation.
- Each connection operates only on the workspaces you own or administer. Attempts to access another workspace are refused.
- Every response goes through a sanitization layer that removes secrets. API tokens, integration keys and credentials are never returned to the client.
- Write operations validate the target workspace before running; in case of doubt, the operation fails instead of proceeding.
- The server operates 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 in your account.
- WhatsApp-specific tools require a business number approved by Meta and connected to the channel.
- Flows created or edited need to be published to go live.
- Some clients limit the total of active tools (VS Code, for example, accepts 128 per request). Connecting only with the permissions you need shortens the list.
Questions or problems with the MCP server: talk to NicoChat support through the usual service channels.