allmcps-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_mcp_serversA | Search the AllMCPs directory for Model Context Protocol (MCP) servers by keyword or category. |
| get_mcp_install_configA | Get setup for one MCP server by ID: the config for every major client (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Cline, Zed, Codex, Gemini CLI, JetBrains, Roo Code, Continue, LM Studio) plus its documentation. Pass |
| get_mcp_alternativesA | List alternative MCP servers to a given server ID — same category, ranked by fit and evidence that they work. |
| compare_mcp_serversB | Compare 2 to 4 MCP servers side by side: transport, install command, evidence they work, tool count and source, health, GitHub stars, last commit and quality score. |
| recommend_mcp_stackA | Recommend a small stack of complementary MCP servers for a role or workflow (e.g. "fullstack web app", "data science", "devops on AWS"), drawn from a live directory search. |
| list_mcp_categoriesA | List all categories available in the AllMCPs directory along with server counts. |
| get_boost_pricingA | Get pricing and features for boosting / featuring an MCP server on AllMCPs.com. |
| boost_mcp_serverA | Initiate a sponsorship / boost order for an MCP server by ID, returning a Stripe checkout session URL and x402 invoice. |
| get_boost_statusB | Check current boost status, verified badge level, and sponsorship expiration for an MCP server by ID. |
| submit_mcp_serverA | Programmatically submit a new MCP server repository to AllMCPs.com for indexing and review. Supports the same optional enrichment fields as the human submission form — fill in whichever you can confidently determine from the repository (README, package.json, code) to produce a fully flushed-out listing. Omit anything you are not confident about rather than guessing; all enrichment fields are optional and unrecognized enum values are simply dropped, not rejected. |
| verify_mcp_claimA | Verify ownership and claim an MCP server listing by checking GitHub README badge, website badge, or DNS TXT record. Works two ways: (1) fully unattended — pass |
| register_mcp_agentA | Start unattended-agent registration: emails a 6-digit confirmation code to the given address. Follow up with confirm_mcp_agent to exchange the code for a bearer token, which unlocks verify_mcp_claim (and future privileged tools) without ever needing a human to sign in via browser. |
| confirm_mcp_agentA | Exchange the 6-digit code emailed by register_mcp_agent for a durable bearer token (90-day TTL). Pass the returned token as |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Most tools target distinct actions, but the discovery cluster (search_mcp_servers, get_mcp_alternatives, compare_mcp_servers, recommend_mcp_stack) has some conceptual overlap that could cause misselection. The boost trio (boost_mcp_server, get_boost_pricing, get_boost_status) and the auth flow (register/confirm/verify) are clearly separated by their descriptions.
All tools follow a strict verb_noun snake_case pattern (get_, list_, search_, compare_, recommend_, submit_, register_, confirm_, verify_, boost_). No deviations or mixed conventions, making the set highly predictable.
13 tools is well within the sweet spot for a directory-plus-account server, and each tool covers a distinct capability (discovery, submission, verification, sponsorship). Nothing feels redundant or missing from a count perspective.
The surface covers discovery, comparison, recommendation, submission, verification, and boost lifecycle well. A minor gap is the absence of a generic 'get single server by ID' for full details, though get_mcp_install_config and compare_mcp_servers partially fill that role.