Mcp Swagger Server

Created By
zaizaizhaoa year ago
Overview

What is MCP Swagger Server?

MCP Swagger Server is a tool that converts REST APIs defined by OpenAPI/Swagger specifications into Model Context Protocol (MCP) format, enabling AI assistants to understand and call your APIs.

How to use MCP Swagger Server?

To use MCP Swagger Server, clone the repository, install dependencies, and run the server with your OpenAPI specification. You can start the server using command line options to specify the transport protocol and authentication methods.

Key features of MCP Swagger Server?

  • Zero-configuration conversion: Instantly convert OpenAPI specs into MCP tools.
  • AI-native design: Optimized for AI assistants like Claude and ChatGPT.
  • Multiple transport protocols: Supports SSE, Streamable, and Stdio transport.
  • Secure authentication: Supports Bearer Token authentication for API access.
  • High performance: Built with TypeScript for complete type safety.

Use cases of MCP Swagger Server?

  1. Converting existing REST APIs for AI integration.
  2. Enabling AI assistants to interact with various APIs seamlessly.
  3. Facilitating the development of AI-driven applications that require API calls.

FAQ from MCP Swagger Server?

  • Can MCP Swagger Server convert any OpenAPI specification?

Yes! It is designed to work with any REST API that follows the OpenAPI/Swagger specification.

  • Is MCP Swagger Server free to use?

Yes! MCP Swagger Server is open-source and free for everyone.

  • How do I authenticate my API calls?

You can use Bearer Token authentication by specifying the token directly or through environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zaizaizhao
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago