Bring your own MCP — Point Mockd at your server

Bring your own MCP

Already built your own MCP server? Point Mockd at it.

Point Mockd at any server that speaks MCP.Connect a custom server

terminalbash

$ mockd connect https://tools.acme.internal/mcp \

--name acme-internal \

--capture all

✓ connected · 14 tools discovered

✓ trace endpoint ready → mock.mock-d.com/byo/8f2c/mcp

watching for tool calls▋

How the proxy works

Mockd sits between your agent and your server

Mockd plays two roles at once: an MCP server to your agent, and an MCP client to your real server. Every message passes straight through — and gets recorded on the way.

Your agent

Your MCP server

→ initialize

← serverInfo · capabilities

handshake ok

initialize

Handshake, passed through

Mockd forwards the handshake and returns your server's real capabilities — so your agent sees exactly the server it would in production.

ƒsearch_contacts

ƒcreate_deal

ƒadd_note

+11 more · 14 tools

tools/list

Your tools, discovered

Mockd asks your server for its tools and renders their names, descriptions and schemas. Nothing is hard-coded.

deals.create196ms

{ amount: 4200 }

inject · 429

tools/call

Forwarded, recorded, tunable

Each call is logged, optionally delayed or turned into a 429 / timeout / empty result, then forwarded on. The response and its latency are captured on the way back.

One catch: reachability

How Mockd reaches your server

Mockd

HTTPS

your-server

Remote / HTTP

If your server is reachable over HTTP, Mockd connects straight to the URL. Nothing to install.

Mockd

tunnel

connectorstdio

Local / stdio

If it runs on your machine behind a firewall, a small local connector tunnels out to Mockd — no inbound ports opened.

Point Mockd at your own server

Connect any MCP server and get the same trace viewer over your own tools.

Connect a custom server