Step 5

Parameter Mapping

⏱ 2 min

How parameter mapping works

When an AI agent calls a tool, it sends a JSON object matching the tool’s input schema. MCP Bridge automatically translates that into the correct HTTP request based on your OAS spec:

OAS parameter location	Maps to
in: query	Query string parameter (?key=value)
in: path	URI path segment (/products/{id})
in: header	HTTP request header
in: body	Request body (POST/PUT)

For the Product Catalog API spec, this means:

• list_products: category and limit → query parameters (?category=...&limit=...)
• get_product_details: id → URI path (/products/p1)

No manual mapping configuration is needed when your spec correctly defines the parameter locations.

---

Editing a tool’s mapping

If you need to customise how a tool’s parameters map to the HTTP request, you can do so by editing the tool. While still in the MCP tools and mapping step of the wizard, click the ⋮ Action menu on any tool row.

---

What’s next

With the bridge deployed and tools mapped, the next step is testing the bridge end-to-end.

Continue to Test Your MCP Bridge →