Kody for Wajo
Reach your team’s packages and connected accounts from Wajo, wherever you chat.
Connect Wajo
Wajo doesn’t have an official Kody setup yet. It needs to support remote MCP servers; if it does, it can usually connect itself.
Copy this setup prompt and paste it into Wajo. It points Wajo at Kody’s connection docs so it can connect itself.
If Wajo asks for an MCP server, give it this URL (Streamable HTTP with OAuth sign-in):
https://kody.codes/mcpSign in to Kody and approve access when asked, then ask Wajo to list its Kody tools.
What Wajo gets from Kody
- memory
Facts without a better home, like project nicknames or team context, that your connected agents can retrieve.
- packages
Reusable code with typed inputs and documented defaults. Keep how a task gets done in the package, ready for any connected agent to run.
- triggers
Subscriptions, emails, webhooks, and schedules that wake packages you own, with no chat left open.
- credentials
API keys, OAuth connections, and MCP servers your agents use but never see.
- apps
A hosted page a package serves, so the work is something you open instead of another turn in chat.
The rest of your team can join from
Everyone keeps the agent they like. They all reach the same credentials, packages, and workflows.