Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

toolmenu

by niksa90version 0.28.1i★ 1iRuns on your computerRepository ↗
Registry nameio.github.niksa90/toolmenu

How to install

What it does

Tests MCP servers as clients meet them: menu, calls, results, sign-in, releases. No LLM.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Search & AI memory

Use together with

Skills that teach the AI this kind of work; they work alongside this one

timesfm

TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.

by google-research★ 35,6381 skills

Skill · How-to guide

Shadowbroker

Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…

by BigBodyCobain★ 11,6051 skills

Skill · How-to guide

google-maps-scraper

scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place

by gosom★ 8,2361 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity28/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score40/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 60 (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install toolmenu. Follow https://mcp.popnx.com/i/niksa90-toolmenu.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server toolmenu for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "toolmenu": { "command": "npx", "args": [ "-y", "toolmenu", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the toolmenu tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "toolmenu": {
          "command": "npx",
          "args": [
            "-y",
            "toolmenu",
            "mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use toolmenu and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using toolmenu or shows a toolmenu tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect toolmenu yet

toolmenu runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect toolmenu

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Search & AI memory that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server toolmenu for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user toolmenu -- npx -y toolmenu mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the toolmenu tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user toolmenu -- npx -y toolmenu mcp
  4. Type /mcp in Claude Code

    You should see toolmenu listed as connected

  5. Try it

    Use toolmenu and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using toolmenu or shows a toolmenu tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server toolmenu for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "toolmenu": { "command": "npx", "args": [ "-y", "toolmenu", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the toolmenu tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use toolmenu and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using toolmenu or shows a toolmenu tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server toolmenu for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "toolmenu": { "type": "stdio", "command": "npx", "args": [ "-y", "toolmenu", "mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the toolmenu tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use toolmenu and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using toolmenu or shows a toolmenu tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use toolmenu💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user toolmenu -- npx -y toolmenu mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "toolmenu": {
      "command": "npx",
      "args": [
        "-y",
        "toolmenu",
        "mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "toolmenu": {
      "command": "npx",
      "args": [
        "-y",
        "toolmenu",
        "mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "toolmenu": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "toolmenu",
        "mcp"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
1,924/wk
Connection
Runs on your computer
Latest versioni
0.28.1
Published to registryi
Nov 18, 2026
Code last changedi
Nov 19, 2026
Maker
niksa90
Packages
npm: toolmenu
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account niksa90, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed today

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked yet

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/niksa90-toolmenu.svg)](https://mcp.popnx.com/en/servers/niksa90-toolmenu)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Search & AI memoryi

  • More stars than 76% of the other 6430 servers in this category
  • Published to the registry more recently than 95% of the other 6430 servers in this category
  • Basic checks equal to or better than 99% of the other 6430 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is toolmenu safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed today, and the latest version (0.28.1) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

OpenSEO

Keyword research, site audits, rank tracking and AI visibility for your AI agent.

by every-appWidely used★ 28.3KUpdated 5 days ago

Runs in the cloud✓ everyapp.com

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

by exa-labsWidely used★ 5.2KUpdated 2 months ago

Runs in the cloud✓ service owner · exa.aiTried by the PopNx team

Microsoft Learn MCP

Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.

by MicrosoftDocsWidely used★ 2KUpdated 12 months ago

Runs in the cloud✓ service owner · microsoft.comTried by the PopNx team

Docs

Search and read Empryo's documentation. Read-only, no auth, no local access.

by proxysoulGrowing★ 1.6KUpdated 2 months ago

Runs in the cloud✓ empryo.com
Compared with similar ones
This one
toolmenu
OpenSEOExaMicrosoft Learn MCPDocsCOTAL actions (cotal.ai)
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoYesYesYesNoNo
Basic checks3/35/52/44/44/44/4
LicenseMITMITMITCC-BY-4.0NOASSERTIONApache-2.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

toolmenu

Tests your MCP server the way agents and clients meet it: the menu they read, the calls they make, the results and sign-in they get back, and every release after.

License

MIT

An MCP server can pass its own tests and still fail in the client. The client's SDK rejects a tool list the server's own test client accepted. A default built from the clock makes every listing different, so no prompt cache ever matches. A patch release makes a parameter required. None of it shows until someone's agent has fewer tools, or a bigger bill, and no error to explain it.

toolmenu does what a client does, in order, and checks each step against the spec, the tool's own schemas and each client's documented limits:

No LLM is involved, so the same server gives the same findings on every run and it fits in CI. It doesn't tell you whether an agent picks the right tool; that takes evals with a model (what it can't catch).

npx toolmenu snapshot -- node dist/server.js      # or: npx toolmenu snapshot https://example.com/mcp

npx toolmenu init -- node dist/server.js # CI: a baseline, a workflow, a comment on every PR

Needs Node 22 or later. Your server can be in any language: toolmenu starts it (stdio) or connects to it (HTTP).

Contents: What it catches · A finding · In CI · Commands · Tested on real servers · What it can't catch · Docs

What it catches

Each row is something a run on real servers found (docs/FINDINGS.md has the versions and how to reproduce each).

What goes wrongSeen on
Lists and results a client rejectsThe official SDK client validates tools/list and every result. One bad schema and it drops the whole list; an answer that breaks the tool's own outputSchema becomes an error12 of 1,089 registry servers: 8 lose every tool, 4 lose answers
A menu that never matches twiceA default built from the clock, an order from a hash set, a container ID in a description. Every listing or every restart is a new menu, so cached prompts missPayPal (list_transactions dates), mcp-atlassian, Desktop Commander
A menu that changes mid-conversationMost clients put tools first in the prompt, so a tool added by an "unlock" call means the conversation after it is processed again. 2026-07-28 rules per-connection menus outOne unlock re-processed 40–57K cached tokens in the author's own logs
Releases that break callersRemoved tools, new required parameters, narrowed types, a tool that became destructive, with the version bump the change needsThe official filesystem server made move_file destructive in a calendar release; Exa removed tools in patch releases
Sign-in a strict client can't finishOAuth discovery that differs from the RFCs: a resource that isn't the server's URL, metadata that isn't there, PKCE not advertised12 of 79 vendor endpoints that answer 401 name a parent or slash-variant resource
Tools one client can't useMore tools than the client sends, names its API refuses or rewrites, descriptions cut before the instruction that matters6 servers in Docker's catalog list more than VS Code's 128 a request
Tokens spent on nothingUnused $defs, the same schema block repeated across tools, growth per releaseNotion's server: the same 9 unused $defs in all 24 tools, 72% of its menu

It also has heuristics for what agents misread (a parameter called just id, writes with no annotations, two tools fighting over one word). Those are marked as guesses and are never errors. Every rule is in docs/RULES.md.

What a finding looks like

A server whose unlock_toolset tool adds two tools to the menu mid-conversation, run with toolmenu session:

step 3: call unlock_toolset {"toolset":"audits"} · answered · menu changed · +2 tools · list_changed received

ERROR session/mid-insert +2 tools inserted at position 1 (list_team_audits, get_team_audit). Invalidates the cached prompt: the tool list and the conversation after it are processed again. cost: the whole tool list (this server's part: ~406 tokens, estimate) and the conversation after it → Next: Add new tools at the end of the list, not in the middle; better, list them from the start. WARN session/unlock-coverage · unsure unlock_toolset looks like it unlocks tools, and the run got through 1 of its 2 toolset values. […] not unlocked: "reports" → Next: Unlock every value: session --init puts each one in the starter.

Every finding has the same parts: a level (ERROR, WARN, INFO; --fail-on decides which fail the run), a rule id you can look up (toolmenu explain session/mid-insert) or turn off in the config, where it happened (the step, the tool, the parameter path), what toolmenu saw, and a `→ Next:` step.

How much to trust a finding depends on what it rests on, and the rule id's prefix says which:

Rule familyWhat it rests on
spec/, apps/, lists/schemaThe protocol: the official JSON schema for the server's version (pinned in schemas/), a MUST/SHOULD in the spec, or the MCP Apps extension
diff/Two menus compared. A breaking change is one where a call that passed validation before now fails it
session/, menu/, lists/variance, auth/, catalog/Behaviour toolmenu observed: the menu changing after a step, between two calls, between two processes or connections, or served to a bad credential. The finding names the step or the call
naming/, ids/, description/, write/, search/How agents read the menu: names, words, descriptions. Tuned on real servers, but heuristics

A finding marked `· unsure`, in any family, rests on names and words rather than on something toolmenu saw happen (above: "looks like it unlocks tools"). It says what was seen, not what it means. No LLM is involved anywhere: the same server gives the same findings on every run.

In CI: one PR comment

npx toolmenu init -- snapshots the server into menu.json (the baseline) and writes this workflow for your project (Node, Python, Go or Rust). Commit both. Credentials you pass go into the workflow as ${{ secrets.… }}, never as text.

# .github/workflows/toolmenu.yml

on: pull_request permissions: contents: read pull-requests: write jobs: toolmenu: runs-on: ubuntu-latest steps:

  • uses: actions/checkout@v7
  • uses: actions/setup-node@v7 with: { node-version: 22 }
  • run: npm ci && npm run build
  • uses: niksa90/toolmenu@v0.28.1 with: command: node dist/server.js baseline: menu.json # your committed snapshot scenario: scenario.yml # optional: run a session too

Every pull request then gets one comment that updates on each push. It leads with a verdict (can this menu replace the baseline as it is?), then the breaking changes, the token change, the version bump the change needs, and anything session caught:

That's toolmenu review --format markdown on two real releases of the official filesystem server. The same findings go to GitHub code scanning (SARIF), to GitLab, Jenkins and others as JUnit, or into one offline HTML page:

Inputs, servers behind auth, forks and gate: review are in docs/github-action.md; SARIF, JUnit, HTML and the badge in docs/ci.md.

Commands

CommandWhat it does
snapshotConnects, lists the menu, checks it (the spec, a second process, your client's limits, token cost) and writes menu.jsondocs
sessionPlays a scenario, or builds one with --auto: calls tools, checks every result, and lists the menu after each step. Read-only tools unless you allow writes; --call-everything calls every tool, for a server in a sandboxdocs
diffCompares two menu files: breaking, minor, notice; token change; the semver bumpdocs
reviewShould the new menu replace the baseline? One verdict and an exit codedocs
auth checkWalks an HTTP server's OAuth discovery as a spec-following client does, without logging indocs
auth loginSigns in to a server behind OAuth once, in a browser; snapshot and session then use that logindocs
scansnapshot on every server in a client config (Claude Desktop, .mcp.json, Cursor, VS Code), side by sidedocs

| history | Installs a package's published versions one by one and diffs them. Runs third-party code: use a container | [docs](https://github.com/niksa90/toolmenu/blob/

Only the beginning is shown; read the rest in the repo