clawifi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAWIFI_API_KEY | Yes | Clawifi API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchC | Fetch a single URL and return its extracted content. |
| scrapeC | Scrape a URL with source-aware routing and return structured content. |
| search_freeC | Run a free-tier web search and return results. |
| extractC | Extract structured data from a URL. |
| map_siteC | Map a site's discoverable URLs starting from a seed URL. |
| crawlC | Start an asynchronous crawl from a seed URL. Returns a crawl_id to poll. |
| get_crawlC | Get the current status and results of a crawl. |
| create_jobC | Create an asynchronous job for a billable operation. Returns a job_id to poll. |
| get_jobC | Get the current status and results of a job. |
| accountA | Get the authenticated account's profile and plan. |
| creditsA | Get the authenticated account's credit usage and remaining balance. |
| list_historyC | List past requests for the authenticated account. |
| list_monitorsC | List configured Evidence Monitor checks for the authenticated account. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Tools like fetch, scrape, and extract have overlapping descriptions (all extract content from URLs), making it ambiguous which to use for a given task. Other tools are distinct, but this cluster reduces clarity.
Most tools follow a verb_noun pattern (e.g., get_crawl, create_job), but a few are single verbs (fetch, scrape, extract) which is a minor deviation. Overall, the naming is clear and predictable.
13 tools cover the core functionalities of web scraping, crawling, job management, account info, and monitoring without being excessive. Each tool serves a distinct purpose.
The tool set covers primary workflows (fetch, scrape, crawl, search) but lacks creation or management of monitors beyond listing, and job management only supports create/get, missing delete or update.