Respan
Give the Sazabi agent tools to query LLM request logs, execution traces, prompts, and customer data from your Respan account.
All Respan integration capabilities
About
This is an MCP connector that gives the Sazabi agent tools from Respan's hosted MCP server at https://mcp.respan.ai/api/mcp. Respan is an LLM observability platform formerly known as Keywords AI. Sazabi stores your Respan API key securely and sends it as the Authorization: Bearer token to Respan's MCP endpoint. Write operations such as creating a log are governed by the per-connection read-only toggle.
What the agent can do:
- Query and filter LLM request logs (
list_logs,get_log_detail,create_log) - Inspect execution traces and span trees (
list_traces,get_trace_tree) - Read customer data and budget usage (
list_customers,get_customer_detail) - Manage prompt templates and versions (
list_prompts,get_prompt_detail,list_prompt_versions,get_prompt_version_detail)
Prerequisites
- A Respan account
- A Respan API key from the Respan dashboard
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Respan in Settings > MCP connectors.
Add your key
Create or copy an API key from the Respan dashboard. Sazabi stores it securely and sends it as the Authorization: Bearer token to Respan's MCP endpoint (https://mcp.respan.ai/api/mcp).
Set up with the CLI
Respan authenticates with a Respan 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 respan --header "Authorization=Bearer <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 — Confirm the API key is valid and has not been revoked. Re-enter it from Settings > MCP connectors.
Connection shows needs attention — The authorization or key may have expired or been revoked; reconnect from Settings > MCP connectors.