Connect Claude Desktop
Wire the EPD MCP server into Claude Desktop in one config file.
What you’ll do
Edit Claude Desktop’s MCP config so it can call EPD tools the same way it calls filesystem or web tools today.
Prerequisites
- Claude Desktop installed.
- A sandbox EPD API key (
epd_test_sk_...). - Node.js 18+ on your machine (Claude Desktop uses it to spawn local MCP wrappers if needed).
Configuration
Open Claude Desktop’s MCP config file:
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
Add EPD as an HTTP MCP server:
{
"mcpServers": {
"epd-commerce": {
"transport": {
"type": "http",
"url": "https://api.epd.com/mcp",
"headers": {
"Authorization": "Bearer epd_test_sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"epd-version": "2026-02-11"
}
}
}
}
}
This config file holds your API key in plain text on disk. Use a sandbox key, lock down filesystem permissions, and rotate if the machine is shared.
Restart Claude Desktop. Open a new conversation — you should see EPD’s tools appear in the tool picker.
First message
Try:
Using EPD, ping the account and tell me what merchant I’m connected as.
Claude will call ping and get_account and read the responses back.
Use sandbox vs. live carefully
Use epd_test_sk_.... Safe to experiment. No real money. Ideal for prompts that create, update, or delete.
Use epd_live_sk_... only when you mean it. Consider a restricted live key with read-only permissions if the agent only needs to look at reports.