Overview
What is MCP Grareco?
MCP Grareco is an MCP server that generates graphic recordings (visual summaries) from web page URLs or plain text. It uses the MCP protocol to convert content into an HTML-based graphic recording format. It is designed for developers and users of MCP-compatible clients such as Claude Desktop.
How to use MCP Grareco?
Install with npm install, build with npm run build, then run in STDIO mode (npm run start) or SSE mode (npm run start:sse). For Claude Desktop, add a configuration entry to cline_mcp_settings.json that invokes the server via npx -y mcp_grareco or connects to an SSE endpoint. Use the tools webToGrareco (with a URL) or textToGrareco (with a text string) to generate graphic recordings.
Key features of MCP Grareco
- Converts web pages to graphic recording HTML
- Converts plain text to graphic recording HTML
- Supports three prompt types: standard, elementary, timeline
- Sends progress notifications during conversion
- Includes debug tools: echo and printEnv
- Sends random-level log messages every 15 seconds
Use cases of MCP Grareco
- Generate a visual summary of a web article or blog post
- Create educational graphic recordings tailored for elementary school students
- Produce timeline-style graphic recordings from chronological text
- Debug MCP server configuration using the printEnv tool
FAQ from MCP Grareco
What tools does MCP Grareco provide?
Four tools: echo (echoes a message), printEnv (shows all environment variables), webToGrareco (converts a URL to a graphic recording HTML), and textToGrareco (converts text to a graphic recording HTML).
What prompt types are available?
Three prompt types: standard (default), elementary (for children), and timeline (for chronological content).
How does the server report progress?
During webToGrareco and textToGrareco processing, the server sends progress notifications using the MCP notifications/message method.
How can I run MCP Grareco?
You can run it in STDIO mode (npm run start) or SSE mode (npm run start:sse). For SSE mode, the server listens on http://localhost:3000/sse by default.
Are there any debug tools?
Yes, echo and printEnv help verify server setup and inspect environment variables for troubleshooting.
