plurk-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLURK_APP_KEY | Yes | Plurk application key. | |
| PLURK_APP_SECRET | Yes | Plurk application secret. | |
| PLURK_ACCESS_TOKEN | Yes | Plurk access token for the target account. | |
| PLURK_MCP_DATA_DIR | No | Root directory for audit logs and policy state. | ./data |
| PLURK_MCP_TIMEZONE | No | Used for daily quota rollover and audit file partitioning. | UTC |
| PLURK_MCP_DEBUG_HOST | No | Debug server bind host. Defaults to 127.0.0.1. | 127.0.0.1 |
| PLURK_MCP_DEBUG_PORT | No | Debug server port. Must be a positive integer. | 3939 |
| PLURK_ACCESS_TOKEN_SECRET | Yes | Plurk access token secret for the target account. | |
| PLURK_MCP_DAILY_POST_LIMIT | No | Maximum number of new plurks per local day. Replies do not consume this budget. | 10 |
| PLURK_MCP_REPLY_COOLDOWN_MINUTES | No | Minimum cooldown between automatic replies in the same thread. | 15 |
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 |
|---|---|
| plurk_get_meC | Return the authenticated Plurk account profile for the credentials supplied in this call. |
| plurk_get_alertsC | Return recent normalized alert events for the credentials supplied in this call. |
| plurk_get_mentions_contextC | Return recent mention-driven interactions and context suitable for summarization or reply planning for the supplied credentials. |
| plurk_get_thread_contextA | Return the parent plurk and normalized replies for a specific thread using the supplied credentials. |
| plurk_postB | Create a new Plurk post for the supplied credentials while enforcing the server-side daily post quota. |
| plurk_replyB | Reply to an eligible Plurk thread for the supplied credentials when it is an owned thread or an explicit mention. |
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 6 tools
Each tool has a clearly distinct purpose: retrieving alerts, profile data, mentions context, thread context, creating a post, and replying to a thread. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent 'plurk_verb_noun' pattern (e.g., plurk_get_alerts, plurk_post). This uniformity in naming makes the tool set predictable and easy to understand.
With 6 tools, this server is well-scoped for interacting with Plurk's social platform. It covers key operations like reading data and posting content without being overly sparse or bloated.
The tool set provides good coverage for core Plurk interactions, including reading alerts, profile, mentions, threads, and posting/replies. A minor gap might be the lack of update or delete operations for posts, but the essential workflows are supported.