storybook
01MCP server Claude CodeCodexCursor +2
One of 5 in .mcp.json
MCP server "storybook", hosted remotely at baldasseva--storybook-mcp.apify.actor, as configured in apify/apify-mcp-server.
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
Apify MCP Server connects AI agents to Apify's collection of web scrapers, crawlers, and automation tools through the Model Context Protocol, allowing them to extract data from websites, search engines, social media, maps, and online stores. It is for users who want agents to collect web data through compatible clients such as Claude Code, Claude.ai, Cursor, or VS Code. The catalogue entries configure or extend agent use of this MCP server.
This repository also configures its own agents. See what apify-mcp-server tells them →
MCP server Claude CodeCodexCursor +2
One of 5 in .mcp.json
MCP server "storybook", hosted remotely at baldasseva--storybook-mcp.apify.actor, as configured in apify/apify-mcp-server.
MCP server Claude CodeCodexCursor +2
One of 5 in .mcp.json
MCP server "figma", hosted remotely at mcp.figma.com, as configured in apify/apify-mcp-server.
MCP server Claude CodeCodexCursor +2
One of 5 in .mcp.json
MCP server "dev", hosted remotely at localhost, as configured in apify/apify-mcp-server.
MCP server Claude CodeCodexCursor +2
One of 5 in .mcp.json
MCP server "stdio" as configured in apify/apify-mcp-server. Runs dist/stdio.js with node. Needs 2 environment variables to run.
MCP server Claude CodeCodexCursor +2
One of 5 in .mcp.json
MCP server "stdio-full" as configured in apify/apify-mcp-server. Runs dist/stdio.js with node. Needs 2 environment variables to run.
MCP server Claude CodeCodexCursor +2
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡. Remote server at mcp.apify.com.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: