An MCP gateway for your personal agents
Connect Claude, Cursor, and Codex to the same tools. Keep the workflows you build and their saved progress in your Kody account.
search · executeYour account’s tools, code, and memoryUse the same tool from another agent.
Example only, no live tool callssearchFind a saved tool that lists GitHub releases.
Found: release-watch Input: repository Output: published releases
The agent finds the tool, checks what it needs, and sees what it returns.
Bring your tools and workflows together.
Connect your MCP tools
Connect your MCP servers to Kody so your agents can discover their tools through one account.
Keep access in one place
Your service connections stay in Kody. Switch agents without rebuilding the connections for each workflow.
Kody
Use Kody when you want to keep the workflow you built with those tools. Your agent can combine them in code and save that code and its progress in a package.
Keep the workflow you built.
Once your agent has built a workflow around a connected service, save it as a package so you can use the code again in the next conversation.
If you’re choosing a gateway for a company, check its team controls, audit exports, deployment options, and access rules. Sharing tools between your own agents doesn’t cover all of those needs.
- Integration
- A saved connection that lets Kody use one of your service accounts.
- Package
- Your code, exports, storage, and optional scheduled jobs.
- Remote MCP server
- An existing server Kody connects to. This doesn’t mean hosting an arbitrary server process inside a package.
Build a release lookup you can take to another agent.
Help me connect this agent to Kody. Build a read-only GitHub release lookup, save it as a package, and tell me how to find and run the same package from another agent connected to my account.