swagger-mcp

Created By
hauntingstepsa year ago
mcp server which will dynamically define tools based on swagger
Overview

What is swagger-mcp?

swagger-mcp is a tool designed to scrape Swagger UI by extracting the swagger.json file and dynamically generating well-defined MCP tools at runtime. These tools can be utilized by the MCP client for further tool selection.

How to use swagger-mcp?

To use swagger-mcp, install it using Go and run it with the required Swagger/OpenAPI JSON URL. Ensure you have the necessary dependencies, including an LLM Model API Key and an MCP Client.

Key features of swagger-mcp?

  • Dynamic generation of MCP tools based on Swagger definitions.
  • Integration with various LLM models for enhanced functionality.
  • Customizable configurations for different use cases.

Use cases of swagger-mcp?

  1. Automating the generation of API client tools.
  2. Enhancing backend services with dynamic tool definitions.
  3. Facilitating easier integration with various APIs through a unified interface.

FAQ from swagger-mcp?

  • What dependencies are required to run swagger-mcp?

You need an LLM Model API Key and an MCP Client to use this tool.

  • How do I configure swagger-mcp?

Configuration is done through command-line flags and a .mcp.json file for integration with MCP clients.

  • Is swagger-mcp open source?

Yes, swagger-mcp is available on GitHub under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hauntingsteps
Star
0
Language
Go
License
MIT 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