OpenAPI / Swagger to JMeter JMX Converter

Presets:Petstore (OAS 3.0 JSON)Minimal (OAS 3.1 YAML)Swagger 2.0 JSON

OpenAPI or Swagger document{ "openapi": "3.0.3", "info": { "title": "Petstore API", "version": "1.0.0" }, "servers": [ { "url": "https://petstore.example.com/{basePath}", "variables": { "basePath": { "default": "v3" } } } ], "tags": [ { "name": "pet" }, { "name": "store" } ], "security": [ { "bearerAuth": [] } ], "paths": { "/pet/{petId}": { "get": { "tags": [ "pet" ], "operationId": "getPetById", "summary": "Find pet by ID", "parameters": [ { "name": "petId", "in": "path", "required": true, "example": 10, "schema": { "type": "integer", "format": "int64" } } ], "responses": { "200": { "description": "Pet response" } } }, "delete": { "tags": [ "pet" ], "operationId": "deletePet", "deprecated": true, "parameters": [ { "name": "petId", "in": "path", "required": true, "schema": { "type": "integer" } } ], "responses": { "204": { "description": "Deleted" } } } }, "/pet": { "post": { "tags": [ "pet" ], "operationId": "addPet", "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/Pet" } } } }, "responses": { "201": { "description": "Created" } } } }, "/pet/findByStatus": { "get": { "tags": [ "pet" ], "operationId": "findPetsByStatus", "parameters": [ { "name": "status", "in": "query", "required": false, "schema": { "type": "string", "enum": [ "available", "pending", "sold" ] } } ], "responses": { "200": { "description": "Pets" } } } }, "/store/inventory": { "get": { "tags": [ "store" ], "operationId": "getInventory", "security": [], "responses": { "200": { "description": "Inventory" } } } }, "/store/order": { "post": { "tags": [ "store" ], "operationId": "placeOrder", "requestBody": { "content": { "application/x-www-form-urlencoded": { "schema": { "type": "object", "properties": { "petId": { "type": "integer", "example": 10 }, "quantity": { "type": "integer", "default": 1 } } } } } }, "responses": { "201": { "description": "Order placed" } } } } }, "components": { "securitySchemes": { "bearerAuth": { "type": "http", "scheme": "bearer", "bearerFormat": "JWT" } }, "schemas": { "BasePet": { "type": "object", "required": [ "name", "status" ], "properties": { "name": { "type": "string", "example": "Fido" }, "status": { "type": "string", "enum": [ "available", "pending", "sold" ] } } }, "Tag": { "type": "object", "properties": { "id": { "type": "integer" }, "name": { "type": "string", "example": "friendly" } } }, "Pet": { "allOf": [ { "$ref": "#/components/schemas/BasePet" }, { "type": "object", "properties": { "tags": { "type": "array", "items": { "$ref": "#/components/schemas/Tag" } } } } ] } } } }OpenAPI 3.0/3.1 and Swagger 2.0, JSON or YAML. Runs entirely in your browser.

Upload JSON or YAML

Virtual Users (Threads)

users

Ramp-Up Time

sec

Duration

sec

Loop Count

loops

Test Plan Name

Extract host to ${BASE_URL}Include optional query paramsUse example path values instead of ${var}Add response assertionsInclude Cookie ManagerInclude deprecated operations

HTTP methods

GETPOSTPUTPATCHDELETEHEADOPTIONSTRACE

HTTP Samplers-

Spec Version-

Base URL-

Variables to Set-

Notices

Operations

User Defined Variables

Generated Apache JMeter JMX XML

JMeter 5.6.3

Download .jmxCopy JMX XMLReset

Use this converter through MCP

Connect an AI agent and call convert_openapi_to_jmx to convert OpenAPI or Swagger JSON/YAML into the same JMeter test plan format.

claude mcp add jmeter-docs https://docs.jmeter.ai/api/mcp --transport http

Conversion runs locally in your browser. Review generated sample values, credentials, assertions, and request order before running load. See the cURL & HAR converter, JMX Linter, and HTTP Request reference.

What gets generated

The converter turns each included API operation into a JMeter HTTP Request sampler and builds the surrounding Test Plan, HTTP Request Defaults, Thread Group, optional Cookie Manager, and response assertions.

• Servers become HTTP Defaults: the selected OpenAPI server supplies the protocol, host, port, and path prefix. With host extraction enabled, the host is stored as ${BASE_URL}.
• Path parameters become variables: /users/{userId} becomes /users/${userId}. A generated User Defined Variable contains the schema example or a CHANGE_ME placeholder.
• Schemas become sample bodies: JSON and form bodies are populated from examples, defaults, enums, formats, and referenced schemas.
• Security becomes variables: bearer authentication becomes ${AUTH_TOKEN} and API-key authentication becomes ${API_KEY}. Basic authentication uses ${BASIC_AUTH}.
• Assertions catch unexpected responses: the optional response assertion accepts HTTP 200, 201, and 204 as a starting point. Adjust it to match each API contract.

Supported specification features

Feature	Support
OpenAPI versions	OpenAPI 3.0, OpenAPI 3.1, and Swagger 2.0
Input formats	JSON and YAML
Local references	#/components/..., #/definitions/..., #/parameters/..., and #/responses/...
Request bodies	JSON, application/*+json, URL-encoded forms, text examples, and XML examples
Parameters	Path, query, and header parameters; optional query parameters are opt-in
Security	Bearer, OAuth2/OpenID Connect, HTTP Basic, and header/query API keys
Schema composition	allOf merging; the first oneOf or anyOf branch is used
Known limitations	Multipart bodies, cookie parameters, and external $ref documents are not converted

Operation order follows the source document’s path order and a stable HTTP method order. The generated plan does not infer a business workflow or dependencies between endpoints, so reorder samplers and add correlation where needed.

Filling in variables before running

Open the generated Test Plan’s User Defined Variables element and replace CHANGE_ME placeholder values and sample IDs. You can also replace values at runtime with JMeter properties after changing the corresponding variable value to a property function such as ${__P(apiKey,CHANGE_ME)}.

For secrets, avoid committing real values to the .jmx. Supply them through your CI secret store and -J properties instead.

Running in CLI mode

Run generated plans in non-GUI mode:

jmeter -n -t openapi-test-plan.jmx -l results.jtl -e -o ./report

The generated Thread Group already reads concurrency, ramp-up, and duration from JMeter properties, so you can override them without editing the plan:

jmeter -n -t openapi-test-plan.jmx \
  -Jthreads=100 -JrampUp=30 -Jduration=300 \
  -l results.jtl -e -o ./report

A duration greater than zero enables the scheduler and infinite looping for the configured duration.

Use via MCP

Connect an MCP-compatible agent:

claude mcp add jmeter-docs https://docs.jmeter.ai/api/mcp --transport http

Ask the agent to call convert_openapi_to_jmx with an OpenAPI 3.x or Swagger 2.0 document in JSON or YAML. It can apply the same server, method, tag, deprecated-operation, path-value, assertion, and Cookie Manager options as the browser converter and returns the generated JMX XML in its response.

Related tools

• Use the cURL & HAR to JMX Converter when you have captured requests rather than an API contract.
• Run the generated plan through the JMX Linter & Health Analyzer before execution.
• Review JMeter Best Practices before increasing load.