Payman AI Documentation MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-documentationC | Get PaymanAI documentation on a specific topic |
| search-documentationC | Search through PaymanAI documentation |
| get-code-examplesB | Get Node.js or Python code examples for PaymanAI integration |
| solve-problemC | Get help with common PaymanAI integration issues |
| get-sdk-helpC | Get help with Node.js or Python SDK usage |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| payman-overview |
TDQS
Scored across 5 tools
The tools have overlapping purposes that could cause confusion, particularly between get-documentation and search-documentation (both retrieve documentation content) and between get-sdk-help and solve-problem (both address integration issues). However, the descriptions provide some differentiation by specifying topics vs. search and SDK usage vs. general issues, which helps mitigate misselection.
All tool names follow a consistent verb_noun pattern with hyphens (e.g., get-code-examples, search-documentation). There are no deviations in naming conventions, making the set predictable and readable throughout.
With 5 tools, the server is well-scoped for its purpose of providing PaymanAI documentation and integration support. Each tool appears to serve a distinct role in the workflow, and the count is neither too sparse nor excessive for the domain.
The tool surface covers key documentation and integration support needs, including code examples, documentation retrieval, SDK help, search, and problem-solving. A minor gap exists in lacking tools for updating or managing documentation (e.g., edit or feedback functions), but agents can likely work around this for the server's stated purpose.