papertrail-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAPERTRAIL_QA_API_TOKEN | No | API access token for the QA Papertrail environment. | |
| PAPERTRAIL_PROD_API_TOKEN | Yes | API access token for the production Papertrail environment. | |
| PAPERTRAIL_QA_API_BASE_URL | No | Base URL for the QA Papertrail environment (e.g., https://api.eu-01.cloud.solarwinds.com). | |
| PAPERTRAIL_PROD_API_BASE_URL | Yes | Base URL for the production Papertrail environment. | |
| PAPERTRAIL_STAGING_API_TOKEN | No | API access token for the staging Papertrail environment. | |
| PAPERTRAIL_STAGING_API_BASE_URL | No | Base URL for the staging Papertrail environment. |
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 |
|---|---|
| papertrail_list_environmentsA | List configured Papertrail credential environments without exposing their API tokens or URLs. |
| papertrail_getA | Make one authenticated GET request to the migrated Papertrail logs API at /v1/logs. This tool is read-only and may truncate large output. |
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 entirely distinct purposes: one lists configured credential environments, the other executes a generic GET request to the Papertrail API. There is no overlap or confusion between them.
Both tools use snake_case and are prefixed with 'papertrail_', but one follows a verb_noun pattern (list_environments) while the other is a bare verb (get). This is mostly consistent but not perfectly uniform.
With only two tools, the server is at the low end of the acceptable range. For its narrow read-only purpose, the minimal set is understandable, but it still feels thin compared to typical MCP servers.
The tool pair covers the essential workflow of identifying an environment and making an authenticated GET request, which is sufficient for basic read-only access. However, there is no dedicated search or pagination tool, though agents can work around this via the generic GET.