One endpoint, any agent
Point Claude, ChatGPT, Hermes Agent or your own code at a single MCP endpoint. The client stays the client, and the tools live on our side.
MetraClick · Managed MCP infrastructure
Put your AI to work, not to chat
MetraClick connects your agents to the systems you already run: CRM, CMS, website, mail and X. One MCP endpoint, one tool catalog, one place to grant, meter and revoke access.
Product
What MetraClick is
MetraClick is a managed Model Context Protocol server. An MCP server is the piece that lets an AI client call real tools instead of describing them: read a CRM contact, create a page, send a mail, publish a post, upload a file. We host that server, wrap the systems you already run, and keep the credentials on our side.
Every request carries a tenant. An environment sees only the tools it was granted and the credentials that belong to it, so two clients can use the same server without ever touching each other's data. Measured on 24 October 2026: 196 tools in the catalog, 11 tool families and 14 isolated environments, with the largest single environment holding 77 tools.
- 196
- tools in the catalog
- 11
- tool families
- 14
- isolated environments
- 1
- MCP endpoint
Capabilities
What the server does
Isolation by default
Each environment carries its own tenant, its own tool grants and its own credentials. Nothing is shared unless you share it.
Credentials stay server-side
Keys for CRM, CMS, X and mail sit encrypted on the server. They are never handed to the model and never end up in a prompt.
Read and write, not just read
Tools create pages, upsert records, send mail, publish posts and upload files, so the agent finishes the job instead of describing it.
Metered per tool
Every call is counted per environment and per tool. Usage is visible before the invoice, not after it.
Your own tools, wrapped
A legacy API or an internal script becomes a proper MCP tool with a schema, validation and a permission gate.
From prompt to record
The agent never holds a password and never talks to your database. It asks for a tool, the server checks who is asking, and the change happens on our side.
The agent calls a tool
Your client sends a tool call with its tenant key. No database credentials, no SQL, no shell.
MetraClick checks and routes
The server validates the arguments, checks the grant, decrypts the right credential and calls your system.
Your system changes
The record is written, the page is live, the mail is sent. The result returns to the agent as structured data.
- CRM
- CMS
- Website pages
- X
- Knowledge
- Custom APIs
FAQ
Questions before you connect
What is an MCP server?
Model Context Protocol is the open standard that lets an AI client call tools on a server. MetraClick is that server, hosted and managed for you, with the tools already wrapped.
Do I have to change my agent?
No. Any MCP-capable client works: Claude, ChatGPT connectors, Hermes Agent, or code your team writes. The endpoint and the tenant key are the only two things it needs.
Where does my data live?
In your systems. MetraClick stores the connection credentials, encrypted, and routes calls; the records stay where they already are. Each tenant is isolated from the others.
Which systems are supported?
CRM and contact databases, TYPO3 and KocoDesk content, website pages on our CDN, mailing and campaigns, X publishing, knowledge bases, and custom APIs we wrap for you.
How is it billed?
Per environment, monthly, with every tool call metered. The tool set is scoped on a free consultation, so the price follows what you actually use.
Is it only for KohlerCode clients?
No. MetraClick runs as its own service on its own infrastructure. KohlerCode builds with it, but the server is available to any team that wants its systems as tools.
Next step
See your own systems as tools
Tell us which systems your agents should reach, and we scope the tool set, the environments and the credentials on a call.