AllMCPs Server

What AllMCPs Server does

AllMCPs Server gives MCP-compatible clients access to the AllMCPs.com directory and its listing-management operations. Agents can search servers by keyword or category, filter results by transport or verification status, inspect categories and server details, and retrieve installation configurations for supported clients.

The server also supports evaluation and selection workflows. An agent can compare two to four listings using factors such as transport, installation command, tool count, operational evidence, health, GitHub activity, and quality score. It can find alternatives within a category or request a small group of complementary servers for a role such as data science, DevOps on AWS, or full-stack web development.

Listing owners can use the management tools to submit a repository, check boost pricing and status, start a sponsorship order, or verify ownership. Unattended agents can register by email, confirm a six-digit code, and use the resulting bearer token for claim verification.

How it works

With no subcommand, npx allmcps-server starts a local stdio MCP process. The package forwards MCP requests to https://allmcps.com/api/mcp, so the tool implementation and available tool set are maintained by the remote service. Clients communicate with the local process using their normal MCP configuration.

The package also accepts CLI subcommands instead of starting an MCP server. Commands such as search postgres, categories, and server <id> call the public AllMCPs REST API and print JSON to standard output. This makes the CLI usable from shell scripts and composable with tools such as jq.

Setup and configuration

Node.js 18 or newer is required. Add the following server entry to an MCP client's configuration:

{
  "mcpServers": {
    "allmcps": {
      "command": "npx",
      "args": ["-y", "allmcps-server"]
    }
  }
}

The ALLMCPS_MCP_URL environment variable changes the remote MCP endpoint used by the local bridge. It defaults to https://allmcps.com/api/mcp.

For shell use, invoke the package with a supported subcommand, for example npx allmcps-server search postgres or npx allmcps-server categories.

Tools and capabilities

• Search by keyword or category, with optional remote/stdio and verified-only filters.
• Retrieve installation configuration for Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Cline, Zed, Codex, Gemini CLI, JetBrains, Roo Code, Continue, or LM Studio.
• Compare listings, find same-category alternatives, and recommend complementary server stacks.
• List directory categories and their server counts.
• Submit a repository for indexing and review, with optional enrichment fields.
• Start and inspect listing boosts, including Stripe checkout and x402 invoice details.
• Verify ownership through a GitHub README badge, website badge, or DNS record.

Submissions enter a pending review queue. A submission response includes a claim URL and badge Markdown. The unattended claim flow uses register_mcp_agent, confirm_mcp_agent, and then verify_mcp_claim with the returned token.

Limitations and notes

The local package is a bridge rather than an independent directory database; requests depend on the configured remote endpoint. Its default behavior is MCP stdio, while CLI mode uses the public REST API. Submission and claim operations have authorization and usage requirements, including submitting a server on behalf of the person authorized to list it and avoiding bulk or unattended submissions.