Kody for Goose

Point Goose at Kody, and the tools it builds stay around for the rest of your team.

Connect Goose

Goose 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 Goose. It points Goose at Kody’s connection docs so it can connect itself.
If Goose asks for an MCP server, give it this URL (Streamable HTTP with OAuth sign-in):
```
https://kody.codes/mcp
```
Sign in to Kody and approve access when asked, then ask Goose to list its Kody tools.

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.

Everyone keeps the agent they like. They all reach the same credentials, packages, and workflows.