Kody

io.github.kody-hqPublished by GitHub account kody-hqv1.0.7Updated Oct 29, 2026

Your agents' cloud for individuals and teams. Search, execute, packages, jobs, and credentials.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Kody is a hosted cloud for AI agents that keeps memory, credentials, code packages and scheduled jobs, reachable from any MCP host over OAuth.

What you can do
  • Search across the account's stored packages, jobs, credentials and memories
  • Execute code in a Code Mode flow rather than through a large fixed tool list
  • Manage packages and package apps hosted on the runtime
  • Manage jobs and automations, including scheduled runs
  • Keep and recall memories and credentials scoped to an account, team or org
When to use it
Useful when you want an agent's memory, secrets, small code packages and scheduled automations to persist and follow you across different MCP hosts, for an individual or a team, instead of living in one client.
Requirements
A remote MCP endpoint at kody.codes with OAuth sign-in; no local runtime, packages or environment variables are declared. A Kody account is needed, and team or org features depend on that account's setup.
Before you install
The service stores credentials and secrets for your agent, so granting access means trusting a third party with them. The execute flow runs code and jobs can run on a schedule, which can change or delete account state. Data is held in the provider's Cloudflare-hosted infrastructure.

Installation

In SourceWeft

  1. Open Kody in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.kody-hq%2Fkody/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[Kody logo]

Your agents' cloud: the memory, keys, code, and automations your AI agent keeps, portable across every MCP host. Built on Cloudflare Workers.

[Build Status] [Join the Discord] [TypeScript] [Node 26] [Cloudflare Workers] [TanStack Start]

Kody is Your agents' cloud: the memory, keys, code, and automations your AI agent keeps, portable across every MCP host. Built on Cloudflare Workers and the Model Context Protocol (MCP), it ships a TanStack Start website, Worker-based request routing, package runtime plumbing, and OAuth-protected MCP endpoints. The project favors a compact MCP surface with powerful search and Code Mode execute flows over a large static tool catalog.

Kody works for individuals and teams (orgs, teams, grants): each account holds isolated packages, jobs, credentials, memories, and related state. Tests and fixtures may seed deterministic local accounts, but no account is privileged at runtime. The repo follows several epicflare starter conventions.

The repo is organized as an Nx monorepo, with shared modules in packages/shared (@kody-internal/shared), the origin app worker under packages/worker, sibling workers under packages/platform-worker, packages/runtime-worker, and packages/jobs-worker, and mock Workers under packages/mock-servers/*. Production topology lives in docs/contributing/architecture/index.md.

Quick Start

bash
npm installnpm run dev

The dev server runs at localhost:3742 by default (the CLI picks the next free port and prints the resolved URL). Wrangler handles the local Cloudflare Workers runtime and D1 database automatically.

To scaffold a new project from the epicflare template instead, run npx create-epicflare.

See docs/contributing/getting-started.md for the full setup paths and expectations. Contributors and agents should start with AGENTS.md for repo-specific guidance.

If you are trying to understand what this repository is for, start with docs/contributing/project-intent.md.

Tech Stack

LayerTechnology
RuntimeCloudflare Workers
UI FrameworkTanStack Start
Package Managernpm
WorkspaceNx + npm workspaces
DatabaseCloudflare D1
Session/OAuthCloudflare KV
MCP StateDurable Objects on kody-platform
E2E TestingPlaywright
BundlerVite

Scope

  • Fair Source platform for individuals and teams, not a general-purpose agent harness
  • MCP-first architecture intended to work across compatible AI agent hosts
  • Compact MCP surface area preferred over a large static tool inventory
  • ChatGPT is a likely primary host target, while keeping the server usable from other MCP hosts where practical

How It Works

kody.codes  → kody-production (origin: TanStack Start, /mcp HTTP, OAuth, email, queues)                 ├─→ kody-platform  (MCP / mailbox / meter / repo-session DOs)                 ├─→ kody-runtime   (package apps, invoke API, StorageRunner)                 └─→ kody-jobs      (cron + JobManager; calls back via JobsHost)
kody.run    → kody-runtime (package-app zone routes)
  • packages/worker/src/index.ts is the origin entrypoint; platform, runtime, and jobs have sibling entrypoints (see architecture)
  • OAuth requests are handled first, then MCP requests, then static assets
  • Webhook ingress (including GET subscription challenges) is handled in the Worker fetch path before TanStack Start
  • Remaining website requests go through TanStack Start (packages/worker/start/http-entry.ts)
  • Client assets are bundled into packages/worker/public/ and served via the ASSETS binding

Documentation

DocumentDescription
docs/contributing/getting-started.mdSetup, environment variables, deploy
docs/contributing/environment-variables.mdAdding new env vars
docs/contributing/cloudflare-offerings.mdOptional Cloudflare integrations
docs/contributing/project-intent.mdScope, goals, and non-goals
docs/contributing/index.mdDeveloping and extending Kody
docs/use/index.mdUsing Kody over MCP
docs/contributing/setup/Local development and verification

Contributing

Outside pull requests to this repository need a signed inbound Contributor License Agreement. Public packages do not use that CLA.

See CONTRIBUTING.md and docs/contributing/index.md.

License

Kody is licensed under the Functional Source License, Version 1.1, ALv2 Future License (FSL-1.1-ALv2). You can use, copy, modify, create derivative works from, publicly perform, publicly display, and redistribute the software for any purpose other than Competing Use. Competing Use means making the software available to others in a commercial product or service that substitutes for Kody, substitutes for another product or service the licensor offers using Kody that existed when the version was made available, or offers the same or substantially similar functionality. Each version becomes available under the Apache License 2.0 on the second anniversary of the date that version was made available.

Public packages published through Kody do not use this repository's CLA and have no license gate; that is separate from this repository's license.

Built with ❤️ by Epic Web

Source: README.md at commit 89e772b

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.7LatestOct 22, 2026
  2. v1.0.6Oct 17, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.