Sweeppea 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 |
|---|---|
| sweeppea_connectA | Returns connection details and configuration instructions for the Sweeppea MCP Server. This remote server provides 109 tools across 20 categories for managing legally compliant sweepstakes promotions in the United States and Canada. Use this tool to obtain the endpoint URL, required authentication headers, and platform-specific setup guides for Claude Desktop, Cursor, Windsurf, and other MCP clients. Requires an active Sweeppea subscription and API key from sweeppea.com. |
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
With only a single tool, there is no possibility of overlap or misselection between tools. The lone tool has a clear, distinct purpose (returning connection details), though it is a meta/gateway tool rather than domain functionality.
The single tool follows a clear snake_case pattern with a vendor prefix (sweeppea_connect), which is readable and predictable. Consistency cannot be meaningfully assessed with one tool, but no naming issues are present.
Exposing only 1 tool for a server that advertises 109 tools across 20 categories is a severe mismatch. The lone tool provides no actual sweepstakes functionality, making the surface effectively empty.
The surface offers no CRUD or lifecycle operations for the stated sweepstakes domain; users must fetch connection details and then rely entirely on an external server. No create/read/update/delete or promotion management capabilities are exposed here.