mcplex
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 | {
"listChanged": true
} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mcplex_find_toolsA | Search for available tools by describing what you want to do. Returns the most relevant tools with their full schemas. Always call this before using mcplex_call_tool. |
| mcplex_call_tool | Execute a tool discovered via mcplex_find_tools. Pass the exact tool name and arguments as specified in the tool's schema. |
| mcplex_list_categoriesA | List all available tool categories (server groups) with tool counts. Use this to explore what's available before searching. |
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 2 tools
The two tools have clearly distinct purposes: one searches for tools by description, the other lists categories. There is no overlap.
Both tools follow a consistent verb_noun pattern with the 'mcplex_' prefix: find_tools and list_categories.
With only 2 tools, the server feels minimal for a discovery service. The referenced mcplex_call_tool is missing, making the count seem incomplete.
The set lacks the mcplex_call_tool mentioned in mcplex_find_tools description, leaving an obvious gap for actually executing tools.