koncrate.recommend_plugins
Find catalog plugins that fit the current task.
Controlled MCP tool execution
Connect your agent to Koncrate once. It discovers installed plugins, and every tool call passes through one gateway that enforces install state, scopes, confirmation, and audit — before it ever reaches a plugin's backend.
Add the gateway as a remote MCP server. In Claude Code:
claude mcp add --transport http koncrate \
https://koncrate-gateway.linaomasa929.workers.dev/mcp
Or, for clients that take a JSON config:
{
"mcpServers": {
"koncrate": {
"type": "http",
"url": "https://koncrate-gateway.linaomasa929.workers.dev/mcp"
}
}
}
That's it — no per-plugin endpoints. One connection, scoped to your workspace.
On connect, the gateway tells the agent its policy and exposes self-serve tools. No prompt engineering required:
Find catalog plugins that fit the current task.
Ask to install a plugin — a human approves before tools appear.
Generate a manifest + a deployable backend skeleton from a short spec.
Submit a finished plugin to the catalog for review.
You own the business logic and the backend. Koncrate owns discovery, auth, policy, confirmation, audit, and billing.
Connecting and installing plugins is free. You pay only for paid plugins you use.
You set your own price — free, per-call, or monthly. Koncrate adds a small platform fee on top and handles metering, so you focus on the tool.
Billing is rolling out; the first cohort of plugins is free to publish.