MCPVault
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_serversB | Search the MCPVault directory for MCP servers. Returns name, grade, status, star count, description, and listing URL for each result. |
| get_mcp_serverA | Retrieve full details for a specific MCP server by its MCPVault slug. Includes grade, verification status, repo, stars, license, client compatibility, topics, and tool list. |
| get_install_commandA | Get the install command for a specific MCP server by its MCPVault slug. Returns the command to add it to your AI client, plus the listing URL. |
| submit_mcp_serverA | Submit a GitHub repository to the MCPVault directory as a new MCP server listing. Use this when you find an MCP server on GitHub that is not yet in MCPVault. |
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 4 tools
Each tool has a clearly distinct purpose: searching the directory, fetching full details, retrieving an install command, and submitting a new server. There is minimal overlap between search results and full details, and the install command is a separate concern.
All tool names follow a consistent snake_case verb_noun pattern: search_mcp_servers, get_mcp_server, get_install_command, submit_mcp_server. The verbs and objects clearly indicate what each tool does.
Four tools is well-scoped for a directory service: search, retrieve details, get install command, and submit. Each tool earns its place without redundancy or bloat.
The core workflow is covered: discover servers, view details, get install instructions, and submit new ones. Minor gaps like listing all servers without a search query or managing existing submissions are not critical for the stated purpose.