> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The Context Company

> Give the Sazabi agent read-only observability tools to query agent insights, runs, and sessions.

[All The Context Company integration capabilities](https://docs.sazabi.com/catalogs/integrations/context-company)

## About

This is an MCP connector that gives the Sazabi agent tools from The Context Company's hosted MCP server at `https://api.thecontext.company/mcp`. Sazabi stores your read-only API key securely and sends it as the `Authorization: Bearer` token. Write tools are blocked by the per-connection read-only toggle.

**What the agent can do:**

* Search agent insights with `insight_search`
* Inspect agent runs with `get_agent_runs`
* Inspect agent sessions with `get_agent_sessions`

## Prerequisites

* An account with The Context Company
* A read-only API key from the [MCP access documentation](https://docs.thecontext.company/access-data/mcp)

## Set up in the dashboard

Configure connectors in the dashboard under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find The Context Company in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Add your key

Generate a read-only API key following The Context Company's [MCP access documentation](https://docs.thecontext.company/access-data/mcp). Sazabi stores it securely and sends it as `Authorization: Bearer <key>` to `https://api.thecontext.company/mcp`.

## Set up with the CLI

The Context Company authenticates with an API key. With the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) installed and authenticated (see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)), connect it in one command, passing the credential as a header:

```bash theme={"system"}
sazabi mcp-connectors connect the-context-company --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**](https://app.sazabi.com/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. Re-enter it from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Connection shows needs attention** — The authorization or key may have expired or been revoked; reconnect from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/guides/investigate/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/mcp-connectors.md)
>
> Browse the connector catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.