Any language, any host
Write the server in whatever your team already writes, and run it where the data is.
Your agents reach everything your work already runs on.
GitHub, Stripe, Supabase, Chrome, email, phone — and anything that speaks MCP, including the system nobody else integrates with.
Your agentsees only the tools it was given
MCPone protocol for every tool
- GitHubrepos · PRs
- Striperevenue
- Supabaseyour data
- Chromesigned-in web
- Your own APIsprivate MCP
- Emailthreads
Available tools
Fifteen to start with, and anything that speaks MCP.
The homepage's toolbelt, one card each. The caption is what the agent actually gets from it.
Your systems
GitHubrepos · PRs
Striperevenue
Supabaseyour data
Chromesigned-in web
Your own APIsprivate MCP
Reaching people
Emailthreads
WhatsAppchats
Phone callsspoken
Calendarbooking
Handoff to youbefore it sends
What they produce
Documentssourced
Videovia plugins
Imagesbest model
CodePR, never merge
Researchcited
Not on the list? If it speaks MCP, your agents can use it — including the internal system nobody else integrates with.
How to connect
Three steps, and the third is a person.
A connection is made once for the workspace, granted per agent, and gated by a human before anything leaves.
- 01
Pick the server
Choose from the list, or paste the endpoint of one you already run.
- 02
Grant it to an agent
Tools are whitelisted per agent. An agent sees only what it has been given.
- 03
Approve what leaves
Email, payments, merges: anything that leaves the building waits for a person.
{
"mcpServers": {
"github": { "url": "https://mcp.github.com/sse" },
"stripe": { "url": "https://mcp.stripe.com/" },
"lims": {
// the one nobody else integrates
"url": "https://lims.internal.example/mcp",
"auth": "oauth"
}
},
"agents": {
"iris": { "tools": ["lims", "github"] }
}
}Build your own
A private MCP for the system nobody else integrates.
MCP is an open protocol. A server is a list of tools with names, inputs and a handler; Kilogent does the rest.
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { z } from "zod";
const server = new McpServer({ name: "lims", version: "1.0.0" });
// one tool: a name, its inputs, and what it returns
server.tool("sample_status", { id: z.string() }, async ({ id }) => ({
content: [{ type: "text", text: await lims.status(id) }],
}));Private by default
The server stays on your side. Kilogent connects to it; the data does not move house.
We build it with you
Instrument data, an internal database, a legacy API. Enterprise and research groups get the connector built together.
Ask about a private MCPHow they run
Managed by Kilogent, metered per task.
Managed by Kilogentnothing to install
Scheduled workrecurring
Agent to agentone memory
Credit meterper task
Tool whitelistper agent
Agents that grow with you, not agents you grow out of.
Describe the problem today. The agents that solve it are born in minutes, and share the work with your people.