Let Claude build your mock APIs and stateful backends

The connection authenticates with a Personal Access Token (PAT). Sign in to APIMock, navigate to Settings → API tokens (or click your avatar in the top-right corner and choose API tokens). Give the token a name like claude-desktop and click Generate Token.

Copy your token immediately—it starts with am_pat_ and is revealed only once. APIMock only ever stores a secure cryptographic hash.

Open Claude Desktop's configuration file (create it if it does not exist):

Add APIMock using the remote HTTP streamable transport. This direct configuration is native, fast, and requires no local bridge dependencies:

{
  "mcpServers": {
    "apimock": {
      "type": "http",
      "url": "https://app.apimock.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer am_pat_your_token_here"
      }
    }
  }
}

Replace am_pat_your_token_here with your token (or paste the snippet copied from APIMock Settings), save the file, and fully restart Claude Desktop (quit the app completely, not just close the window).

{
  "mcpServers": {
    "apimock": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.apimock.dev/api/mcp",
        "--header",
        "Authorization: Bearer am_pat_your_token_here"
      ]
    }
  }
}

After restarting Claude Desktop, start a new chat and click the tools icon (). APIMock exposes a comprehensive suite of 10 specialized agent tools:

Discovery & Workspace
  list_workspaces          See accessible workspaces, slugs, and your roles

Domain Scaffolding & State
  scaffold_backend         Atomically scaffold relational resources, typed schemas, seed data & custom endpoints
  create_resource          Declare a stateful CRUD collection with typed fields (GET, POST, PATCH, DELETE)

Endpoints & Organization
  list_folders             Inspect folder and subfolder hierarchy with paths and IDs
  create_folder            Create nested folders or subfolders
  list_endpoints           List existing endpoints and routes to avoid duplicates
  create_endpoint          Create mock HTTP endpoints with status codes, templates, delays, and auth

Contracts & Specs
  import_openapi           Import OpenAPI/Swagger specs (URL or YAML/JSON) with automatic resource detection

Observability & Self-Healing
  inspect_failed_requests  Query recent 4xx/5xx logs, unmatched routes, and offending payloads
  heal_mock_endpoint       Update response bodies, status codes, or schemas to fix integration failures

Not seeing them? Double-check that the JSON syntax is valid, your token is active in APIMock Settings, and that you restarted Claude Desktop.

With the full tool suite connected, Claude transitions from a simple mock assistant to an autonomous backend orchestrator. Here are the core patterns:

In workspace "acme", scaffold an e-commerce backend with:
- A "products" collection with fields: name (string, required), price (number, required), in_stock (boolean), and category (enum: electronics, apparel, home). Include 5 seed records.
- An "orders" collection with fields: user_id (string, required), total (number, required), status (enum: pending, paid, shipped).
- A custom POST /api/checkout endpoint that accepts cart items and returns an order confirmation.

Import the OpenAPI spec from https://petstore.swagger.io/v2/swagger.json into workspace "acme". Automatically generate mock endpoints and identify any CRUD collections as stateful resources.

My frontend just received a 404 when requesting GET /api/v1/user-profiles. Inspect recent failed requests in workspace "acme", diagnose the missing route or schema mismatch, and heal the mock endpoint so my client succeeds.

List my APIMock workspaces.

Then, in workspace "acme", create a folder "auth" and add:
  - POST /api/auth/login     returning a fake JWT and user profile
  - POST /api/auth/refresh   refreshing the auth token
  - POST /api/auth/logout    returning 204 No Content

Every resource and endpoint created by Claude is live instantly under your workspace subdomain. Because resources are fully stateful, you can test complete CRUD cycles immediately without a real backend:

# 1. List existing products
curl https://acme.apimock.dev/api/products

# 2. Add a new product (persisted statefully)
curl -X POST https://acme.apimock.dev/api/products \
  -H "Content-Type: application/json" \
  -d '{"name": "Mechanical Keyboard", "price": 129.99, "in_stock": true, "category": "electronics"}'

# 3. Retrieve the newly created product by ID
curl https://acme.apimock.dev/api/products/6

• Stateful persistence: POST creates real records that appear in subsequent GET calls and can be patched or deleted.
• Request Inspector: Open APIMock to watch live request traces, latency, headers, and request bodies in real time.
• Autonomous healing: When tests or UI components fail, ask Claude to inspect the failure logs and patch the contract.
• Revoke anytime: Revoke or rotate tokens in Settings → API tokens whenever needed without affecting your workspace data.