Plugolis MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLUGOLIS_API_URL | No | Where to read the data | https://plugolis.com/api |
| PLUGOLIS_CACHE_TTL_MS | No | How long to cache the data, in milliseconds (15 min) | 900000 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_serversA | Search the Plugolis directory of MCP servers. All filters are optional; with no arguments it lists every server. Returns name, slug, category, status and a link for each match. Use get_server for install details. |
| get_serverA | Full details for one MCP server by slug: description, install command, ready-to-paste config JSON, required env vars, maintenance status and links. |
| list_categoriesA | List every Plugolis server category with its slug, number of servers and the server slugs in it. |
| search_fixesA | Find step-by-step fixes for MCP errors. Paste the error message (or describe the problem) and optionally filter by client. Returns matching fixes; use get_fix for the full steps. |
| get_fixA | The full fix for one MCP error by slug: the exact error, its cause, numbered steps with code, and sources. |
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
The set forms two clean search/get pairs for distinct resources (servers and fixes), so an agent can easily tell which to call. The only mild overlap is between search_servers with no arguments (lists every server) and list_categories (lists categories plus their server slugs), but the descriptions clarify the intended split.
All five tools follow a strict verb_noun snake_case pattern: search_servers, get_server, list_categories, search_fixes, get_fix. The search/get/list verbs are used predictably for the same resource actions throughout.
Five tools is a lean but sensible surface for a read-only directory covering two content types plus categorization. It sits at the low edge of the ideal range; nothing is redundant, though the set is thin enough that any missing lookup path would be noticeable.
Search and retrieval are covered for both the server directory and the error-fix library, which matches the read-only nature of the domain. Minor gaps exist, such as no direct tool to enumerate servers within a given category without going through search_servers, but agents can bridge this easily.