MCP Server for Windsurf/Roocode

Created By
bananabit-deva year ago
Model Context Protocol (MCP) server for Windsurf integration with image generation and web scraping capabilities.
Overview

What is MCP?

MCP is a Model Context Protocol server designed for Windsurf integration, providing capabilities for image generation and web scraping.

How to use MCP?

To use MCP, clone the repository, set up a virtual environment, install the required packages, and configure the server with your API keys. Then, you can generate images or scrape web content through the provided APIs.

Key features of MCP?

  • Image Generation: Create images using the Flux Pro model based on user prompts.
  • Web Scraping: Extract content from webpages using the ScrapeGraph API with options for markdown conversion and smart scraping.

Use cases of MCP?

  1. Generating unique images for creative projects.
  2. Extracting and analyzing content from online sources for documentation or sentiment analysis.
  3. Collecting structured data from websites for further processing.

FAQ from MCP?

  • Can MCP generate any type of image?

Yes! MCP can generate images based on the prompts provided by the user.

  • Is there a limit to the web scraping capabilities?

While MCP can scrape various websites, it's important to respect the rate limits of those sites.

  • How do I handle errors during scraping?

MCP includes error handling mechanisms to fall back to simpler extraction methods if needed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bananabit-dev
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago