snapforge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SNAPFORGE_API_KEY | Yes | Your SnapForge API key | |
| SNAPFORGE_BASE_URL | No | Base URL for SnapForge API (default: https://snapforge.org) | https://snapforge.org |
Instructions
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| snapforge_screenshotA | Capture a screenshot of a public URL or raw HTML and return it as an image (PNG/JPEG). Full-page by default. |
| snapforge_pdfB | Render a public URL or raw HTML to a PDF. The PDF is written to a temp file and its path is returned. |
| snapforge_markdownA | Extract a clean Markdown version of a public URL or raw HTML (article extraction + HTML→Markdown). Great for feeding live web content to an LLM. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct output format (image, PDF, markdown) with no overlap in functionality, making selection unambiguous.
All tools follow the consistent prefix 'snapforge_' followed by a clear noun describing the output, forming a predictable pattern.
Three tools is an appropriate scope for a server focused on converting web content to common formats—neither too few nor too many.
Covers the three most common output conversions (image, PDF, markdown), though additional options like plain text or specific rendering parameters are absent.