Schema | Scrapi MCP Server

Scrapi MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`apiKey`	No	Your Scrapi API key, alternative to SCRAPI_API_KEY environment variable.
`SCRAPI_API_KEY`	No	Your Scrapi API key (hsmcp_...). Can also be passed via --api-key CLI argument.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
scrape_urlA	Scrapes a webpage and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering.
scrape_urlsA	Scrapes multiple webpages in parallel and returns the content in AI-readable Markdown format. Can access blocked sites through browser rendering.
get_usageA	Check API usage and remaining credits. Returns current plan, subscription credits, purchased credits, and total remaining credits.
scraper_server_statusA	Check the status of all ScraperServer instances. Shows server health, circuit breaker state, failure counts, and last success/failure times.
get_billingB	Retrieve MCP billing information: subscription details, available plans, daily usage history, or spending limits.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bamchi/scrapi-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server