LABSCO SUMMARY
Any documented API becomes a tool your agent can call.
Instead of one MCP server per service, you hand it a specification URL and the endpoints described there become callable — which is the difference between waiting for someone to write a connector and using the API this afternoon.
What it is
A LangChain-based server that loads OpenAPI specifications at runtime and turns them into callable tools, reachable either from an MCP client over SSE or from a Langflow canvas through its bundled components. It also runs as a plain CLI, which is the quickest way to see whether a given spec parses before wiring anything up.
What you get
- Dynamic loading of an OpenAPI specification from a URL, so an API becomes usable without a purpose-built server for it
- An MCP server mode over SSE —
uv run hippycampus-server --transport sse --port 8000, reachable athttp://localhost:8000/sse - A CLI mode,
uv run hippycampus-cli, for debugging spec parsing and agent interaction before involving a client - Two Langflow components: OpenApi Service for loading a spec, and Hippycampus MCP Server for connecting over SSE
Requirements
Python 3.12.9 and the UV package manager; create a virtual environment, then uv pip install -e ., and uv pip install langflow if you want the visual side. A Google AI Studio API key in GOOGLE_API_KEY — authentication errors almost always mean it is unset. For Langflow, export LANGFLOW_COMPONENTS_PATH pointing at the repository's langflow/components directory, start the MCP server before Langflow, and restart Langflow if the components do not appear. Specs in the wild are not always correct: the official XKCD swagger declares its comic_id as a number rather than an integer, and the repository ships a corrected copy in its test folder.
Setup effort
Build from source — git clone https://github.com/cromwellian/hippycampus
USE CASES
01
Using an API nobody has built a server for
Load its OpenAPI specification and call the endpoints from your assistant without writing a wrapper.
02
Checking whether a spec is usable at all
Run the CLI against it first and watch the parsing and agent interaction, before involving an MCP client or Langflow.
03
Building the flow visually
Drop the OpenApi Service and MCP Server components into Langflow and wire the API into a graph rather than a script.
04
Debugging a spec that will not load
The XKCD example in the test folder shows the shape of the problem — a type declared wrongly in the published spec — and gives you a corrected file to compare against.
BEFORE YOU INSTALL
What to know first
Requires
- Python 3.12.9
- GOOGLE_API_KEY in your environment
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/cromwellian/hippycampus
cd hippycampusInstallation
TERMINAL
curl -LsSf https://astral.sh/uv/install.sh | sh
uv venv
source .venv/bin/activate
uv pip install -e .Google AI Studio API Key
TERMINAL
export GOOGLE_API_KEY='<YOUR_GOOGLE_API_KEY>'MCP Server Mode (SSE)
TERMINAL
uv run hippycampus-server --transport sse --port 8000MCP Server: Use http://localhost:8000/sse