Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"mcp-reasoner": {
"args": [
"C:\\Users\\[Username]\\path\\to\\mcp-reasoning-server\\dist\\index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server that provides advanced reasoning capabilities for Claude in Cursor AI.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / developer-tools
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
MCP Security Weekly
Get CVE alerts and security updates for Mcp Reasoning Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Notable Mentions :
https://github.com/Jacck/mcp-reasoner
Thanks for giving me the idea Jacck .
A Model Context Protocol (MCP) server that provides advanced reasoning capabilities for Claude in Cursor AI.
npm install
npm run build
Build the server first:
cd mcp-reasoning-server
npm run build
Open Cursor AI
Navigate to Settings > Features > MCP
Click the "+ Add new global MCP server" button
Enter the following details:
node C:\\Users\\[YourUsername]\\path\\to\\mcp-reasoning-server\\dist\\index.jsClick "Add"
Find your server in the list (it will initially show as "Disabled")
Click "Disabled" to toggle it to "Enabled"
Click the refresh button to load the available tools
A command prompt window will open automatically - this is your server running
As long as this command prompt window remains open, the reasoning tools will be available
Alternatively, you can manually edit your Cursor MCP configuration file at C:\Users\[Username]\.cursor\mcp.json (Windows):
{
"mcpServers": {
"mcp-reasoner": {
"command": "node",
"args": ["C:\\Users\\[Username]\\path\\to\\mcp-reasoning-server\\dist\\index.js"]
}
}
}
npm run build before restartingYou can use the reasoning tools directly in your Cursor AI conversations with Claude:
Use the /reason-mcts command followed by your query to start a MCTS-based reasoning chain:
/reason-mcts How can I optimize the performance of this React component?
Use the /reason-beam command for beam search-based reasoning:
/reason-beam What architecture would be best for this microservice system?
Use the /reason-r1 command for single-step Transformer-based reasoning:
/reason-r1 Analyze the complexity of this algorithm.
Use the /reason-hybrid command to combine Transformer and MCTS reasoning:
/reason-hybrid How should we approach refactoring this legacy codebase?
To make it easier for Claude to work with these reasoning tools, you can add the following custom instructions:
When I use commands like /reason-mcts, /reason-beam, /reason-r1, or /reason-hybrid in chat, interpret them as requests to use the corresponding reasoning tools:
/reason-mcts: Use the reason_mcts tool with the text following the command as the query
Example: "/reason-mcts How do I solve this problem?" should call the reason_mcts tool
/reason-beam: Use the reason_beam tool with the text following the command as the query
Example: "/reason-beam What's the best approach for this complex problem?" should call the reason_beam tool
/reason-r1: Use the reason_r1 tool with the text following the command as the query
Example: "/reason-r1 Analyze this code for performance issues" should call t
... [View full README on GitHub](https://github.com/AzDeltaQQ/Mcp-Reasoning-Server#readme)