Upvote.club Local MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UPVOTE_API_KEY | Yes | API key from https://upvote.club/api | |
| UPVOTE_API_URL | No | API base URL | https://api.upvote.club |
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 |
|---|---|
| list_platformsA | List all social platforms supported by Upvote.club with their available promotion actions, minimum price per action (in points), and example URLs. Call this first if you are unsure which platform or action applies to the link the user wants to promote. |
| get_api_referenceA | Full Upvote.club Public API reference for MCP: all tool inputs/outputs, request examples (single-action, MULTI_ACTION, meaningful comments), minimum prices per platform/action, billing rules, and complete error catalog. Call before create_task if unsure about fields or pricing. |
| create_taskA | Create a promotion task on Upvote.club. SPENDS points (price × actions_required, plan discount) and 1 daily slot. Call get_api_reference for examples and errors. Auto-detects platform from URL when social_network_code omitted. GitHub/Product Hunt min 16 pts/action; meaningful COMMENT min 64 pts/action. |
| get_task_statusA | Get status and progress of one or more Upvote.club tasks (actions completed, progress percentage, meaningful comment submissions). |
| delete_taskA | Delete an Upvote.club task. Refunds unused points and restores one daily task slot. Completed tasks cannot be deleted. Confirm with the user first. |
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 5 tools
Each tool has a clearly distinct purpose: create, delete, get reference, get status, list platforms. No overlap or ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (create_task, delete_task, get_api_reference, get_task_status, list_platforms).
5 tools is well-scoped for a promotion task service, covering creation, deletion, status checking, API reference, and platform enumeration without being excessive or insufficient.
Core CRUD operations are present (create, delete, read status), and supporting tools (API reference, platform list) enhance usability. Missing update/modify functionality is a minor gap.