Kody

What Kody does

Kody provides a cloud-backed home for agent state and capabilities. It is built for individuals and teams, with account-level isolation for packages, scheduled or managed jobs, credentials, memories, and related data. Rather than exposing a long static catalog of narrowly scoped tools, Kody emphasizes two central interaction patterns: searching available state and running code through Code Mode.

The service is designed around the Model Context Protocol, so an MCP-compatible host can connect to its endpoints and use the agent-facing surface. Kody also includes a web application and a Worker-based backend that coordinates package execution, platform state, and jobs.

How it works

Kody runs on Cloudflare Workers. Its origin worker handles OAuth, MCP requests, webhooks, website traffic, and static assets. Requests can then be routed to separate platform, runtime, and jobs workers. Platform services manage MCP-related state, mailbox and metering functions, and repository sessions; runtime services host package applications and invocation APIs; the jobs worker handles cron activity and job management.

The service uses Cloudflare D1 for database storage, KV for sessions and OAuth-related state, and Durable Objects for MCP state on the platform worker. Package applications can be reached through the kody.run package-app zone, while the main kody.codes origin provides the website and /mcp endpoint. OAuth protects MCP access, and account boundaries keep user and team resources separate.

Setup and configuration

For local development, install the repository dependencies and start the development server:

npm install
npm run dev

The local service normally starts on port 3742, although the CLI selects another available port when necessary and prints the resulting URL. Wrangler supplies the local Cloudflare Workers runtime and D1 database. The project is organized as an Nx monorepo using npm workspaces, with the main application in packages/worker and supporting workers for platform, runtime, and jobs functions.

Kody is intended to be used through MCP-compatible hosts. Its production deployment uses OAuth-protected HTTP MCP endpoints and Cloudflare services, while local development is handled through the repository's Worker tooling.

Tools and capabilities

• Search agent-accessible state through the compact MCP surface.
• Execute code with the Code Mode execute flow.
• Store and use packages associated with an account or team.
• Manage jobs, including cron-backed work through the jobs worker.
• Keep credentials, memories, and related account state isolated.
• Route package applications through the runtime worker and kody.run.

Limitations and notes

Kody is a platform for agent memory, keys, code, and automations rather than a general-purpose agent harness. Its scope is MCP-first and favors a small tool surface over a large inventory of fixed tools. The project is built on Cloudflare Workers and depends on Cloudflare-oriented services such as D1, KV, and Durable Objects.

The repository is licensed under the Functional Source License, Version 1.1, with the Apache License 2.0 future license (FSL-1.1-ALv2). The license includes a restriction on Competing Use, and each version becomes available under Apache 2.0 two years after release. Public packages published through Kody are handled separately from the repository license.