Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
claude mcp add openapi-mcp-rs -- npx -y openapi-mcp-rs@0.1.1รันในเทอร์มินัล
{ "mcpServers": { "openapi-mcp-rs": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Run an MCP server for an OpenAPI JSON specification, or embed the same tools in another Rust application. The four tools search operations, explain their inputs, call an API, and inspect component schemas.
The CLI and all three libraries are published at version 0.1.0.
MCP server for OpenAPI specifications
cargo install openapi-mcp --version 0.1.0 --locked
openapi-mcp --spec /absolute/path/to/openapi.json
cargo run -p openapi-mcp -- --spec examples/pets.json
The server communicates over stdio; diagnostics go to stderr. The API server URL
comes from the specification. Override it with
--base-url https://api.example.com/v1, which also supports specifications that
omit servers.
The npm distribution is named openapi-mcp-rs and launches the openapi-mcp
executable. Run the published package with:
npx --yes [email protected] --spec /absolute/path/to/openapi.json
Version 0.1.0 includes native binaries for Linux and macOS on x64/arm64, and
Windows on x64. npm selects the package for your platform automatically.
Pass a JSON file with --config /path/to/config.json:
{
"spec": "openapi.json",
"base_url": "https://api.example.com/v1",
"headers": { "X-Workspace": "example" },
"bearer_token_env": "EXAMPLE_API_TOKEN",
"tool_prefix": "example",
"allow_file_reads": false
}
The spec path in a config file is relative to that file. A --spec path is
relative to the working directory. CLI settings override the corresponding
config values. --header NAME=VALUE is repeatable and overrides matching config
headers. --bearer-token or OPENAPI_MCP_BEARER_TOKEN overrides the configured
token environment variable and the Authorization header. Configured HTTP headers
override headers supplied through tool arguments.
Default tool names are api_search, api_explain, api_call, and api_schema.
--tool-prefix example changes them to example_search, and so on. Local file
uploads require --allow-file-reads or allow_file_reads: true in the config.
The HTTP executor uses a 30-second timeout and does not follow redirects.
This first standalone server supports stdio, OpenAPI JSON, and configured HTTP headers/bearer tokens. It does not perform OAuth authorization or token refresh. Embedded hosts can provide their own executor and authentication lifecycle.
Consuming projects can replace temporary sibling paths with registry dependencies:
[dependencies]
openapi-mcp-spec = "0.1.0"
openapi-mcp-core = "0.1.0"
openapi-mcp-io = "0.1.0"
The parser retains source schema metadata. Hosts supply presentation and
validation callbacks through Policy, and can replace RequestExecutor for
their own networking or authentication. Policy::neutral() uses generic
behavior. The core performs no filesystem or network I/O; its MCP SDK types
currently bring runtime dependencies transitively.
This is an operation catalog and request builder, not a complete OpenAPI schema validator. References are resolved shallowly; component lookup merges one parent level. The HTTP executor supports JSON and binary multipart request bodies.
mise install --locked
mise run check
Mise supplies the local and CI tools from mise.toml and mise.lock. Rust is
pinned separately in rust-toolchain.toml. The check task runs formatting,
Clippy, version consistency, Rust and npm tests, docs, dependency checks, and
stdio and installed-package smoke tests.
Run individual checks or build the documentation:
mise run test
mise run package-test
mise run docs
The smoke tests exercise a local API through a real MCP process. The package test builds npm tarballs for the current platform, installs them outside the checkout, and tests the installed launcher. It does not publish packages.
See development for the task reference and
prerequisites, CI for required checks, and
distribution for the packaging and release boundary.
The documentation book is built into docs/book/.
The libraries and launcher were extracted from
onshape-mcp, starting from commit
a05fb34. Onshape-specific authentication, schema annotations, tools, and
resources remain in that project.
Licensed under either MIT or Apache-2.0.
{ "mcpServers": { "openapi-mcp-rs": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Openapi MCP Rs ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-14 MCP server for OpenAPI specifications