Mengonversi spesifikasi OpenAPI menjadi definisi MCP tool dengan resolusi konflik parameter otomatis dan fitur pembuatan HTTP request bawaan.
Juga dikenal sebagai agentfront/mcp-from-openapi
- Stars
- 12
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- —
- Commit terakhir
- 12 Nov 2026
- Lisensi
- Apache-2.0
Apa itu from-openapi MCP?
Mengonversi spesifikasi OpenAPI menjadi definisi MCP tool dengan resolusi konflik parameter otomatis dan fitur pembuatan HTTP request bawaan.
Ringkasan dibuat dari README proyek
Tentang from-openapi MCP server
Developer yang ingin menjembatani celah antara REST API dan AI agent dapat menggunakan library ini untuk mengubah spesifikasi OpenAPI menjadi definisi MCP tool yang siap digunakan. Library ini mengotomatiskan tugas sulit dalam menangani konflik parameter di mana nama yang sama muncul di lokasi berbeda seperti path, query, atau request body. Dengan menyediakan mapper eksplisit dan request builder bawaan, library ini memastikan HTTP request disusun dengan benar tanpa perlu perakitan manual.
Tool ini bekerja di Node.js atau V8 isolates seperti Cloudflare Workers dan mendukung pemuatan spesifikasi dari URL, file, atau objek JSON. Tersedia fitur khusus untuk berbagai AI client, memungkinkan pengguna menargetkan Claude, OpenAI, atau Gemini untuk memastikan schema yang dihasilkan sesuai dengan apa yang diterima oleh masing-masing model tersebut. Library ini juga menyediakan fitur keamanan seperti pencegahan SSRF dan dukungan untuk berbagai skema autentikasi termasuk Bearer, OAuth2, dan AWS Sig V4.
Selain konversi sederhana, library ini menawarkan kemampuan kurasi seperti laporan token budget melalui analyzeToolSet dan linting untuk mengidentifikasi celah pada spesifikasi. Pengguna dapat memfilter tool berdasarkan tag, method, atau path globs untuk membuat set kapabilitas yang lebih spesifik bagi agent mereka.
Apa yang bisa Anda lakukan dengannya
- 1Resolusi konflik penamaan parameter APIMengubah nama parameter yang tumpang tindih dari berbagai bagian HTTP request secara otomatis untuk mencegah tabrakan schema.
- 2Generate schema tool khusus clientMenghasilkan JSON schema yang diformat khusus sesuai dengan kebutuhan Claude, OpenAI, atau Gemini.
- 3Otomatisasi konstruksi HTTP requestMengonversi input tool secara langsung menjadi HTTP request yang valid, termasuk serialisasi query yang kompleks dan multipart bodies.
- 4Monitor konsumsi token AIMengestimasi biaya token dari sebuah toolset untuk mencegah penurunan akurasi pada AI agent.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal from-openapi MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal from-openapi MCP di Claude Code
$ claude mcp add mcp-from-openapi -- npx -y mcp-from-openapiInstal from-openapi MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-from-openapi": {
"command": "npx",
"args": [
"-y",
"mcp-from-openapi"
]
}
}
}Instal from-openapi MCP di VS Code
.vscode/mcp.json
{
"servers": {
"mcp-from-openapi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-from-openapi"
]
}
}
}Instal from-openapi MCP di VS Code CLI
$ code --add-mcp '{"name":"mcp-from-openapi","type":"stdio","command":"npx","args":["-y","mcp-from-openapi"]}'Instal from-openapi MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-from-openapi": {
"command": "npx",
"args": [
"-y",
"mcp-from-openapi"
]
}
}
}Instal from-openapi MCP di Codex
$ codex mcp add mcp-from-openapi -- npx -y mcp-from-openapiInstal from-openapi MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-from-openapi] command = "npx" args = ["-y", "mcp-from-openapi"]
Instal from-openapi MCP di Gemini CLI
$ gemini mcp add -s user mcp-from-openapi npx -- -y mcp-from-openapiInstal from-openapi MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-from-openapi": {
"command": "npx",
"args": [
"-y",
"mcp-from-openapi"
]
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauagentfront/mcp-from-openapi is public and reachablegithub.com/agentfront/mcp-from-openapi ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyamcp-from-openapi names agentfront/mcp-from-openapi as sourcenpmjs.com/package/mcp-from-openapi ↗Lolos
- Provenance build (atestasi Sigstore)Sigstore attestation for mcp-from-openapinpmjs.com/package/mcp-from-openapi/v/2.9.3#provenance ↗Lolos
- Lisensi open source (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-12github.com/agentfront/mcp-from-openapi ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from mcp-from-openapiLolos
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubmcp-from-openapi
Convert OpenAPI specifications into MCP tool definitions with automatic parameter conflict resolution
What This Solves
When converting OpenAPI specs to MCP tools, you hit parameter conflicts -- the same name appears in different locations (path, query, body). This library resolves them automatically and gives you an explicit mapper for building HTTP requests.
The Problem:
paths:
/users/{id}:
post:
parameters:
- name: id # path
in: path
requestBody:
content:
application/json:
schema:
properties:
id: # body -- CONFLICT!
type: string
The Solution:
{
inputSchema: {
properties: {
pathId: { type: "string" }, // Automatically renamed
bodyId: { type: "string" } // Automatically renamed
}
},
mapper: [
{ inputKey: "pathId", type: "path", key: "id" },
{ inputKey: "bodyId", type: "body", key: "id" }
]
}
Now you know exactly how to build the HTTP request.
Features
- Built-in Request Builder --
buildHttpRequest()applies the full OpenAPI serialization table (form/deepObject/pipeDelimited queries, label/matrix paths, multipart, binary,wholeBody) so you never hand-write request assembly - Client Compatibility Targets --
target: 'claude' | 'openai' | 'gemini' | 'strict'emits schemas each client actually accepts (inlined refs, closed objects, collapsed unions, demoted formats) - Context-Budget Reports --
analyzeToolSet()estimates the token bill per tool and warns at the thresholds where agent accuracy degrades - Overlays & Lint -- apply OpenAPI Overlay curation files at load time;
lint()flags the spec gaps that hurt tool-calling accuracy - Curation-Grade Filtering -- Filter by tag, method, path glob (
/admin/**), operationId, areadOnlyOnlysafety switch, andx-mcpextension flags with root < path < operation precedence - Smart Parameter Handling -- Automatic conflict detection and resolution across path, query, header, cookie, and body;
allOfbodies flatten, union and binary bodies map cleanly (wholeBody,binarymarkers) - Complete Schemas -- Input schema combines all parameters; output schema from responses (with oneOf unions); clean JSON Schema 2020-12 output (
nullableunions, normalizedexamples) - MCP-Native Tools --
titleand toolannotations(readOnly/destructive/idempotent hints) inferred from HTTP semantics, overridable via thex-mcpextension family; spec-compliant tool names (64-char cap, stable hash truncation, collision dedup); deterministic tool ordering for prompt-cache friendliness;toSdkTool()for one-line SDK registration - Security Resolution -- Framework-agnostic auth for Bearer, Basic, Digest, API Key, OAuth2, OpenID, mTLS, HMAC, AWS Sig V4; per-scheme
includeSecurityInInput - SSRF Prevention -- Blocks internal IPs, localhost, and cloud metadata endpoints by default during
$refresolution; one-flagsecureDefaultsposture for untrusted specs - Multiple Input Sources -- Load from URL, file, YAML string, or JSON object
- Rich Metadata -- Authentication, servers, tags, deprecation, external docs,
x-frontmcpextension - Production Ready -- Full TypeScript support, validation, structured errors, 100% test coverage (enforced)
- Runtime Agnostic -- Works on Node and V8 isolates (Cloudflare Workers) alike
Installation
npm install mcp-from-openapi
# or
yarn add mcp-from-openapi
# or
pnpm add mcp-from-openapi
Quick Start
import { OpenAPIToolGenerator } from "mcp-from-openapi";
// Load an OpenAPI spec
const generator = await OpenAPIToolGenerator.fromURL(
"https://api.example.com/openapi.json",
);
// Generate MCP tools
const tools = await generator.generateTools();
// Each tool has everything you need
tools.forEach((tool) => {
console.log(tool.name); // "createUser"
console.log(tool.title); // "Create a user" (from summary/extensions)
console.log(tool.annotations); // { readOnlyHint: false, destructiveHint: true, ... }
console.log(tool.inputSchema); // Combined schema for all params
console.log(tool.outputSchema); // Response schema
console.log(tool.mapper); // How to build the HTTP request
console.log(tool.metadata); // Auth, servers, tags, etc.
});
Building Requests
buildHttpRequest() turns a tool plus input values into a ready-to-send request — style/explode serialization, deepObject queries, multipart, binary, and wholeBody handled correctly:
import { buildHttpRequest } from "mcp-from-openapi";
const request = buildHttpRequest(tool, { id: "42", filter: { tag: "news" } });
// { url: 'https://api.example.com/users/42?filter[tag]=news',
// method: 'GET', headers: {...}, body: undefined, ... }
await fetch(request.url, {
method: request.method,
headers: request.headers,
body: request.body as BodyInit,
});
The mapper array stays public for anyone who needs custom request assembly — see Request Builder and Parameter Conflicts for its contract.
Serving with the Official MCP SDK
import { toSdkTool, buildHttpRequest } from "mcp-from-openapi";
import { fromJsonSchema } from "@modelcontextprotocol/server"; // SDK v2
for (const tool of await generator.generateTools({ target: "claude" })) {
server.registerTool(...toSdkTool(tool, { fromJsonSchema }), async (input) => {
const request = buildHttpRequest(tool, input);
const response = await fetch(request.url, {
method: request.method,
headers: request.headers,
body: request.body as BodyInit,
});
return { content: [{ type: "text", text: await response.text() }] };
});
}
Documentation
| Document | Description |
|---|---|
| Getting Started | Loading specs, generating tools, building requests |
| Configuration | LoadOptions, GenerateOptions, RefResolutionOptions |
| Parameter Conflicts | How conflict detection and resolution works |
| Request Builder | buildHttpRequest — full OpenAPI parameter serialization |
| Client Targets | Per-client schema dialects (Claude, OpenAI, Gemini) |
| Curation | Token budgets, overlays, lint, trimming, response hints |
| Type Signatures | TypeScript call contracts for code-execution surfaces |
| Modern MCP Fields | Tool _meta, icons, x-mcp-header, elicitation descriptors |
| Arazzo Workflows | fromArazzo() — Arazzo 1.0 workflows as consolidated MCP tools |
| Tested Examples | Runnable examples, each executed as an e2e test on every CI run |
| Response Schemas | Output schemas, status codes, oneOf unions |
| Annotations & Extensions | Tool title, annotation inference, x-mcp extension family |
| Security | SecurityResolver, all auth types, custom resolvers |
| SSRF Prevention | Ref resolution security, blocked IPs and hosts |
| Format Resolution | Format-to-schema enrichment (uuid, date-time, email, int32, etc.) |
| Naming Strategies | Custom tool naming and conflict resolvers |
| SchemaBuilder | JSON Schema utility methods |
| Error Handling | Error classes, context, and patterns |
| x-frontmcp Extension | Custom OpenAPI extension for MCP annotations |
| API Reference | Complete types, interfaces, and exports |
| Examples | MCP server, Zod, filtering, security, and more |
| Architecture | System overview, data flow, design patterns |
Requirements
- Node.js >= 20.0.0
- TypeScript >= 5.0 (for TypeScript users)
- Peer dependency:
zod@^4.0.0
Contributing
Contributions are welcome! Start with the contributing guide; this project follows the Contributor Covenant. Bug reports and feature requests go through the issue templates.
Security
Report vulnerabilities privately — see the
security policy.
When loading untrusted specs, use secureDefaults: true.
Related Projects
License
Pertanyaan tentang from-openapi MCP
Bagaimana cara menambahkan from-openapi MCP ke Claude Code?
Jalankan claude mcp add mcp-from-openapi -- npx -y mcp-from-openapi di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan from-openapi MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bagaimana library ini menangani konflik parameter dalam spesifikasi OpenAPI?
Library ini secara otomatis mendeteksi dan menyelesaikan konflik ketika nama parameter yang sama muncul di lokasi berbeda seperti path, query, atau body dengan cara mengubah namanya (renaming).
Apakah saya bisa menggunakannya dengan berbagai AI client seperti Claude atau OpenAI?
Ya, library ini mendukung target kompatibilitas client tertentu termasuk Claude, OpenAI, dan Gemini dengan menghasilkan schema yang diterima oleh masing-masing client tersebut.
Apakah ini membantu dalam mengelola penggunaan token untuk tool?
Ya, tersedia laporan context-budget yang mengestimasi biaya token per tool dan memberikan peringatan saat ambang batas tercapai.
Metode autentikasi apa saja yang didukung?
Library ini menyediakan dukungan framework-agnostic untuk Bearer, Basic, Digest, API Key, OAuth2, OpenID, mTLS, HMAC, dan AWS Sig V4.