Mcp Openapi Runner

io.github.saurav61091Published by GitHub account saurav61091v1.0.1Updated Oct 24, 2026

Turn any OpenAPI 3.x spec into callable MCP tools for Claude. No custom integration code needed.

VerifiedSTDIODesktop onlyDeveloper Tools AI & ML

Server details

Identifier: io.github.saurav61091/mcp-openapi-runner
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account saurav61091 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.saurav61091%2Fmcp-openapi-runner.svg)](https://sourceweft.com/mcp/io.github.saurav61091%2Fmcp-openapi-runner?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that turns an OpenAPI 3.x specification into callable tools, letting an assistant call the described API without custom integration code.

What you can do: Reads an OpenAPI 3.x specification and exposes its operations as MCP tools the assistant can call. Generates tool definitions from the spec so no hand-written integration code is needed. Lets the assistant invoke the API endpoints described in the specification.
When to use it: Useful when you have an OpenAPI 3.x spec for an API and want an assistant to call its endpoints directly, instead of writing a bespoke MCP integration for each API.
Requirements: Runs as a local process on the user's machine via npx from the npm package mcp-openapi-runner, so Node.js is needed. You supply an OpenAPI 3.x specification. Desktop only; no authentication is declared.

Before you install

The assistant can call whatever operations the spec exposes, including ones that write, change or delete data, and requests go to the API described in the spec. Review the spec's operations and any credentials the API needs before connecting it.

Installation

In SourceWeft

Open Mcp Openapi Runner in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.