atodeyomu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLIENT_ID | Yes | OAuth 2.0 Client ID from X Developer Portal | |
| CLIENT_SECRET | Yes | OAuth 2.0 Client Secret from X Developer Portal |
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_quoted_postsA | 前回確定したカーソル以降の引用ポスト（あとで読む用の引用リツイート）と引用元コンテンツを取得する。カーソルは進めない。 |
| commit_cursorA | 下流処理（Notion 保存など）の成功を確認した後に呼び、取得位置カーソルを確定する。X API は呼ばない。 |
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 completely distinct purposes: one confirms cursor progression after downstream success, the other retrieves new quoted posts. No overlap or ambiguity.
Both tool names follow a consistent verb_noun snake_case pattern ('commit_cursor', 'get_quoted_posts'), making them predictable and clear.
With only 2 tools, the server feels minimal. While it may be sufficient for a focused task, it borders on being too thin compared to typical well-scoped servers (3-15 tools).
The tool set covers the core workflow of retrieving new posts and committing progress. No obvious missing operations for the stated purpose, though additional features like resetting a cursor could be useful.