SCP Local MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCP_TEST_ENDPOINT | No | Endpoint to use for testing with a development server. This bypasses DNS discovery and directs all requests to your local test server. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scp_authorizeA | BEFORE USING THIS ENSURE THE DOMAIN SUPPORTS SCP BY CALLING scp_discover FIRST. Authorize access to a merchant's customer context via SCP. Must be called before accessing any customer data. IMPORTANT: You must ask the user for their REAL email address - never use placeholder emails like user@example.com. Ask: "What email address do you use with [Merchant]?" and wait for their response. |
| scp_check_authorizationC | Check if authorized with a merchant domain |
| scp_revoke_authorizationC | Revoke authorization with a merchant domain |
| scp_discoverC | Discover SCP endpoint for a merchant domain via DNS |
| scp_get_ordersA | Get order history from a merchant. Domain must be authorized first. |
| scp_get_loyaltyA | Get loyalty status and points from a merchant. Domain must be authorized first. |
| scp_get_offersA | Get active personalized offers from a merchant. Domain must be authorized first. |
| scp_get_preferencesA | Get saved customer preferences (sizes, styles, addresses) from a merchant. Domain must be authorized first. |
| scp_get_intentsB | Get shopping intents from a merchant. Domain must be authorized first. |
| scp_create_intentA | Create a new shopping intent with a merchant. Domain must be authorized with intent:create scope. |
| scp_update_intentB | Update an existing shopping intent. Domain must be authorized with intent:write scope. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| scp-usage-guide | How to use Shopper Context Protocol (SCP) tools |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose targeting specific SCP operations like authorization, discovery, data retrieval (intents, loyalty, offers, orders, preferences), and intent management. No overlap exists; for example, scp_get_intents and scp_get_offers retrieve different data types, and scp_authorize vs. scp_check_authorization handle separate authorization steps.
All tools follow a consistent scp_verb_noun naming pattern with snake_case throughout, such as scp_authorize, scp_get_intents, and scp_update_intent. This uniformity makes the tool set predictable and easy to navigate, with no deviations in style or structure.
With 11 tools, the server is well-scoped for SCP operations, covering authorization, discovery, data retrieval, and intent management without being excessive. Each tool serves a specific function in the SCP workflow, making the count appropriate for the domain's needs.
The tool set provides comprehensive coverage for SCP interactions, including authorization lifecycle (authorize, check, revoke), discovery, and full CRUD for intents (create, get, update) and retrieval of customer data (loyalty, offers, orders, preferences). A minor gap is the lack of delete operations for intents or other data, but core workflows are well-supported.