pplog MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PPLOG_ACCESS_TOKEN | Yes | Access token for pplog |
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 |
|---|---|
| get-poemA | Retrieves a poem from pplog by ID. |
| search-poemsA | Searches for poems in pplog with advanced query syntax support. |
| create-poemA | Creates a pplog poem: a casual short note (not literary verse). Posting hides your previous poem from other readers. |
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: create a poem, retrieve by ID, and search. No overlap.
Pattern is verb_noun with hyphens (create-poem, get-poem, search-poems), though 'poems' is plural for search while others use singular.
Three tools is borderline minimal for a typical CRUD surface, but may be appropriate if the domain is intentionally limited.
Missing update and delete operations; no way to modify or remove poems. Also lacks a list-all endpoint, forcing reliance on search.