Reference
MCP
Raindex MCP lets a compatible agent client call the same shared workflows as the REST API and the Raindex Agent, over Streamable HTTP with an Account-scoped API key. MCP grants no authority beyond the Account and capability rules Raindex already enforces.
Client configuration
- Create an API key in the Developer Console.
- Store it in your client's secret store and send it as a Bearer token.
- Add the endpoint through your client's HTTP MCP setup. No local package is required.
mcp.json
{
"mcpServers": {
"raindex": {
"url": "https://raindex-backend.onrender.com/mcp",
"headers": {
"Authorization": "Bearer raindex_your_key_here"
}
}
}
}Verify the endpoint
The health check is public. Tool discovery and invocation require a valid API key.
Health check
curl https://raindex-backend.onrender.com/mcp/healthFirst call and governed actions
- Start with
raindex_get_product_context, then inspect only the capabilities the task needs. - After connecting,
tools/listreturns only the tools available to the key's Account. - Preview is not Apply. Mutating tools keep typed confirmation, owner validation and durable receipts. See Governed actions.
Tool schema reference
The global schema reference for registered shared workflows, read live from https://raindex-backend.onrender.com/mcp/tools.
This list is not filtered to any Account.It describes contracts only. A tool listed here may be unavailable to your Account. Your client's authenticated
tools/list, or Capabilities in the Developer Console, is authoritative.Loading the current tool schemas…