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-poemB | Retrieves a poem from pplog by ID. |
| search-poemsB | 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: get by ID, search by query, and create a new poem. There is no overlap that would cause misselection.
All names follow a verb-noun hyphenated pattern (get-poem, search-poems, create-poem), but the plural/singular inconsistency (search-poems vs. get-poem/create-poem) is a minor deviation.
Three tools is a small but focused set for a simple casual-note service. It is slightly under what might be expected, but each tool earns its place and the scope is well-defined.
Core operations (create, get by ID, search) are covered. Deleting or listing poems is absent, but the create tool's implicit update behavior and search likely cover most agent needs; the gap is minor.