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 the exact claude_desktop_config.json setup snippet and documentation for a specific MCP server by ID. |
| recommend_mcp_stackB | Recommend a curated multi-tool MCP server stack for a specific developer role or workflow (e.g. "fullstack", "data science", "devops"). |
| 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_statusA | 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. |
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 9 tools
Each tool targets a distinct function within the directory workflow, from search and install config to submission and boost payments. The only mild overlap is between verify_mcp_claim and get_boost_status, since both touch verified badge status, though one is an action and the other is a status query.
All tools follow a consistent snake_case verb_noun pattern (search_, get_, list_, verify_, boost_, submit_). There are no mixed conventions or vague generic verbs, making the tool surface predictable.
Nine tools is well-scoped for a directory and marketplace server: discovery, retrieval, submission, claiming, and promotional payments are each represented. It fits comfortably within the ideal 3-15 tool range.
Core workflows are covered, including searching, retrieving install config, submitting a server, claiming ownership, and managing boost orders. However, there is no update or delete path for an existing listing and no general get-server-details tool beyond the install config, leaving notable lifecycle gaps.