Sazabi
MCP connectors

Respan

Give the Sazabi agent tools to query LLM request logs, execution traces, prompts, and customer data from your Respan account.

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

Set up in the dashboard

Configure connectors in the dashboard under 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, and sazabi mcp-connectors connect only supports OAuth providers — so set up this connector in the dashboard first (above). Once it's connected, the Sazabi CLI can inspect and manage it (installed and authenticated — see sazabi mcp-connectors reference):

sazabi mcp-connectors list
sazabi mcp-connectors details <connection-id>

Find the connection ID with sazabi mcp-connectors list. To rotate the stored credentials later, use sazabi mcp-connectors update-credentials <connection-id>.

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.

Further reading