> ## 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.

# Context.dev

> Give the Sazabi agent tools to resolve brand data, scrape and crawl websites into LLM-ready Markdown, extract structured data, and manage website-change monitors.

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

## About

This is an MCP connector that gives the Sazabi agent tools from Context.dev's hosted MCP server (`context-dev.stlmcp.com`). Context.dev uses a "Code Mode" tool scheme: instead of one tool per endpoint, it exposes `search_docs` (query the Context.dev SDK) and `execute` (run agent-authored TypeScript against the SDK in a sandbox), letting the agent compose brand lookups, scraping, extraction, and monitor operations into a single call. Sazabi stores your Context.dev API key securely and sends it as the `x-context-dev-api-key` header on each request.

**What the agent can do:**

* Resolve brand data by name, domain, email, stock ticker, or ISIN (logos, colors, socials, industry codes)
* Scrape and crawl websites into clean, LLM-ready Markdown, HTML, or images
* Extract structured data, styleguides, product catalogs, and NAICS/SIC industry classifications
* Create, update, run, and inspect website-change monitors

## Prerequisites

* A Context.dev account
* A Context.dev API key (`ctxt_secret_...`) from the [Context.dev dashboard](https://context.dev)

## 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 Context.dev in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Add your key

Create or copy an API key (`ctxt_secret_...`) from your [Context.dev dashboard](https://context.dev). Paste it into Sazabi. Sazabi stores it securely and sends it as the `x-context-dev-api-key` header to Context.dev's MCP endpoint at `https://context-dev.stlmcp.com`.

## Set up with the CLI

Context.dev authenticates with a Context.dev 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 context-dev --header x-context-dev-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**](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 API key is correct.

## Troubleshooting

**No tools discovered** — Confirm the API key is valid. Check that the key format starts with `ctxt_secret_`.

**Connection shows needs attention** — The API key may have expired or been revoked; create a new key and 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.