Mock MCP Studio

Mock MCP Studio lets you create fully configurable mock MCP servers — ideal for developing MCP clients before the real server exists, or for testing error scenarios and edge cases.

Creating a Mock MCP Server

  1. Go to Explorer in the navigation
  2. Click Add New → MCP Server
  3. Choose Create Mock MCP Server
  4. Name your server and optionally add a description
  5. Define tools, resources, and prompts (see below)
  6. Save — the mock is immediately live as an MCP endpoint

Defining Capabilities

Tools

Each tool has a name, description, and a JSON Schema input schema:

{
  "name": "get_weather",
  "description": "Get current weather for a location",
  "inputSchema": {
    "type": "object",
    "properties": {
      "location": { "type": "string", "description": "City name or coordinates" }
    },
    "required": ["location"]
  }
}

Resources

Resources expose data by URI:

{
  "uri": "file:///data/{path}",
  "name": "Data Files",
  "description": "Access project data files",
  "mimeType": "text/plain"
}

Prompts

Prompts are pre-defined templates with optional arguments:

{
  "name": "code_review",
  "description": "Review code for issues",
  "arguments": [
    { "name": "language", "required": true },
    { "name": "code", "required": true }
  ]
}

Flows Tab

Each capability gets its own response flow. Open the Flows tab to see all capabilities listed. Click Edit ↗ on any capability to open the Flow Builder for that capability.

Template Variables in MCP Flows

Use {{variableName}} syntax to reference context in node fields:

VariableDescription
{{toolName}}Name of the invoked tool
{{toolArgs.X}}Individual tool argument by key
{{resourceUri}}URI of the resource being read
{{promptName}}Name of the prompt
{{promptArgs.X}}Individual prompt argument by key
{{mcpServerId}}This mock server's ID

MCP End Node

The End node for MCP flows includes an output type selector that controls the wire format of the response:

Output typeWire format
Toolcontent: [{ type: "text", text: "..." }]
Resourcecontents: [{ uri, mimeType, text }]
Promptmessages: [{ role, content: { type, text } }]

Set isError: true on the End node to return a tool error response instead of a result.

Mock MCP Endpoint

After creation, the server is available at:

{base-url}/api/mock-mcp-servers/{id}/mcp

This endpoint handles all MCP JSON-RPC methods: initialize, tools/list, tools/call, resources/list, resources/read, prompts/list, prompts/get.

The capability manifest is served at:

{base-url}/api/mock-mcp-servers/{id}/.well-known/mcp-server.json

API Key Protection

Enable Require API Key in the Settings tab to restrict access to your mock server. Generate API keys in the same tab. Include the key as a Bearer token in requests:

Authorization: Bearer your_api_key_here

API Routes

MethodPathDescription
GET/POST/api/mock-mcp-serversList / create mock servers
GET/PUT/DELETE/api/mock-mcp-servers/:idServer operations
POST/api/mock-mcp-servers/:id/mcpMCP JSON-RPC endpoint
GET/api/mock-mcp-servers/:id/.well-known/mcp-server.jsonCapability manifest
GET/POST/api/mock-mcp-servers/api-keysList / create API keys
DELETE/api/mock-mcp-servers/api-keys/:idRevoke API key