klaut.pro
One MCP. One bill for every agent tool.
Connect your agents to one MCP endpoint. Pay for usage from one token balance.
One login. One tool list. One token balance.
Your agents call klaut over MCP for shared tools and billing.
Too many tools means too many bills.
Each tool brings its own server, API key, and invoice. It is hard to see who called what. It is hard to pay for it in one place.
How it works
Three steps from agent to tools and billing.
- 01ConnectPoint your agent at the klaut MCP URL.
- 02ManageTurn tools on, set key limits, and choose who can call them.
- 03MeterEach call uses tokens from one balance. You can set a cap.
Tools on the wire
Capabilities your agents call through one MCP API.
- SecretsKeys and passwords with limits
- MailSend email from agents
- SearchSearch the web or your data
- DatabaseStore agent state
- StorageKeep files
- LiteratureResearch with sources
- WritingWrite scientific reports. Make text sound natural.
One token bill
One balance. See usage per tool. Cap spend per agent. Pricing details come with early access.
Need a tool we do not have?
Tell us what you need. We read every wish, pick what to build next, and add it to the same MCP and the same token bill.
FAQ
Straight answers for teams evaluating klaut.
What is the klaut MCP API?
One MCP endpoint. Your agents call klaut tools through it.
How do my other MCP servers fit?
Keep your own tools. Use klaut for shared tools, login, logs, and billing.
How does the token bill work?
Calls use tokens from one balance. You see usage per tool. You can cap each agent.
How do agents log in?
Each agent gets its own login with limited keys, rotation, and logs.
Can we ask for a missing tool?
Yes. Use Wish a tool. We use wishes to plan early access.
When can we get in?
In waves. Join the waitlist with a work email.
From the field
How-tos, comparisons, and plain-language notes on MCP and agent tools.