SCP Local MCP Server
OfficialUses SQLite for encrypted local storage of authentication tokens and configuration data
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SCP Local MCP Server show me my recent orders from Amazon"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SCP Local MCP Server
A Model Context Protocol (MCP) server that provides AI assistants like Claude with secure access to customer data through the Shopper Context Protocol (SCP).
What is this?
This MCP server acts as a bridge between AI assistants and e-commerce systems that implement the SCP protocol. It enables Claude Desktop and other MCP clients to:
š Securely authorize access to customer accounts using OAuth 2.0 with PKCE
š¦ Retrieve order history, loyalty points, active offers, and shopping preferences
š Discover SCP endpoints for merchants via DNS or well-known URIs
š Store and manage encrypted authentication tokens locally
All customer data requests are authenticated and authorized by the merchant's SCP server, ensuring privacy and security.
Related MCP server: ACP Commerce MCP Server
Quick Start with npx
The easiest way to use this server is with npx - no installation required!
With Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"scp": {
"command": "npx",
"args": ["-y", "@shoppercontextprotocol/local-mcp-server"]
}
}
}On Windows, the config file is located at: %APPDATA%\Claude\claude_desktop_config.json
Testing with a Local Development Server
If you're developing an SCP server locally, you can configure the MCP server to point to your test endpoint:
{
"mcpServers": {
"scp": {
"command": "npx",
"args": ["-y", "@shoppercontextprotocol/local-mcp-server"],
"env": {
"SCP_TEST_ENDPOINT": "http://localhost:8787/v1"
}
}
}
}This bypasses DNS discovery and directs all requests to your local test server.
Installation (Alternative)
For development or if you prefer a local installation:
# Install globally
npm install -g @shoppercontextprotocol/local-mcp-server
# Or install locally for development
git clone <repository>
cd local_mcp
npm install
npm run buildUsage
With Claude Desktop (Local Installation)
{
"mcpServers": {
"scp": {
"command": "scp-mcp-server"
}
}
}Or with a local build:
{
"mcpServers": {
"scp": {
"command": "node",
"args": ["/absolute/path/to/local_mcp/dist/index.js"]
}
}
}Direct Usage
# If installed globally
scp-mcp-server
# Or with local build
npm startDevelopment
npm run dev # Watch mode
npm run build # Production build
npm test # Run testsConfiguration
The server stores configuration in ~/.scp/config.json. It will be created automatically on first run with these defaults:
{
"dns_resolver": "1.1.1.1",
"dns_cache_ttl": 86400,
"poll_interval": 2,
"max_poll_attempts": 150,
"token_refresh_threshold": 300,
"request_timeout": 30000,
"demo_mode": true,
"demo_endpoint": "http://localhost:8787/v1"
}Configuration Options
dns_resolver: DNS server to use for SCP endpoint discovery (default: Cloudflare's 1.1.1.1)dns_cache_ttl: How long to cache discovered endpoints in seconds (default: 24 hours)poll_interval: Seconds between polling attempts during OAuth flow (default: 2)max_poll_attempts: Maximum number of polling attempts (default: 150 / 5 minutes)token_refresh_threshold: Seconds before expiry to refresh tokens (default: 300 / 5 minutes)request_timeout: HTTP request timeout in milliseconds (default: 30000 / 30 seconds)demo_mode: Enable demo mode (default: true)demo_endpoint: Endpoint to use in demo mode (default: http://localhost:8787/v1)
Testing with a Development Server
There are multiple ways to point the MCP server to your test SCP server:
Option 1: Environment Variable (Recommended for npx)
Set SCP_TEST_ENDPOINT when running the server:
# Direct usage
SCP_TEST_ENDPOINT=http://localhost:8787/v1 scp-mcp-server
# With npx
SCP_TEST_ENDPOINT=http://localhost:8787/v1 npx @shoppercontextprotocol/local-mcp-server
# In Claude Desktop config (see Quick Start section above)Option 2: Demo Mode Configuration
Edit ~/.scp/config.json:
{
"demo_mode": true,
"demo_endpoint": "http://localhost:8787/v1"
}By default, demo mode is enabled and directs all SCP requests to the demo endpoint. This is useful for local testing without needing DNS records.
Option 3: Production Mode
To use real DNS-based discovery for production merchants:
{
"demo_mode": false
}Priority Order:
SCP_TEST_ENDPOINTenvironment variable (highest priority)Demo mode configuration
DNS-based discovery (lowest priority)
Data Storage
Tokens:
~/.scp/tokens.db(SQLite, encrypted)Config:
~/.scp/config.json
MCP Tools
scp_authorize- Authorize access to a merchantscp_check_authorization- Check authorization statusscp_revoke_authorization- Revoke access to a merchantscp_discover- Discover SCP endpoint for a domain
MCP Resources
scp://{domain}/orders- Order historyscp://{domain}/loyalty- Loyalty statusscp://{domain}/offers- Active offersscp://{domain}/preferences- Customer preferencesscp://{domain}/intents- Shopping intents
How to Use in Claude Desktop
After adding the MCP server to your Claude Desktop config and restarting Claude, you can interact with SCP-enabled merchants:
First Time: Authorize Access
Can you help me authorize access to my Boot Barn account?
My email is customer@example.comClaude will use the scp_authorize tool to:
Discover the SCP endpoint for bootbarn.com
Initiate OAuth authorization with a magic link
The magic link will be sent to your email
Poll for authorization completion
Store encrypted tokens locally
Access Your Data
Once authorized, you can ask Claude to retrieve your data:
What are my recent Boot Barn orders?How many loyalty points do I have at Boot Barn?Do I have any active offers or coupons?Claude will automatically:
Use the stored authorization tokens
Refresh tokens if they're about to expire
Fetch data from the merchant's SCP server
Present the information in a helpful format
Check Authorization Status
Am I authorized with Boot Barn?Revoke Access
Revoke my Boot Barn authorizationExample Workflow
Here's a complete example of using SCP in Claude Desktop:
You: "Help me authorize with acmestore.com using customer@example.com"
Claude: Initiates OAuth flow, sends magic link to email
You: Clicks magic link in email
Claude: Completes authorization and confirms success
You: "What orders have I placed?"
Claude: Retrieves and displays order history
You: "Do I have any active coupons?"
Claude: Shows available offers and promotions
How It Works: Initialization Instructions
The SCP MCP Server provides built-in instructions to Claude during the initialization phase, ensuring it knows how to properly use the SCP tools without any additional prompting.
Automatic Guidance
When Claude Desktop connects to the SCP server, it automatically receives instructions that tell it to:
Always check authorization first - Before accessing any customer data, Claude will check if you're authorized with the merchant
Ask for your email - If not authorized, Claude will ask for your email address to start the OAuth flow
Request all necessary scopes - Claude requests comprehensive permissions upfront:
orders,loyalty,preferences,intent:read,intent:createExplain the magic link process - Claude tells you to check your email for the authorization link
Handle errors gracefully - If something goes wrong, Claude knows how to guide you through fixing it
Why This Matters
This automatic initialization means:
ā No manual configuration needed - Claude knows how to use SCP tools immediately
ā Consistent behavior - Every conversation follows the same authorization workflow
ā Better user experience - Claude proactively handles authorization before trying to access data
ā Fewer errors - Reduces "Not authorized" errors by checking authorization first
The Initialization Flow
1. Claude Desktop starts and reads claude_desktop_config.json
2. Spawns the SCP MCP server (node dist/index.js or npx)
3. Sends initialize request to the server
4. Server responds with:
- Server info (name, version)
- Instructions for the LLM
- Capabilities (tools, resources)
5. Claude reads the instructions and knows:
ā Check authorization first
ā Ask for email when needed
ā Request all scopes upfront
ā Create intents when users express shopping goals
6. Server is ready, Claude is ready with full context
7. User asks: "Show me my orders"
8. Claude follows the instructions:
- Checks authorization
- Asks for email if needed
- Initiates OAuth flow
- Retrieves and displays ordersExample Instructions Provided
During initialization, Claude receives these instructions:
IMPORTANT WORKFLOW:
1. AUTHORIZATION REQUIRED FIRST
Before accessing ANY customer data, you MUST authorize with the merchant domain.
Check authorization:
- scp_check_authorization(domain="acmestore.com")
If not authorized:
- Ask user: "What email do you use with [Merchant]?"
- Call: scp_authorize(domain="...", email="...", scopes=[...])
- Tell user: "Please check your email for a magic link"
2. ACCESSING DATA
Once authorized, use these tools:
- scp_get_orders(domain="...") - Order history
- scp_get_loyalty(domain="...") - Loyalty status
- scp_get_preferences(domain="...") - Saved preferences
- scp_get_intents(domain="...") - Shopping intents
3. CREATING INTENTS
When user expresses a shopping goal, create an intent:
- scp_create_intent(domain="...", base_intent="...", context={...})
REMEMBER:
ā
ALWAYS check authorization before accessing data
ā
Request comprehensive scopes upfront
ā
Create intents when users express shopping goals
ā NEVER access data without authorization firstThis ensures every interaction with the SCP server follows best practices and provides a smooth, secure experience for users.
Available Tools
11 toolsscp_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.
Inputs: domain (required), email (required), scopes (required).
scp_check_authorizationC
Check if authorized with a merchant domain
Inputs: domain (required).
scp_create_intentA
Create a new shopping intent with a merchant. Domain must be authorized with intent:create scope.
Inputs: base_intent (required), domain (required), ai_assistant, context, +2 more.
scp_discoverC
Discover SCP endpoint for a merchant domain via DNS
Inputs: domain (required).
scp_get_intentsB
Get shopping intents from a merchant. Domain must be authorized first.
Inputs: domain (required), limit, status.
scp_get_loyaltyA
Get loyalty status and points from a merchant. Domain must be authorized first.
Inputs: domain (required).
scp_get_offersA
Get active personalized offers from a merchant. Domain must be authorized first.
Inputs: domain (required), active_only.
scp_get_ordersA
Get order history from a merchant. Domain must be authorized first.
Inputs: domain (required), limit, offset, status.
scp_get_preferencesA
Get saved customer preferences (sizes, styles, addresses) from a merchant. Domain must be authorized first.
Inputs: domain (required).
scp_revoke_authorizationC
Revoke authorization with a merchant domain
Inputs: domain (required).
scp_update_intentB
Update an existing shopping intent. Domain must be authorized with intent:write scope.
Inputs: domain (required), intent_id (required), add_milestone, context, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
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.
Related MCP Connectors
Shop connected e-commerce stores: search, compare, cart, and checkout with buyer approval.
Real-time data APIs for 50+ commerce, grocery, social and maps platforms over one OAuth MCP server
Agentic commerce + trust MCP: discover, verify, and transact across droplinked's merchant network.
Remote MCP for Living Stack offer discovery and buyer-authorized checkout preparation.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform e-commerce operations including product search, budget-constrained shopping recommendations, and sustainability analysis. Includes a secure HTTP bridge with OAuth integration and observability features for production deployment.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform e-commerce operations through a standardized interface implementing the x402 and Agentic Commerce Protocol (ACP). Supports merchant sessions, product search, and payment orchestration with production-ready security features.-
- AlicenseNot gradedqualityCmaintenanceEnables AI shopping agents to search products, check stock, apply promotions, manage cart sessions, and create cryptographically signed checkout sessions on e-commerce storefronts, while giving merchants analytics into agent intent and catalog demand gaps.MIT

com.upscrape/mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables AI clients to retrieve real-time structured data from 50+ commerce, grocery, social, and maps platforms over a remote MCP server using OAuth authentication.1MIT