threadflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| validate_threadA | Run the per-post evidence check on a draft thread WITHOUT saving anything: 280-char platform limit per post, 25-post thread limit, empty-post detection, hook quality on post 1, and the links-on-final-post convention. Returns flags + an issue list WITH per-post evidence. Side effect: none (the registry only accepts drafts made with draft_thread). |
| draft_threadA | Validate a thread AND register the validated posts in the in-memory draft registry (keyed by the exact joined text; lost on restart — re-draft before finalizing). Returns the draftId and the validation report. post_thread/schedule_thread REJECT any posts array that was never drafted, with an error naming the exact text — the thread equivalent of the sibling's unscored-offer gate. |
| schedule_threadA | Schedule a VALIDATED draft to run at an ISO-8601 UTC time. Requires the exact posts to have been drafted with draft_thread first (the registry refuses unvalidated text). Accepts the optional marketing pre-flight score — score < 45 returns the kill-rule refusal and schedules nothing. In-memory only (lost on restart); this is workflow discipline, not a scheduler daemon. |
| post_threadA | Mark a VALIDATED draft as cleared to post NOW. Requires the exact posts to have been drafted with draft_thread first (refuses unvalidated text) and honors the optional pre-flight kill-rule gate (score < 45 -> refusal, verbatim sibling rule). This tool records the audit line; the actual platform POST is executed by the ThreadFlow app's authenticated path — this server holds no X credentials by design. |
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 4 tools
The four tools map to distinct workflow stages (validate, draft, schedule, post), and descriptions explicitly contrast validate_thread's no-side-effect dry run with draft_thread's registry write. The main residual overlap is that both validate and draft perform validation, so an agent could momentarily hesitate between them, but the side-effect distinction resolves it.
All four names follow a strict verb_noun snake_case pattern (validate_thread, draft_thread, schedule_thread, post_thread). The convention is predictable and the noun is consistent across the set.
Four tools is well-scoped for a narrow thread draft/validate/schedule/post workflow, and each tool clearly earns its place. Nothing feels padded or redundant.
The happy-path lifecycle is covered (validate -> draft -> schedule or post), but there is no way to edit a registered draft, list/inspect drafts, cancel a scheduled post, or discard a draft. The in-memory registry makes these gaps more painful, since a scheduled post cannot be unscheduled through the tool surface.