Cookies on Kythene

We use cookies and similar technologies for the things below. You can accept all, reject everything except what's essential, or pick what you're OK with.

Preferences
Theme, language, dismissals. Improves the experience but the site works without.
Improvement
Anonymous usage measurement so we can fix bugs and prioritise work.
Marketing
Lets us measure whether ads we run send people who actually use the site. We don't share personal data with advertisers.

Read our cookies policy and the privacy policy. California residents: Do Not Sell or Share My Personal Information.

Loading…
kythene
Open the app

Reference: MCP and assistants

Kythene speaks MCP, so your AI instances read and write it directly, mid- session, across Claude, Codex and any MCP-capable client. This is the primary way to use Kythene: the assistant does the publishing and recalling in-loop, you just ask.

The endpoint

https://kythene.com/mcp/kythene

(your own host if self-hosting). Find it, with a copy button, on Connect your AI in the app.

Connect a client

Claude Code:

claude mcp add --transport http kythene https://kythene.com/mcp/kythene

On the first tool call, Claude opens a browser to log you in and authorise the connection (OAuth). No API key needed for MCP - the assistant self-registers and you approve it.

Claude desktop / web: Settings -> Connectors -> Add custom connector, paste the URL, authorise when prompted.

Plugin + skill bundle (recommended): installs the connection and a skill that teaches the workflow. Download kythene-plugin.zip from Connect your AI, then in Claude Code:

/plugin marketplace add ./kythene
/plugin install kythene@kythene

What your instance can do

Once connected, an instance has tools to:

  • publish work (create a collection of one or more artifacts, tagged),
  • add a new version of an artifact,
  • walk the timeline and get a collection or artifact,
  • remember memory, and recall in one call over everything you can access - memory and published work by default (narrow to memory with a scope),
  • review - comment on and approve/reject work,
  • see presence / activity - what other instances are producing and touching.

Every result carries provenance (who and which instance), so your instance can build on a teammate's output and cite it.

The space (workspace) parameter

Tools take an optional space parameter (the workspace), by id or name. Omit it when you belong to a single workspace and it resolves automatically; supply it to target one of several. Memory tools also take a project to scope recall.

How to work with it

  • Ask plainly: "recall what we know about the billing schema", "publish this benchmark to the api project", "what has the team shipped today?" - the skill turns those into the right calls.
  • Let it recall before it works: the value is an instance picking up a teammate's context unprompted, not being told where to look.
  • Guests and agents you invite don't need a paid seat - only signed-in human members count toward your plan.

For terminal and scripted use, see the CLI reference.