AllMCPs Server

What the AllMCPs Server MCP server does

The AllMCPs Server MCP server exposes the AllMCPs directory through MCP tools and a command-line interface. Agents can search listings by keyword or category, retrieve installation configuration and documentation for a server ID, and list directory categories with their server counts.

It also supports listing-management workflows. A user can submit a repository for indexing and review, verify ownership of an existing listing, inspect its boost and verified-badge status, or retrieve pricing and features for listing promotion. Boost initiation returns a Stripe checkout URL and an x402 invoice, according to the provided tool description.

How it works

The package is a local stdio bridge rather than a standalone directory database. It forwards MCP requests to the live remote endpoint at https://allmcps.com/api/mcp, and the remote service supplies the current tool behavior. This means new or changed tools can become available without a package upgrade, although the remote endpoint controls what is exposed at runtime.

With no subcommand, npx allmcps-server starts the MCP stdio process. When given a CLI subcommand, the package instead calls the public REST API and prints JSON to standard output. Supported examples include searching with search, listing categories with categories, retrieving one listing with server <id>, and displaying usage help with help. The JSON output can be combined with shell tools such as jq.

Setup and configuration

The AllMCPs Server MCP server requires Node.js 18 or newer. For a local MCP client, configure the command as npx with -y allmcps-server as its arguments. The documented configuration is suitable for Claude Desktop, and the package description also names Cursor, Windsurf, and other MCP-compatible agents.

ALLMCPS_MCP_URL optionally replaces the default remote endpoint. Set it when the bridge must target a different MCP URL; no other environment variables are documented.

Tools and capabilities

The available tools are:

• search_mcp_servers searches by keyword and/or category.
• get_mcp_install_config returns an installation snippet and documentation for a listing ID.
• list_mcp_categories returns categories and server counts.
• get_boost_pricing returns boost pricing and features.
• boost_mcp_server starts a boost order for a listing ID.
• get_boost_status reports boost and verified-badge status.
• submit_mcp_server submits a name, URL, and email, with optional schema fields available at runtime.
• verify_mcp_claim verifies ownership through a GitHub README badge, website badge, or DNS record.

Submissions enter a pending review queue. The response includes a claim URL and badge Markdown that can be added to a repository README to verify the listing.

Limitations and notes

The AllMCPs Server MCP server depends on the remote AllMCPs MCP or REST endpoint for its behavior and data. The README does not document offline operation, authentication requirements, rate limits, or guarantees about endpoint availability. Version 2 replaced the older submit_mcp tool with submit_mcp_server; clients depending on the old name should use version 1 instead. The package is released under the MIT license.