About allmcps-server
allmcps-server is a local stdio MCP bridge and CLI for searching and managing listings in the AllMCPs.com directory. It serves developers and MCP-compatible agents, combining directory tools with scriptable JSON commands and a live remote tool set.
Key features
- 01Search servers by keyword and category
- 02Get installation configs for 13 clients
- 03Compare servers and find alternatives
- 04Browse categories and recommendations
- 05Submit, claim, and verify listings
- 06CLI commands output JSON
Use cases
- 01Find servers for a development workflow
- 02Retrieve setup instructions for a client
- 03Compare listings before choosing a server
- 04Submit or claim a directory listing
MCP support
Runs as a local stdio MCP server that bridges to AllMCPs.com's remote MCP endpoint. It exposes directory search, installation, comparison, submission, and listing-management tools.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y allmcps-serverALLMCPS_MCP_URLOverride the remote AllMCPs MCP endpoint this package bridges to.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project README
allmcps-server
The official local MCP server and CLI for AllMCPs.com — search, browse, get install configs for, and submit Model Context Protocol (MCP) servers directly from Claude, Cursor, any MCP-compatible agent, or a plain shell script.
This package is a thin stdio bridge to the AllMCPs remote MCP endpoint. Tool behavior lives server-side, so this package always exposes the current live tool set with no need to upgrade the package when a tool is added or changed.
v2.0.0 replaces the single
submit_mcptool with the full tool set below, including a renamedsubmit_mcp_server(previouslysubmit_mcp). If you depend on the old tool name, pinallmcps-server@1.
Install
Requires Node.js 18+. Add to your MCP client config (e.g. claude_desktop_config.json):
{
"mcpServers": {
"allmcps": {
"command": "npx",
"args": ["-y", "allmcps-server"]
}
}
}
CLI mode
Run with a subcommand instead of a bare npx allmcps-server and it becomes a plain scriptable CLI
over the public REST API — no MCP client needed:
npx allmcps-server search postgres # search the directory
npx allmcps-server categories # list every category
npx allmcps-server server <id> # full detail for one listing
npx allmcps-server help # usage
Each prints JSON to stdout, so it composes with jq and other Unix tools. With no subcommand it
runs as the MCP stdio server described below (the default npx allmcps-server behavior).
Tools
| Tool | Required arguments | Description |
|---|---|---|
search_mcp_servers | — | Search by keyword and/or category; optional transport (remote/stdio) and verified_only filters. |
get_mcp_install_config | id | Setup for a server in 13 clients (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Cline, Zed, Codex, Gemini CLI, JetBrains, Roo Code, Continue, LM Studio); optional client for one. |
get_mcp_alternatives | id | Alternatives to a server in the same category. |
compare_mcp_servers | ids (2 to 4) | Side by side: install, evidence it works, tools, health, stars, last commit, quality score. |
recommend_mcp_stack | role | A small stack of complementary servers for a role or workflow. |
list_mcp_categories | — | List all categories with server counts. |
get_boost_pricing | — | Get pricing and features for boosting/featuring a listing. |
boost_mcp_server | id | Start a sponsorship/boost order — returns a Stripe checkout URL and x402 invoice. |
get_boost_status | id | Check boost and verified-badge status for a listing. |
submit_mcp_server | name, url, email | Submit a new MCP server to the directory. |
verify_mcp_claim | id | Verify ownership and claim a listing via GitHub README, site badge, or DNS. |
register_mcp_agent | email | Start unattended-agent registration — emails a confirmation code. |
confirm_mcp_agent | email, code | Exchange the emailed code for a bearer token (see below). |
submit_mcp_server submissions land in the pending review queue at allmcps.com.
The response includes a claim_url and a ready-to-paste badge_markdown snippet — adding that badge to
your repo's README verifies the listing instantly instead of waiting on manual review.
verify_mcp_claim normally requires an active AllMCPs sign-in, which an unattended agent doesn't have.
To claim without a browser session: call register_mcp_agent, retrieve the code from the email it sends,
call confirm_mcp_agent to mint a bearer token, then pass that token as agentToken on verify_mcp_claim.
Full spec: https://allmcps.com/auth.md
Every tool's full input schema (including optional arguments like category, description, sku, and
method) is available at runtime via the standard MCP tools/list call, or by inspecting
/api/mcp directly.
Configuration
| Environment variable | Default | Purpose |
|---|---|---|
ALLMCPS_MCP_URL | https://allmcps.com/api/mcp | Override the remote endpoint this package bridges to. |
Related
- Directory API docs: https://allmcps.com/docs/api
- Remote MCP server (same tools, called directly over HTTP): https://allmcps.com/api/mcp
- Also listed on the official MCP Registry as
io.github.Jackalope-Dev/allmcps-server, Glama, and the LobeHub Marketplace
License
MIT © Jackalope Digital — see LICENSE.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.