MCP Server / Getting Started

Connect MCP Inspector

Inspect every tool, every parameter, and every response with the official MCP debugger.

What you’ll do

Run the official MCP Inspector against the EPD MCP server, browse the tool catalog, and call tools by hand. This is the fastest way to understand and debug an MCP integration.

Prerequisites

  • Node.js 18+
  • A sandbox EPD API key

Run Inspector

npx @modelcontextprotocol/inspector

Inspector opens at http://localhost:5173.

Connect to EPD

In the Inspector UI:

  1. Transport type → Streamable HTTP
  2. URL → https://api.epd.com/mcp
  3. Headers → add:
    • Authorization: Bearer epd_test_sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    • epd-version: 2026-02-11
  4. Click Connect.

You should see a Tools tab populated with EPD’s tools.

Try a few calls

ping

Click ping → Run Tool with no arguments. You’ll get a small JSON response confirming the account.

list_customers

Click list_customers → set limit: 5 → Run Tool. You’ll see the first five customers in your sandbox account.

create_customer

Click create_customer → fill email, first_name, last_name, and phone (E.164 format, e.g. +14155551234) → Run Tool. Inspector shows you the exact request and response, including the new customer’s UUID id.

Why Inspector matters

Schema visibility

See the JSON schema for every tool — required params, types, descriptions.

Annotation flags

Read-only / destructive / idempotent / open-world hints are visible directly in the tool list.

Raw responses

Every response (including error envelopes) is shown verbatim — invaluable when debugging an agent’s tool call.

Repeatable bug reports

Inspector shows the exact JSON-RPC frame; paste it into a support ticket and we can reproduce instantly.