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

# Replit

> Connect Replit Agent to Context.dev for live web research, scraping, and company data.

Connect Context.dev to Replit Agent through the Model Context Protocol (MCP). Ask Agent to search the web, read websites, extract structured data, or bring company logos and brand data into your app.

<Card title="Add Context.dev to Replit" icon="plug" href="https://replit.com/~?settings.show=true&settings.tab=integrations&connector=predefined-context_dev">
  Open the Context.dev integration in your Replit settings.
</Card>

## Prerequisites

* A [Replit account](https://replit.com) with access to Agent
* A [Context.dev account](https://context.dev/signup) with credits for tool calls

## Install and connect

<Steps>
  <Step title="Open the integration">
    Select **Add Context.dev to Replit** above while signed in to Replit. You can also open [Integrations](https://replit.com/integrations) and find Context.dev under **MCP Servers for Replit Agent**.
  </Step>

  <Step title="Authorize Context.dev">
    Select **Sign in** for Context.dev. Complete the Context.dev sign-in and authorization prompts, then return to Replit.
  </Step>

  <Step title="Start an Agent chat">
    Confirm that the connection shows as connected, then open a project and start an Agent chat. Replit automatically discovers the server's tools and makes them available across your projects.
  </Step>
</Steps>

<Info>
  Context.dev uses browser-based OAuth for MCP. You do not need to create or paste an API key into Replit for this connection.
</Info>

<Accordion title="Connect manually if the integration link is unavailable">
  In Replit's [Integrations](https://replit.com/integrations), select **+ Add MCP server**. Set **Display name** to `Context.dev` and **MCP Server URL** to:

  ```text theme={null}
  https://mcp.context.dev/mcp
  ```

  Leave custom headers empty. Select **Test & save** and complete Context.dev's OAuth flow.
</Accordion>

## Verify the setup

Ask Agent to make a request whose result you can inspect:

```text theme={null}
Use Context.dev to scrape https://www.context.dev and return the page title and source URL. Use the connected tool.
```

Confirm that Agent shows a successful Context.dev tool call with live output. If Replit asks for confirmation before running the tool, review and approve the request.

Tool calls use the credits in your connected Context.dev account.

## Use Context.dev in Agent

Name Context.dev in your prompt and describe the result you want:

```text theme={null}
Use Context.dev to retrieve the brand profile for linear.app, then build a landing page using its logo, colors, and fonts.
```

```text theme={null}
Use Context.dev to find Stripe's latest official product announcements. Summarize them and include the source URLs.
```

## Troubleshooting

| Symptom                                   | Fix                                                                                                        |
| ----------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Sign-in does not finish                   | Return to Replit's Integrations page, select Context.dev, and complete the browser authorization flow.     |
| Agent answers without calling Context.dev | Check the connection status in Integrations, then explicitly request a live Context.dev tool call in chat. |
| Calls fail for insufficient credits       | Review usage in the [Context.dev dashboard](https://context.dev/dashboard).                                |

## Reference

<CardGroup cols={2}>
  <Card title="Replit MCP setup" icon="book" href="https://docs.replit.com/build/connect-via-mcp">
    Official instructions for connecting MCP servers and using their tools in Agent.
  </Card>

  <Card title="Context.dev MCP guide" icon="robot" href="/install-mcp">
    Hosted server capabilities, authentication, and usage details.
  </Card>
</CardGroup>