Add the server in mcp.json, click connect and authorize in the browser.
2026-09-08
In Cursor, the NicoChat server goes into mcp.json as a remote server by URL. Cursor detects that the server requires OAuth, shows a login button and opens the browser for authorization in NicoChat. After that, the chat agent uses the NicoChat tools like any other.
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.
Cursor up to date. Support for OAuth on remote servers has existed since the 2025 versions; older versions only accept local servers.
Step by step
1
Open the MCP settings
Go to Cursor Settings › Tools & MCP and click Add Custom MCP. Cursor opens your user mcp.json file.
2
Declare the server
Paste the block below. To apply it to a single repository, put the same content in .cursor/mcp.json at the project root.
3
Connect
Save the file. In the server list, NicoChat shows up with a login notice. Click Connect (or Needs login): the browser opens on the NicoChat authorization.
4
Authorize
Log in, choose permissions and validity and confirm. Back in Cursor, the server turns green and lists the tools.
5
Use it in the chat
In the chat in Agent mode, ask NicoChat for something. Cursor asks for confirmation before each tool, unless you turn on automatic execution.
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 validity of the connection: 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 the 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
With the connection in place, ask Cursor in natural language. Some examples that use read only:
"List my workspaces and the channels in each one."
"How many contacts entered 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 inside a flow stays as a draft until you publish it in NicoChat.
Tool limit
Cursor limits how many tools stay active at the same time. NicoChat exposes many of them; if you have other servers, turn off the ones you are not using in Tools & MCP, or connect to NicoChat only with the permissions you need.
Disconnect or revoke
In the client: remove the nicochat block from mcp.json, or turn the server off in Tools & MCP.
In NicoChat: in Account Settings, revoke the authorization. The effect is immediate, even if the server is still registered in the client.
Common problems
Update Cursor. If the browser still does not open, remove the block, save, paste it again and save: Cursor redoes the server discovery.
Check that the chat is in Agent mode, not Ask. And check that the server is switched on in the Tools & MCP list.
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 validity you chose during authorization expired. Reconnect and, if you prefer, choose "no expiration".
