mcp-server-collector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_MODEL | Yes | OpenAI model to use for processing | gpt-4o-mini |
| OPENAI_API_KEY | Yes | OpenAI API key for accessing OpenAI services | |
| OPENAI_BASE_URL | Yes | Base URL for OpenAI API | https://api.openai.com/v1 |
| MCP_SERVER_SUBMIT_URL | Yes | URL endpoint to submit MCP Server information | https://mcp.so/api/submit-project |
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 |
|---|---|
| extract-mcp-servers-from-urlC | Extract MCP Servers from a URL |
| extract-mcp-servers-from-contentC | Extract MCP Servers from given content |
| submit-mcp-serverC | Submit MCP Server to MCP Servers Directory like mcp.so |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: extracting servers from content, extracting from a URL, and submitting to a directory. The descriptions make it unambiguous which tool to use for each scenario, preventing misselection.
All tool names follow a consistent verb_noun pattern with hyphens (e.g., extract-mcp-servers-from-content, extract-mcp-servers-from-url, submit-mcp-server). This predictable naming scheme enhances readability and usability for agents.
With 3 tools, the server is well-scoped for its purpose of collecting and submitting MCP servers. Each tool earns its place by covering distinct aspects of the workflow, avoiding bloat or thinness.
The tool set covers the core workflow of extraction (from content and URLs) and submission, with no obvious dead ends. A minor gap might be the lack of tools for managing or listing already submitted servers, but agents can work around this with the existing tools.