Skip to main content
Cursor supports stdio MCP servers, and remote Streamable HTTP MCP servers with OAuth authentication. The client starts the MoleSignal CLI, which carries the messages to MoleSignal. It needs Node.js 20 or later.
1

Sign in once

The browser opens on MoleSignal to approve the sign-in; the CLI keeps it and renews it.
2

Add MoleSignal

In .cursor/mcp.json for the project, or ~/.cursor/mcp.json for every project:
Then turn molesignal on under Tools & MCP.
Where no browser is at hand, set MOLESIGNAL_URL and MOLESIGNAL_TOKEN (an API token) in the server’s environment instead of signing in. See Connect over stdio. The sections below connect over Streamable HTTP, without the CLI.

​
Configure the server

Create .cursor/mcp.json for the current project, or ~/.cursor/mcp.json for a global configuration:
1

Open Tools & MCP

Open Cursor Settings → Tools & MCP and locate molesignal.
2

Connect with OAuth

Select Connect and complete the MoleSignal authorization page. Cursor discovers the OAuth endpoints from the MCP protected-resource metadata.
3

Verify tools

Confirm that tool_search, call_read_tool, and call_managed_tool appear in the available tools. Restart the server from Tools & MCP after changing the configuration.
Do not commit a Bearer token in .cursor/mcp.json. Prefer OAuth for an interactive Cursor session. Use a client-supported secret injection mechanism for non-interactive credentials.
See the official Cursor MCP documentation.
Last modified on October 18, 2026