explaingit

shivamchavan01/mcp_foundry

Analysis updated 2026-05-18

0PythonAudience · developerComplexity · 4/5Setup · moderate

TLDR

A tool that turns an API specification into a working, tested AI-agent tool server, automatically fixing tools that fail their tests.

Mindmap

mindmap
  root((MCP Foundry))
    What it does
      Spec to MCP server
      Tests each tool
      Auto repairs failures
    Tech stack
      Python FastAPI
      FastMCP
      Prism mock
    Pipeline
      Parse OpenAPI
      Generate server
      Evaluate with agent
      Register in Codex
    Use cases
      Build agent tool servers
      Validate tool clarity
    Audience
      AI agent developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Convert an existing OpenAPI spec into an MCP tool server for an AI coding agent.

USE CASE 2

Automatically test whether an AI agent can reliably tell similar API operations apart.

USE CASE 3

Catch and auto-repair weak or confusing tool descriptions before shipping an MCP server.

USE CASE 4

Register a generated tool server directly into the Codex coding assistant configuration.

What is it built with?

PythonFastAPIFastMCPNode.jsPrism

How does it compare?

shivamchavan01/mcp_foundry0xallam/my-recipe0xhassaan/nn-from-scratch
Stars00
LanguagePythonPythonPython
Last pushed2022-11-22
MaintenanceDormant
Setup difficultymoderatemoderatemoderate
Complexity4/52/54/5
Audiencedevelopergeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Needs Python 3.11+, Node.js, and an API key from a supported LLM provider before it runs.

The README states this is a hackathon build and asks users to add a proper license before publishing or distributing it, so no usage terms are defined yet.

In plain English

MCP Foundry takes an OpenAPI specification, the kind of document that describes what an API can do, and turns it into a working MCP server. MCP stands for Model Context Protocol, a way for AI assistants like coding agents to call tools. Instead of just generating code and stopping there, this project also tests every generated tool against a temporary mock version of the API, scores how well each tool performs, and automatically tries to repair the ones that fail, up to three rounds of fixing. The project describes its approach as generate, evaluate with real agent prompts, repair, and evaluate again. Each generated tool gets a visible score rather than a simple pass or fail hidden behind a checkmark, and the project intentionally reports a needs_review status when it cannot confirm a tool works reliably, rather than pretending everything passed. Under the hood, the pipeline parses the OpenAPI spec, spins up an isolated mock server using a tool called Prism so nothing touches the real API during testing, rewrites vague tool descriptions so an AI can tell similar tools apart, generates the actual server code using the FastMCP framework, runs the agent style evaluation, and if successful, registers the finished server into a coding tool called Codex. To use it, you need Python 3.11 or newer, Node.js and npm, and an API key from one of the supported AI providers, which include Mistral, Groq, Nvidia, and Google. There is a web interface where you click a button to start generating a server, and it also exposes a plain API you can call directly with curl commands. Generated servers, along with their evaluation results, are saved to files on disk. The README notes clear limitations: registration only works on the same machine where the server was generated, job status is stored in memory so restarting the backend loses progress, and results depend on the chosen AI provider staying available. The README states this is a hackathon project and asks users to add a proper license before publishing or distributing it, so its licensing terms are currently undefined.

Copy-paste prompts

Prompt 1
Walk me through installing MCP Foundry and setting up an API key for one of the supported LLM providers.
Prompt 2
Show me how to POST an OpenAPI spec URL to MCP Foundry's /generate endpoint and check the job status.
Prompt 3
Explain what the needs_review status means in MCP Foundry and why a tool might get it.
Prompt 4
Help me use the local Petstore fixture to test MCP Foundry's pipeline without calling a real API.
Prompt 5
What does MCP Foundry's auto-repair step actually change when a generated tool fails evaluation?

Frequently asked questions

What is mcp_foundry?

A tool that turns an API specification into a working, tested AI-agent tool server, automatically fixing tools that fail their tests.

What language is mcp_foundry written in?

Mainly Python. The stack also includes Python, FastAPI, FastMCP.

What license does mcp_foundry use?

The README states this is a hackathon build and asks users to add a proper license before publishing or distributing it, so no usage terms are defined yet.

How hard is mcp_foundry to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is mcp_foundry for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.