Cekura
Give the Sazabi agent tools to test, monitor, and evaluate AI agent workflows directly from agent conversations.
All Cekura integration capabilities
About
Cekura is an MCP connector that gives the Sazabi agent tools to test, monitor, and evaluate AI agent workflows. Cekura's MCP server accepts API key authentication via HTTP headers. Sazabi stores your key securely and sends it as the X-CEKURA-API-KEY header to Cekura's MCP endpoint. Once connected, the agent can run evaluations, check workflow health, and surface issues in your AI pipelines.
What the agent can do:
- Run evaluations and test suites against AI agent workflows
- Monitor workflow health and surface failures
- Retrieve evaluation results and historical run data
- Trigger on-demand checks on specific workflow configurations
- Browse workflow definitions and test case libraries
Prerequisites
- A Cekura account
- A Cekura API key from Settings > API Keys in the Cekura dashboard
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Cekura in Settings > MCP connectors.
Add your key
Paste your Cekura API key; Sazabi sends it as the X-CEKURA-API-KEY header to Cekura's hosted MCP endpoint. Create or copy a key from Settings > API Keys in the Cekura dashboard.
Set up with the CLI
Cekura authenticates with a Cekura API key. With the Sazabi CLI installed and authenticated (see sazabi mcp-connectors reference), connect it in one command, passing the credential as a header:
sazabi mcp-connectors connect cekura --header X-CEKURA-API-KEY=<api-key>The CLI connects to the MCP server at once and prints the connection with the tools it discovered; a credential the server rejects is reported, and the connection is left needing attention. Use NAME=@<file> to read a value from a file, or --header-file <file.json> for a JSON object of header names and values. To rotate the stored credentials later, use sazabi mcp-connectors update-credentials <connection-id>; find the connection ID with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the key is correct.
Troubleshooting
No tools discovered — Check that the API key is valid and was copied correctly from the Cekura dashboard.
Connection shows needs attention — The key may have expired or been revoked; reconnect from Settings > MCP connectors.