Skip to content
Agentic Scraper

Connect MCP Market tools

Agentic Scraper has three MCP integration paths: direct MCP Market connections, MCP tools attached to Agentic Scraper agents, and private custom MCPs.

Connect an MCP Market integration directly

Open an approved integration in Dashboard → MCP Market and use Connect to your AI client. Enter:

  1. your Agentic Scraper API key;
  2. the integration’s required parameters, if any; and
  3. the client you use.

The dashboard generates a client-specific configuration for this endpoint:

https://mcp.agenticscraper.com/mcp/<MCP_MARKET_ID>

The generated asmcp_... bearer credential contains the MCP ID, your Agentic Scraper API key, and the integration parameters. It is a secret equivalent to your API key: do not commit, publish, log, or share it. Generate a new value if the API key or any parameter changes.

All approved tools are exposed by default. Calls use the authenticated Agentic Scraper account for access control, wallet checks, usage records, and marketplace billing. The credential is bound to one MCP Market ID and cannot be reused with another marketplace endpoint.

Codex

Paste the generated TOML into ~/.codex/config.toml:

[mcp_servers."agentic-<slug>"]
url = "https://mcp.agenticscraper.com/mcp/<MCP_MARKET_ID>"
http_headers = { Authorization = "Bearer <MCP_CLIENT_CREDENTIAL>" }

When an integration has no extra parameters, you can alternatively keep the plain Agentic Scraper API key in an environment variable and add it in one command:

Terminal window
codex mcp add agentic-<slug> \
  --url https://mcp.agenticscraper.com/mcp/<MCP_MARKET_ID> \
  --bearer-token-env-var AGENTIC_SCRAPER_API_KEY

Claude Code

Terminal window
claude mcp add --transport http agentic-<slug> \
  https://mcp.agenticscraper.com/mcp/<MCP_MARKET_ID> \
  --header "Authorization: Bearer <MCP_CLIENT_CREDENTIAL>"

The same URL and Authorization header work in Claude Desktop’s remote MCP configuration.

Cursor, Windsurf, and other mcpServers clients

{
  "mcpServers": {
    "agentic-<slug>": {
      "url": "https://mcp.agenticscraper.com/mcp/<MCP_MARKET_ID>",
      "headers": {
        "Authorization": "Bearer <MCP_CLIENT_CREDENTIAL>"
      }
    }
  }
}

VS Code

Add this server to .vscode/mcp.json or your user MCP configuration:

{
  "servers": {
    "agentic-<slug>": {
      "type": "http",
      "url": "https://mcp.agenticscraper.com/mcp/<MCP_MARKET_ID>",
      "headers": {
        "Authorization": "Bearer <MCP_CLIENT_CREDENTIAL>"
      }
    }
  }
}

Gemini CLI

Add this entry under mcpServers in ~/.gemini/settings.json:

{
  "mcpServers": {
    "agentic-<slug>": {
      "httpUrl": "https://mcp.agenticscraper.com/mcp/<MCP_MARKET_ID>",
      "headers": {
        "Authorization": "Bearer <MCP_CLIENT_CREDENTIAL>"
      }
    }
  }
}

ChatGPT

Custom MCP apps are configured independently from Codex; they do not share Codex’s local config.toml.

  1. Enable developer mode if it is available for your ChatGPT workspace.
  2. Go to Settings or Workspace settings → Apps → Create.
  3. Use the generated server URL and select bearer-token authentication.
  4. Paste only the generated MCP client credential as the token, scan the tools, and create the app.

ChatGPT custom MCP app availability and the exact menu depend on the workspace plan and admin policy.

Custom agent MCP configuration

The public REST API exposes:

  • POST /api/v1/agents/discover-mcp
  • POST /api/v1/agents
  • POST /api/v1/agents/run
  • PATCH /api/v1/agents/{id}

Custom agent requests can include market_mcps and custom_mcps. Their exact schemas are in the Client API reference.

MCP Market tools inside Agentic Scraper agents

Agent execution calls the same market proxy with stored, encrypted selections. Internal agent/selection headers are platform implementation details; external clients should use the direct endpoint and generated bearer credential above.

For entries using provider_event, the proxy does not apply the legacy tool price. It forwards signed charge-context headers to the provider. For entries using tool_call_fixed, the proxy applies the configured tool charge after a successful upstream tool call.

Documentation MCP

The read-only documentation search MCP is available at https://docs.agenticscraper.com/mcp. It retrieves guides and live OpenAPI operations and is unrelated to marketplace execution.