MCP
One gateway for all products, with one login. Each product has its own endpoint under the same OAuth connection:
https://mcp.prudai.com/mcp/<product>https://mcp.prudai.com/mcp is a directory of the endpoints per product.
The gateway is an OAuth resource server (RFC 9728) with Keycloak as the authorization server. You connect an assistant with your own Prudai account; there is no key per product. For each call the gateway exchanges your token for a short-lived token for that one product, with your rights. See Login.
The tools
Section titled “The tools”Each product has the same four meta-tools. That keeps the load small, even with hundreds of operations:
| Tool | What it does |
|---|---|
search_tools | Searches tools: task tools first, the separate operations on request |
describe_tool | Gives the full input schema from the OpenAPI specification |
execute_tool | Runs the tool, with your rights and the same envelope |
get_guide | Gives the manual for this product |
Task tools combine several /v1 calls in the language of the user. Every result says what is known, what is not (notIncluded) and what the logical next steps are (next).
Writing
Section titled “Writing”execute_toolis a dry run, unless you passdryRun: false.- An action that asks for approval gives
approval_required; the decision is up to a person. - An action with level
forbidden_for_agentsdoes not reach the product. - Each call leaves one audit line: who, organisation, product, tool and outcome. No content.
Checking from the CLI
Section titled “Checking from the CLI”prudai mcp --checkprudai mcp connections list