Skip to content

Kody for OpenMuse

Wire Kody into your OpenMuse harness so the work it does reaches the rest of your team.

Connect OpenMuse

OpenMuse has no settings screen for MCP servers, so Kody connects through the harness behind your OpenMuse deployment. A chat prompt alone cannot add it.

  1. Register Kody as an MCP server in the harness behind your OpenMuse fork. The guide covers both ways to wire it in.

    Read OpenMuse and Kody

  2. Point the harness at this URL (Streamable HTTP with OAuth sign-in):

    https://kody.codes/mcp

  3. Once the harness is wired up, paste this setup prompt into OpenMuse to sign in and get started.

More ways to connect

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