mcpField
M
Mockmcp

Mockmcp

Remote
github.com/K-CupplesDeveloper Tools0Updated 27w ago
Repository

About Mockmcp

MockMCP is a hosted MCP server for developers prototyping agent workflows without building a backend or fixtures. Its 12 tools return deterministic, realistic fake data across common tutorial scenarios.

Key features

  1. 0112 tools for common data scenarios
  2. 02Seeded, repeatable fake data
  3. 03User, product, and order operations
  4. 04Mock events, email, and knowledge-base search
  5. 05Hosted Streamable HTTP endpoint

Use cases

  1. 01Prototype an agent workflow without a backend
  2. 02Test user, product, or order interactions
  3. 03Try event logging, email, or knowledge-base search

MCP support

MockMCP exposes 12 fake-data tools through a hosted Streamable HTTP MCP endpoint. It can be connected directly by MCP clients such as Claude Code, Cursor, and Claude Desktop.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mockmcp.io/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

MockMCP

Hosted MCP endpoint returning realistic fake data for prototyping agents. Paste one URL, zero setup.

Live at mockmcp.io — https://mockmcp.io/mcp

Built for devs who want to prototype agent workflows without wiring up a backend, writing fixtures, or standing up a local MCP server. 12 pre-built tools covering the scenarios in most agent tutorials.

Try it

# Initialize a session and get back a session id
curl -i -X POST https://mockmcp.io/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0.1"}}}'

# Use the Mcp-Session-Id header in subsequent calls:
curl -X POST https://mockmcp.io/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Mcp-Session-Id: <paste-id-here>" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_users","arguments":{"limit":3}}}'

Connect your client

Claude Code

claude mcp add --transport http mockmcp https://mockmcp.io/mcp

Cursor — add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "mockmcp": {
      "url": "https://mockmcp.io/mcp"
    }
  }
}

Claude Desktop — Settings → Connectors → Add custom connector → paste https://mockmcp.io/mcp as the URL.

No mcp-remote proxy required. All three clients speak Streamable HTTP natively.

Tools

ToolWhat it does
list_usersPaginated list of mock users
get_userOne mock user by id or seed
create_userCreate a mock user (no persistence)
list_productsPaginated list of mock products
get_productOne mock product
list_ordersMock orders with optional status filter
get_orderOne mock order
create_orderCreate a mock order (no persistence)
list_eventsMock analytics events
create_eventRecord a mock event
send_emailReturns fake success, nothing delivered
search_knowledge_baseMock KB search with ranked results

All data is seeded from your inputs — same input, same output.

Limits

Free tier, per hashed IP + User-Agent fingerprint:

  • 30 requests per minute
  • 500 requests per day

Hit the wall? Drop your email at mockmcp.io/waitlist for paid-tier access when it launches.

429 responses carry a structured JSON-RPC error with upgrade_url and retry_after_seconds. Every successful response carries X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and X-RateLimit-Scope headers.

Run locally

npm install
npm run dev

Server listens on http://localhost:3000. MCP endpoint at /mcp. Without Upstash env vars, rate limiting falls back to an in-memory store (per-process, fine for dev).

Stack

Deploy (for forks)

Targets Node 20+. Build + start are pinned via nixpacks.toml; health checks + restart policy via railway.json.

  1. Fork this repo, push to GitHub.
  2. Railway → New Project → Deploy from GitHub → pick your fork.
  3. Add env vars in Railway → Variables:
VarNotes
UPSTASH_REDIS_REST_URLFrom upstash.com free tier
UPSTASH_REDIS_REST_TOKENPaired with the URL above
PORTRailway sets this automatically
  1. Railway service → Settings → Networking → Custom Domain → paste your domain → follow the DNS instructions.
Health check

GET /health returns {"ok":true}. Railway pings this during deploy.

Waitlist signups

POST /api/waitlist logs a structured JSON line per signup:

{"event":"waitlist_signup","email":"[email protected]","at":"2026-04-24T19:33:06.396Z"}

Grep them with railway logs | grep waitlist_signup. Storage-free by design — swap in Resend, a Tally forward, or a DB when the paid tier is live.

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.