Step 5 of 5

# Mapping and execution

Define how MCP tool arguments map to upstream request fields, and how the upstream response maps back to MCP output. Then set execution parameters — auth is configured per-upstream in step 3.

Input → Request
yaml / input-mapping
first_name: "$.input.first_name" last_name: "$.input.last_name" email: "$.input.email" company: "$.input.company" phone: "$.input.phone" source: "$.input.source"
Response → Output
yaml / output-mapping
lead_id: "$.response.data.id" status: "$.response.data.status" created_at: "$.response.data.created_at" owner_id: "$.response.data.owner.id"
Execution
Execution config
Timeouts, retry policy and auth profile reference
Optional
yaml / exec-config
timeout_ms: 10000 retry: max_attempts: 3 backoff_ms: 500 auth: profile: acme_bearer tls: verify: true
Operation will be saved as a draft
Clicking "Create operation" saves the contract in draft status. You can run tests, inspect metadata and publish from the operation workspace. Drafts are never exposed to MCP clients.