Kody for Instinct

Bring your team’s tools and connected accounts to Instinct, the personal assistant you text or call.

Connect Instinct

Instinct has no official MCP support, but it can use a computer the way you do, so it connects through the Kody CLI. If Instinct adds remote MCP support, it can connect to https://kody.codes/mcp instead.

Ask Instinct to install the Kody CLI on its computer (Node 22 or later):
```
npm install -g @kodycodes/cli
```
Have it sign in. The command prints a link and a short code. Ask Instinct to send them to you, open the link, check that the code matches, and approve.
```
kody login --device
```
Instinct can then use Kody from the CLI: kody search finds what your account can do, and kody execute --local runs it with your connected accounts, without Instinct seeing a key.
```
kody search "what can you do"
```

More ways to connect

What Instinct 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.