Skrape MCP Server
OfficialSkrape MCP Server
Convert webpages into clean, LLM-ready Markdown using skrape.ai. An MCP server that seamlessly integrates web scraping with Claude Desktop and other MCP-compatible applications.
Key Features
Clean Output: Removes ads, navigation, and irrelevant content
JavaScript Support: Handles dynamic content rendering
LLM-Optimized: Structured Markdown perfect for AI consumption
Consistent Format: Uniform structure regardless of source
Features
Tools
get_markdown- Convert any webpage to LLM-ready MarkdownTakes any input URL and optional parameters
Returns clean, structured Markdown optimized for LLM consumption
Supports JavaScript rendering for dynamic content
Optional JSON response format for advanced integrations
Installation
Installing via Smithery
To install Skrape MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @skrapeai/skrape-mcp --client claudeManual Installation
Get your API key from skrape.ai
Install dependencies:
npm installBuild the server:
npm run buildAdd the server config to Claude Desktop:
On MacOS:
nano ~/Library/Application\ Support/Claude/claude_desktop_config.jsonOn Windows:
notepad %APPDATA%/Claude/claude_desktop_config.jsonAdd this configuration (replace paths and API key with your values):
{
"mcpServers": {
"skrape": {
"command": "node",
"args": ["path/to/skrape-mcp/build/index.js"],
"env": {
"SKRAPE_API_KEY": "your-key-here"
}
}
}
}Using with LLMs
Here's how to use the server with Claude or other LLM models:
First, ensure the server is properly configured in your LLM application
Then, you can ask the ALLMI to fetch and process any webpage:
Convert this webpage to markdown: https://example.com
Claude will use the MCP tool like this:
<use_mcp_tool>
<server_name>skrape</server_name>
<tool_name>get_markdown</tool_name>
<arguments>
{
"url": "https://example.com",
"options": {
"renderJs": true
}
}
</arguments>
</use_mcp_tool>The resulting Markdown will be clean, structured, and ready for LLM processing.
Advanced Options
The get_markdown tool accepts these parameters:
url(required): Any webpage URL to convertreturnJson(optional): Set totrueto get the full JSON response instead of just markdownoptions(optional): Additional scraping optionsrenderJs: Whether to render JavaScript before scraping (default: true)
Example with all options:
<use_mcp_tool>
<server_name>skrape</server_name>
<tool_name>get_markdown</tool_name>
<arguments>
{
"url": "https://example.com",
"returnJson": true,
"options": {
"renderJs": false
}
}
</arguments>
</use_mcp_tool>Development
For development with auto-rebuild:
npm run watchDebugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/skrapeai/skrape-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server