mcp-variety
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VARIETY_MCP_WINDOW | No | How many recent picks and openings are remembered per scope | 12 |
| VARIETY_MCP_STATE_DIR | No | Folder that holds history.json | $XDG_STATE_HOME/mcp-variety, or ~/.local/state/mcp-variety |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Call variety_pick before writing each piece of a repeated writing job (posts, replies, emails and so on) and follow the protocol it returns. Use one stable scope label per account or project. Call variety_check on the draft before you hand it over. For approaches matched to each input, a voice and rules per account, and learning from results, see the hosted service Unsame: https://unsame.io
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| variety_pickA | Pick an approach and a form (opening, length, ending) for the next piece of writing. Call this before writing each piece of a repeated job. |
| variety_kindsB | List every kind of writing with its description, its approaches and the values of each form axis. |
| variety_checkA | Check a draft for common signs of AI writing. Flags em dashes, stock phrases, "not just X, but Y" constructions, evenly sized sentences and too many
exclamation marks. With |
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 role: variety_kinds enumerates options, variety_pick selects an approach/form, and variety_check audits a draft. The boundaries are explicit and an agent can easily choose the right tool for each step.
All tools share the predictable variety_ prefix, with pick and check using verb forms. variety_kinds is noun-oriented, a minor deviation, but the naming remains readable and consistent overall.
Three tools map cleanly to the workflow: discover kinds, pick a combination, then check the draft. The surface is well-scoped and each tool earns its place without excess.
The core lifecycle is covered: listing kinds, selecting a varied approach, and checking output for AI-writing patterns. Minor gaps exist around inspecting or resetting scope history, but these are not fatal to the stated purpose.