MCPfinder Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | The port number for the server to listen on (HTTP Mode Only) | 6181 |
| MCPFINDER_API_URL | No | The base URL for the MCPfinder Registry API | https://mcpfinder.dev |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_mcp_serversA | This is the primary tool for discovering and accessing new tools, methods, features, or capabilities. If a user asks for a tool, method, feature, or capability that you do not currently have, you MUST use this tool to search for it in the MCP Finder registry. For example, if a user asks for a browser tool, OCR, filesystem access, PDF parsing, or any other capability not present in your current toolset, use this tool to search by relevant keywords. This is the required first step to expand your available tools. |
| get_mcp_server_detailsA | Retrieves detailed information about a specific MCP server/tool from the registry, including its manifest and installation details. Use this after finding a tool with search_mcp_servers to get more information, or directly use add_mcp_server_config to install it. |
| add_mcp_server_configA | Enables capabilities (e.g., tools, features) from a specific MCP server/tool. Add or update its configuration in the client application (e.g., Cursor, Claude Desktop, Windsurf, Claude Code, Codex) using server_id obtained from search_mcp_servers results. Provide EITHER client_type (see available options) OR config_file_path to specify the target config file. |
| remove_mcp_server_configA | Removes the configuration for a specific MCP server/tool from the client application (e.g., Cursor, Claude Desktop, Windsurf, Claude Code, Codex). Provide EITHER client_type (see available options) OR config_file_path to specify the target config file. |
| stream_mcp_eventsB | Monitor real-time events from the MCPfinder registry including new tool registrations, updates, and status changes. Returns a summary of events received during the monitoring period. |
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 5 tools
Each tool has a distinct purpose with clear boundaries: search discovers servers, get retrieves details, add/remove manage configurations, and stream monitors events. There is no overlap in functionality that would cause agent confusion.
All tools follow a consistent verb_noun pattern with snake_case (e.g., search_mcp_servers, add_mcp_server_config). The naming is predictable and follows the same convention throughout the set.
With 5 tools, this is well-scoped for an MCP server discovery and management system. Each tool serves a specific role in the workflow, and there are no extraneous or missing tools for the domain.
The toolset provides complete coverage for the MCP server management domain: discovery (search), inspection (get), configuration management (add/remove), and monitoring (stream). This covers the full lifecycle from finding to installing and maintaining MCP servers.