payplug-docs-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_payplug_docsA | List the official Payplug documentation pages known to this MCP. |
| read_payplug_docA | Read an official Payplug documentation page. Only URLs under https://docs.payplug.com/ are accepted. |
| search_payplug_docsA | Search the configured official Payplug documentation pages. The search is intentionally simple and read-only. It fetches the configured documentation pages, converts them to plain text, ranks them by occurrences of the query terms, and returns excerpts from the best matches. |
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: reading a specific page, searching across pages, and listing known pages. There is no meaningful overlap or ambiguity between them.
All tool names follow a verb_noun pattern with the common 'payplug_doc' prefix. The only minor inconsistency is that 'read_payplug_doc' uses singular 'doc' while the other two use plural 'docs'.
Three tools is well-scoped for a documentation MCP. Each tool covers a necessary operation without redundancy or bloat.
The standard documentation access workflow is fully covered: list available docs, search within them, and read a specific page. There are no obvious missing operations for this domain.