Connect Claude Code, Cursor, Windsurf & Claude Desktop to your enterprise data — databases, files, APIs, SSH & more. Define connectors in YAML. No code. No install.
v1.4.1 · Release notes
Define your connectors in oe-mcp.yaml — database credentials, file paths, API tokens. One file, any number of connectors.
Point Claude Code, Cursor, or Windsurf at the binary. Every connector is exposed as tools your AI can call directly from the IDE.
Query your database, read files, post to Slack, search GitHub — all from inside your IDE, with no custom integration code.
Choose stdio for Claude Code — launched automatically as a child process — or HTTP for Cursor, Windsurf, and cloud deployments.
Claude Code launches the binary automatically as a child process. Add to ~/.mcp.json or your workspace .mcp.json:
Reload VS Code — MCP tools appear automatically in Claude Code.
Start the server once, then point your app at the URL. Deploy to a cloud server to share one endpoint across your team:
Deploy oe-mcp-linux to EC2, fly.io, or Railway — the whole team connects via one URL, no binary on each machine.
One YAML file defines all your connectors and seeds default memory values. Credentials stay on your machine — nothing is sent anywhere.
Download oe-mcp-samples.zip for ready-to-use configs: postgres · mysql · mongodb · github · slack · gdrive · ssh · filesystem · oracle · multi-connector
Every OE MCP session includes four memory tools. Context persists in oe-mcp-memory.json next to your config — survives restarts and new sessions.
Every connector below is available as MCP tools in your AI app. Declare it in oe-mcp.yaml — the binary handles authentication, protocol, and tool exposure.
Download the binary, write a YAML config, and your AI assistant can query databases, browse files, and call APIs — in minutes.