What is this?
Machine Internet UAA (Universal API Adapter) wraps any web API into an MCP server — a standardized interface that AI agents can call directly. You paste a URL, it discovers the API's tools, generates a schema, and exposes it on a local port that Claude (or any MCP client) can talk to.
Discovery Paths
Path A
OpenAPI Spec
Fetches an OpenAPI / Swagger spec from the target and converts every endpoint into an MCP tool. Works on any modern REST API that publishes a spec.
Path B
Traffic Sniffing
When no spec exists, a headless browser loads the site and records XHR/fetch calls. Only works on SPAs (single-page apps) — server-rendered pages yield no captures.
Step-by-step
1
Paste a URL — any API homepage, docs page, or direct spec URL. Use the Options panel to provide a spec URL or filter tags if you already know them.
2
Click "Wrap API" — the discovery pipeline runs (Path A first, Path B as fallback). Output streams in the Log tab in real time.
3
Start the service — click ▶ Start on any card. This launches a local MCP server on a free port (starting at 8100).
4
Copy the MCP URL — shown in the footer and on each live card. Paste it into your Claude MCP config or any compatible AI client.
5
Use in Claude — add the URL under Settings → MCP Servers. Claude will see all discovered tools and call them on your behalf.
MCP Config snippet
Add this block to your Claude config file (claude_desktop_config.json):
{
"mcpServers": {
"my-api": {
"url": "http://localhost:8100/mcp"
}
}
}
Auth & Secrets
Tap any service card → Auth tab to see its auth type and the exact serve.py command with the right port. Set secrets as environment variables before starting — the server reads them at runtime, never baking them into the schema file.
Good targets for Path B
Services with no public spec, legacy internal tools, or anything built before the OpenAPI standard. The traffic sniffer works best on React/Vue/Angular SPAs that fire API calls on page load — e.g. HN Algolia search, undocumented dashboards, internal portals.
