@ivotoby/openapi-mcp-server

Name: @ivotoby/openapi-mcp-server Review
Item: @ivotoby/openapi-mcp-server
Rating: 3.2
Author: Aaron Matthews

Connector Development Usable

Works inClaude Code Claude Cowork Claude Chat

Usable Scanned — metadata only

Turns any OpenAPI spec into a set of MCP resources Claude can call. Bridges existing REST APIs into the MCP ecosystem without writing custom server code.

MCP server that exposes any REST API described by an OpenAPI/Swagger spec as tools an AI assistant can call. Point it at a spec URL or file via environment variables (API_BASE_URL, OPENAPI_SPEC_PATH, API_HEADERS) and it maps the endpoints automatically — no custom server code. Runs via npx with stdio transport for Claude Desktop or HTTP transport for other clients.

Connect Claude to your company's internal tools using their documentation
Browse and call your team's web services from a conversation
Test your internal service endpoints without writing code

286 starsMIT (commercial OK)FreeNo code needed

Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

Why it matters

Turns any OpenAPI spec into a set of MCP resources Claude can call. Bridges existing REST APIs into the MCP ecosystem without writing custom server code.

Best for

API-heavy teams who want Claude to interact with their internal services described by OpenAPI/Swagger specs.

Works in

Claude Code Claude Cowork Claude Chat

Source

https://github.com/ivo-toby/mcp-openapi-server

By GitHub Actions

How to Get It

Option 1: Claude Desktop AppOpen the Customize panel in the sidebar → browse connectors → search and add. Works in Claude Code, Claude Cowork, and Claude Chat.

Option 2: Paste into Claude CodeCopy the command below and paste it into a Claude Code conversation. Claude will run it for you.

Command

npx -y @ivotoby/openapi-mcp-server  # set env vars: API_BASE_URL, OPENAPI_SPEC_PATH, API_HEADERS — see README for the claude_desktop_config.json snippet

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

First thing to try

Once it’s connected, paste this into Claude:

Help me connect Claude to my company's internal tools using their documentation

PrerequisitesNode.js (runs via npx); an OpenAPI specification (URL or local file) for the target API, plus any auth headers the API requires

Trust Signals Auto-scanned

Stars286Contributors11Last updated2026-06-15LicenseMIT (OK for commercial use)Weekly downloads9,321Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-08-13 · scanner v1

Data & Access

Data processingPrompts sent to Anthropic API. Enterprise/Team plans exclude training.

Community Pulse Quiet

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 277 GitHub stars; 9 contributors; last commit 21d ago; license MIT.

Things to check

Requires OpenAPI specs to be accurate and complete; malformed or outdated specs will cause failures. Authentication handling depends on OpenAPI spec quality and may require manual configuration for edge cases.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation Scores

Evaluation

Ease of Use

3/5

Versatility

3/5

Reliability

4/5

Security

3/5

Overall score3.25 / 5.00 UsableEvaluatedJul 2026

catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 277 GitHub stars; 9 contributors; last commit 21d ago; license MIT.

← Back to the Claude Observatory