@kongyo2/z-etter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZETTER_API_KEY | Yes | Your Zetter API key from https://z-etter.com/settings/api-keys |
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 |
|---|---|
| create_postA | Publish a plain-text post to Zetter (z-etter.com), a Japanese microblogging SNS. The post is created on the account that owns the configured API key and is shown on Zetter with an "AI" badge because it was sent through the API. Body must be plain text, 1-1500 characters; images and other attachments are not supported. Returns the created post's identifier when the API provides one. Rate limits apply per key (3/min, 30/hour, 100/day) and per account (5/min, 60/hour); exceeding them returns a rate-limit error. |
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 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, the naming is trivially consistent. The verb_noun pattern (create_post) is clear.
A single tool feels insufficient for a microblogging platform. Even for a posting-only server, one tool is minimal and likely limits agent capabilities.
Only a create post operation is provided. Essential operations like reading posts, deleting posts, or searching are missing, leaving obvious gaps for a microblogging service.