HN Showcase
Back to browse
GitHub Repository
0 starsPython

Mcpify – Turn any REST API into an MCP server in one command

by harpreetsingh80·Jun 27, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●●BangerSolve My ProblemBig Brain

Zero per-endpoint wrappers—OpenAPI spec becomes live MCP tools instantly.

Strengths
  • •Eliminates tedious manual tool wrapper code for every single API endpoint.
  • •Stays automatically in sync when the OpenAPI spec changes upstream.
  • •Single auth header applies globally across all generated tools.
Weaknesses
  • •Only supports OpenAPI 3.x; Swagger 2.0 and advanced filtering still on roadmap.
  • •Stdio transport only; SSE and HTTP server modes not yet implemented.
Category
AI/ML
Target Audience

AI developers integrating APIs into Claude, Cursor, or Windsurf

Similar To

manual MCP tool wrappers · OpenAPI-to-Function converters

Post Description

Wiring an existing API into MCP means hand-writing a tool wrapper per endpoint. Almost every API has an OpenAPI spec, so mcpify just reads it and generates the whole server. Built it because I kept doing this by hand. Feedback welcome.

Similar Projects

Developer Tools●●Solid

Turn any OpenAPI spec into agent-callable skills

It extracts focused, executable operations from giant OpenAPI files (the GitHub REST YAML is shown) to shrink context and avoid sidecar adapter sprawl — a pragmatic answer to token bloat and brittle ad-hoc integrations. Useful and concrete: if it actually generates tidy, updateable skill units and runtime hooks it saves a lot of maintenance. That said, the idea competes with existing LangChain/openai-function patterns; the repo will need clear runtime, versioning, and update strategies to feel like more than a nicer converter.

Solve My ProblemNiche Gem
yz-yu
104mo ago