Get started with Kody

Install Kody directly, or open Customize and add a remote MCP server with the URL below. You can also merge the JSON into ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).

https://heykody.app/mcp

JSON config (merge under your existing mcpServers if you already have one):

{
  "mcpServers": {
    "kody": {
      "url": "https://heykody.app/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.

In ChatGPT, turn on Developer mode under Settings → Security and login. Developer mode is available on the web for eligible paid plans (Plus, Pro, Business, Enterprise, and Education). In a managed workspace, ask an admin to enable access if the setting or Plugins UI is missing. Then open Settings → Plugins → Browse plugins → Create app. Paste the MCP URL below as the server URL. For the app icon, download Kody's favicon from the link below. Owners can edit a developer-mode app's name and logo later from its Manage menu in Apps settings. Complete OAuth when prompted.

https://heykody.app/mcp

https://heykody.app/apple-touch-icon.png

Using Kody packages works great with non-coding agents. For creating or editing packages, a coding agent such as Cursor, Claude Code, Codex, Copilot, or OpenCode is usually smoother — those hosts can edit files and iterate on code more easily.

Codex (ChatGPT desktop, Codex CLI, and the IDE extension) shares ~/.codex/config.toml. Add this streamable HTTP entry, then run codex mcp login kody if OAuth does not start automatically:

[mcp_servers.kody]
url = "https://heykody.app/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.

In Claude Desktop, open Settings → Connectors (or Customize → Connectors), add a custom connector, and paste this MCP URL. Claude Desktop handles remote OAuth through that UI — do not put the remote URL into claude_desktop_config.json.

https://heykody.app/mcp

After connecting, start a new chat and ask Claude to list Kody tools before the first task. Claude Desktop often does not bind MCP tools until that next turn.

Using Kody packages works great with non-coding agents. For creating or editing packages, a coding agent such as Cursor, Claude Code, Codex, Copilot, or OpenCode is usually smoother — those hosts can edit files and iterate on code more easily.

In Grok.com → Connectors, click New Connector, select Custom, and paste this MCP URL. Complete OAuth when Grok prompts you. For Grok Business and Enterprise, a team admin must first add this custom MCP server in the cloud console. Members can then connect it from the Grok connectors page. See xAI's custom MCP connector docs for details.

https://heykody.app/mcp

Using Kody packages works great with non-coding agents. For creating or editing packages, a coding agent such as Cursor, Claude Code, Codex, Copilot, or OpenCode is usually smoother — those hosts can edit files and iterate on code more easily.

Prefer the CLI (user scope, all projects):

claude mcp add --transport http -s user kody https://heykody.app/mcp

Or merge this into a project .mcp.json (or the user-scoped mcpServers block). Claude Code requires type: "http" for remote servers:

{
  "mcpServers": {
    "kody": {
      "type": "http",
      "url": "https://heykody.app/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.

Add this to your OpenCode config (opencode.json in the project, or your global OpenCode config). OpenCode uses type: "remote" and will start OAuth when needed:

{
  "mcp": {
    "kody": {
      "type": "remote",
      "url": "https://heykody.app/mcp",
      "enabled": true
    }
  }
}

You can also run opencode mcp add and paste the URL interactively, then opencode mcp auth kody if prompted.

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.

In VS Code (Copilot Chat): install Kody directly, create or edit .vscode/mcp.json in your workspace, or open user MCP config via the MCP: Open User Configuration command. VS Code uses the root key servers, not mcpServers:

{
  "servers": {
    "kody": {
      "type": "http",
      "url": "https://heykody.app/mcp"
    }
  }
}

Use Agent mode in Copilot Chat so MCP tools are available, then complete OAuth when VS Code opens it.

In Copilot CLI: add a remote HTTP server (writes ~/.copilot/mcp-config.json). Copilot CLI does not read .vscode/mcp.json:

copilot mcp add --transport http kody https://heykody.app/mcp

Or merge this into ~/.copilot/mcp-config.json (root key mcpServers):

{
  "mcpServers": {
    "kody": {
      "type": "http",
      "url": "https://heykody.app/mcp"
    }
  }
}

See GitHub's Copilot CLI MCP docs for details. For the desktop GitHub Copilot app, use the Copilot App tab.

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.

In the GitHub Copilot app, open settings and go to MCP Servers. Add a custom remote HTTP server with this MCP URL, then complete OAuth when the app opens it:

https://heykody.app/mcp

Servers you already configured for Copilot CLI (or in a repository) are also available in the app. You can merge this into ~/.copilot/mcp-config.json instead:

{
  "mcpServers": {
    "kody": {
      "type": "http",
      "url": "https://heykody.app/mcp"
    }
  }
}

See GitHub's Copilot app customization docs for MCP Servers, skills, and plugins.

Using Kody packages works great with non-coding agents. For creating or editing packages, a coding agent such as Cursor, Claude Code, Codex, Copilot, or OpenCode is usually smoother — those hosts can edit files and iterate on code more easily.

Any MCP-capable host that supports remote / streamable HTTP servers can connect to Kody. Add a remote MCP server pointed at this URL and complete the OAuth flow when the host opens it:

https://heykody.app/mcp

Config file shapes differ by host. If your client expects a JSON mcpServers map with a url field, start from the Cursor or Copilot CLI snippet; if it uses servers with type: "http", use the Copilot (VS Code) snippet.