Zum Inhalt
HALOWERK

Modellwerk

openapi to mcp

Converts each OpenAPI operation into an MCP tool. Path, query and header parameters and the JSON request body are merged into one input schema, because MCP tools take exactly one; a name collision between a body field and a parameter is reported rather than silently overwritten. Internal $refs are expanded inline so each tool schema stands alone — an MCP client cannot resolve them.

POST https://modell.halowerk.com/v1/openapi-to-mcp

Eingaben

Felder des veröffentlichten Eingabeschemas
FeldTypPflichtBeschreibung
documentobjectJaThe OpenAPI 3.x document as JSON.
namingstringNeinHow to normalise tool names.
include_methodsarrayNeinOnly convert these HTTP methods, e.g. ["get"] for a read-only server.
prefixstringNeinPrefix for every tool name, to keep several APIs apart in one client.
Vollständiges Eingabeschema anzeigen
{
  "type": "object",
  "required": [
    "document"
  ],
  "additionalProperties": false,
  "properties": {
    "document": {
      "type": "object",
      "description": "The OpenAPI 3.x document as JSON."
    },
    "naming": {
      "type": "string",
      "enum": [
        "snake_case",
        "preserve"
      ],
      "default": "snake_case",
      "description": "How to normalise tool names."
    },
    "include_methods": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Only convert these HTTP methods, e.g. [\"get\"] for a read-only server."
    },
    "prefix": {
      "type": "string",
      "maxLength": 40,
      "description": "Prefix for every tool name, to keep several APIs apart in one client."
    }
  }
}

Originalschema öffnen

Veröffentlichtes Eingabebeispiel

{
  "document": {},
  "naming": "snake_case"
}

Ergebnis & Dokumentation

Maschinenlesbare Dokumentation dieses Hubs

Quelle dieser Seite: der veröffentlichte HALOWERK-Katalog. Stand: 2026-11-01, 15:19 UTC.

Weitere Endpunkte dieses Hubs

Alle Endpunkte dieses Hubs →