Crawlab MCP Server

Created By
crawlab-teama year ago
Overview

what is Crawlab MCP Server?

Crawlab MCP Server is a Model Context Protocol (MCP) server designed for Crawlab, enabling AI applications to interact seamlessly with Crawlab's functionalities.

how to use Crawlab MCP Server?

To use the Crawlab MCP Server, install it as a Python package or run it locally using Docker. After installation, start the server and configure your AI application to connect to it.

key features of Crawlab MCP Server?

  • Spider management (create, read, update, delete)
  • Task management (run, cancel, restart)
  • File management (read, write)
  • Resource access (spiders, tasks)
  • Natural language interaction with Crawlab functionalities

use cases of Crawlab MCP Server?

  1. Automating web scraping tasks through AI commands.
  2. Managing and monitoring spider tasks in real-time.
  3. Integrating with AI applications for enhanced data extraction capabilities.

FAQ from Crawlab MCP Server?

  • What is the MCP Server used for?

The MCP Server allows AI applications to communicate with Crawlab for managing web scraping tasks and resources.

  • How do I install the MCP Server?

You can install it as a Python package or run it using Docker. Detailed instructions are provided in the documentation.

  • Can I use the MCP Server with any AI application?

Yes! The MCP Server is designed to work with various AI applications that can send natural language queries.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
crawlab-team
Star
1
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago