Skip to content
Weavz
Menu
Context.dev

Context.dev MCP integration

Scrape live web content, extract structured website data, capture screenshots, and retrieve brand intelligence.

Sign in, add Context.dev in Apps, then choose the account your AI can use.

4 tools
Use withChatGPTClaudeClaude CodeCursorCodexMCP clientsSetup guide

Tools

Name
scrape_markdown

Scrape a URL into clean GitHub Flavored Markdown for LLM and RAG workflows.

extract_structured_data

Extract schema-shaped data from a website using Context.dev Web Extract.

retrieve_brand

Retrieve brand, company, logo, social, and industry data from a domain, email, name, or ticker.

screenshot

Capture a viewport or full-page screenshot URL for a domain or direct URL.

Quick Start

TypeScript
import { WeavzClient } from '@weavz-io/sdk'

const weavz = new WeavzClient({ apiKey: 'wvz_...' })

const result = await weavz.actions.execute('context-dev', 'scrape_markdown', {
  workspaceId: '550e8400-e29b-41d4-a716-446655440000',
  integrationAlias: 'context-dev',
  input: { /* ... */ },
})

Related Integrations

Works well with

Frequently Asked Questions

Is there a Context.dev MCP server through Weavz?

Yes. Add the Context.dev integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 4 Context.dev actions.

What can an AI agent do with Context.dev?

Available actions include Scrape Markdown, Extract Structured Data, Retrieve Brand, Screenshot. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.

How do I connect Context.dev to Claude or ChatGPT?

Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add Context.dev, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.

Can I use Context.dev through an API or SDK?

Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.

What authentication does Context.dev require?

The catalog lists an API key for Context.dev. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.

How do I review sensitive Context.dev actions?

Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.

What limits or costs apply to Context.dev?

Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.

Connect Context.dev in minutes

Get 20,000 free action executions every month. No credit card required.