Get started with Kody
Connect any MCP-capable AI agent to your Kody account, then ask it to help you set things up.
1. Not sure what you’d use Kody for?
Paste this into any AI agent that can fetch a URL or search the web — ChatGPT, Claude, or whatever you already use. It has the agent read Kody's docs, interview you, and suggest concrete automations. No account or setup needed yet.
I'm deciding whether Kody (https://kody.wraplogic.xyz) would be useful for me. Read https://github.com/kentcdodds/kody/blob/main/docs/use/what-can-kody-do.md and follow its links for anything you need more detail on. Then interview me about the tools I use, recurring chores I do by hand, and automations I've wished for. Finish with 3-5 specific things Kody could do for me, ranked by payoff versus setup effort, each with a concrete first step. Don't set anything up yet — this works before I have an account.
2. Add Kody as an MCP server
Pick your MCP client below for host-specific setup. When the agent connects, it starts an OAuth flow — sign in to Kody if needed, approve the request, and the agent receives a token scoped to your account.
Choose your client
In Cursor, open Customize and add a remote MCP server with this URL, or merge the JSON below into ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
https://kody.wraplogic.xyz/mcp
JSON config (merge under your existing mcpServers if you already have one):
{
"mcpServers": {
"kody": {
"url": "https://kody.wraplogic.xyz/mcp"
}
}
}
Coding agents are the best fit when you want to create or edit Kody packages. Once a package exists, non-coding agents can use it just fine.
3. Install a starter package
No featured starters are available right now. Copy the Choose your own adventure prompt to explore with your agent, or browse community packages.
- Build it yourselfChoose your own adventureSkip the starters and ask your agent what Kody can do — connect an integration, explore, and build something custom.Copies a prompt you can paste into your agent to explore what Kody can do and build something custom.

Bring your own keys
Kody never asks a company for access on your behalf. You create the connection yourself — your agent walks you through it — so it is completely yours: your app, your scopes, no middleman.
Typical appsYouTheir shared appGitHub
KodyYouYour own appGitHub
- Your keys, your scopes. You decide exactly what Kody can touch, and you can revoke it anytime.
- No middleman. Nothing sits between you and the provider — no shared app to trust or get breached.
- No fixed list. If it has an API, your Kody can learn to use it.
The trade-off: a few minutes of setup instead of one click. Your agent does the tedious parts.