One connection, and your AI has the team's tools.

Kythene as your team's MCP gateway, for getting a team set up. Give each person's AI the team's MCP servers, your own APIs turned into tools, and the skills that say how you do things - curated per role, with an audit log of every call made through them. Connecting your AI to Kythene is joining the team: you get its tools and how it does things.

Start free Read the Toolkits docs →

Today a new joiner is handed a list of servers to connect, keys to find and a skills folder to copy. Here an admin puts the kit together once, and a member connects once and gets it. Publish a new version of a skill and it reaches the AI of everyone whose toolkit holds it, with nobody reconnecting anything.

for the person setting it up

Build a kit once, give it to a role

A toolkit is a bundle of servers and skills you give to a group of people. Sales gets the CRM and the refund skill, support gets the helpdesk, and nobody's AI wades through tools they'll never use.

MCP servers, and APIs as tools: Add any MCP server. Or add a plain API from its OpenAPI document, or a Connect service by reflection or a descriptor set, and pick the operations that become tools.
On unless you switch it off: A server brings all its tools, prompts and skills. Untick the three you don't want; when the server adds a fourth, you don't have to touch the toolkit. Tools that can delete or overwrite are marked.
Skills your team writes: Write "this is how we deploy" once, as a skill, and the people you give it to have it in their AI. Publish a new version and it's live for the people who hold it, with no release and nothing to reinstall.
Several toolkits each: A member can be in more than one and gets everything in all of them, each thing once.
Their account, or one shared key: Each member signs in to a server as themselves, so it applies their own permissions and its logs say who did what. Or share one key for a server that wants one. Keys are sealed and never shown again.

for their AI

One connector, the whole kit

Your team gets one MCP address, the team's own, and it carries Kythene's tools plus whatever their toolkits hold. Nothing to install on their side, and a change to the kit reaches connected AI without reconnecting.

Tools next to Kythene's: A server's tools arrive named after it, so crm__find_contact can't collide with another server's. Descriptions and schemas come through as the server wrote them.
Skills, loaded as they're needed: The AI lists the team's skills at the start of a session and fetches one when a task matches. Native skills take over in clients that read them over MCP.
Connect once, on My tools: Where each member signs in, they do it once, and My tools lists only the servers their toolkits hold. If their AI tries one they haven't connected, it hands them a link rather than a dead end.
Read-only for viewers: A viewer gets only the tools a server marks read-only, whatever a toolkit says.
Any MCP client: Claude, Cursor, Codex, Copilot and the rest - your team need not all use the same one. Connect yours →

How a kit gets built

Set it up once. Everyone else just connects.

Owners and admins build toolkits. Everyone else gets what theirs hold.

Add what the team uses

Add your CRM's MCP server, an internal API, a skill you've written. Kythene reads what each one offers, and saves it only if it can.

Put it in a toolkit

Name the toolkit, tick the servers and skills that go in, switch off any tool you don't want, and tick who gets it.

Members connect once

They add the team's connector to their AI and sign in where a server needs it. From then on the kit follows them, and follows the toolkit when you change it.

Nothing reaches anyone until a toolkit gives it

Adding a server or publishing a skill gives it to nobody (Kythene's own tools aren't affected). Until it's in a toolkit, Kythene says so on its page, and a call to something no toolkit gives you is refused. Take a server out of a member's kit and their sign-in to it is ended, so no credential sits around for something they can no longer use. And adding a server trusts it like Kythene's own code - what it says and returns reaches the AI of everyone you give it to - so add the ones you'd trust with that.

What your AI did, and as whom

Every call through the kit is on the record.

The audit log has each call made through the team's servers: who made it, which of their agents, the tool, the toolkit that gave it to them, how long the server took, what came of it, and the arguments and result in full. Owners and admins see everyone's; members see their own.

Filter it, and export what you've filtered to as NDJSON. Calls are kept for 12 months unless the owner sets another period.

On your own infrastructure too

Toolkits run on a self-managed install as well, with a licence that includes them. Same gateway, same audit log, your servers and your data.

Read about self-hosting → · Every capability, by group →

One place for the team and its AI

The kit is how they work. The rest is what they know.

artifacts

What the AI works with

The team's servers, APIs and skills, in one connection. You're here.

Give your team's AI one connection.

Start free Read the docs See pricing