Back to AI Lab

AI LAB · AGENT INFRASTRUCTURE & PRODUCT STRATEGY

OmniMCP: What If Any API Could Be an AI Agent Tool?

Putting on a founder hat to bridge the gap between everyday REST APIs and local AI assistants—while solving the UX and context-bloat bottlenecks that break agentic workflows at scale.

ROLE: PRODUCT DESIGNER & SOLO ARCHITECT FOCUS: AGENT TOOLING, DX & COMMERCIAL STRATEGY
OmniMCP Dashboard: Central command for local MCP servers, OpenAPI bridges, and AI agent connections
OmniMCP Dashboard: Central command for local MCP servers, OpenAPI bridges, and AI agent connections

How It Started

It began with a personal frustration: I wanted Windows Copilot and my local AI tools to talk to everyday services even when native MCP support didn't exist. That sparked a bigger product question: You shouldn't have to wait for every data provider to build an MCP server—what if you could turn any public API into an AI tool in seconds?

The Product Vision

With OmniMCP, you can point the hub at any standard API—whether that’s analysing your personal Spotify listening history with an API key or checking live local pollution data—and instantly expose it to your AI assistant, while keeping credentials secure and context windows lean.


Product, UX & Commercial Decisions

  • Instant API-to-MCP Synthesis: Instead of writing custom Python or Node wrapper code for every service, OmniMCP uses LLM-grounded discovery to read standard OpenAPI/REST docs and generate a working local tool connection on the fly.
  • Solving "Context Bloat" in Practice: Once you can turn any API into a tool, you hit a massive practical wall: loading 50+ tool schemas into an LLM destroys its reasoning and burns tokens. I designed a progressive-disclosure routing layer so the AI only loads a tool's schema at the exact moment it needs to call it.
  • Wearing the Founder Hat (Market Timing vs. Platform Risk): There is a genuine commercial product with legs here—turning raw APIs into managed agent capabilities for non-coders. At the same time, like many infrastructure plays in AI, it operates in a tight strategic window before the major OS and model providers inevitably absorb this layer natively.
Connectors & Tool Catalogue: Managing active MCP servers, OpenAPI REST bridges, and credential security
Connectors & Tool Catalogue: Managing active MCP servers, OpenAPI REST bridges, and credential security
The Takeaway

“Building OmniMCP was an exercise in end-to-end product leadership—starting from a personal technical itch, discovering the second-order scaling problem (context bloat), and evaluating the commercial moat with clear eyes.”

OmniMCP Runtime

The standalone desktop runtime and documentation website are coming soon.

Coming Soon