Prysm MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRYSM_OUTPUT_DIR | No | Custom output directory for saving formatted results. Default is ~/prysm-mcp/output/ |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrapeFocusedB | Fast web scraping optimized for speed (fewer scrolls, main content only) |
| scrapeBalancedC | Balanced web scraping approach with good coverage and reasonable speed |
| scrapeDeepC | Maximum extraction web scraping (slower but thorough) |
| formatResultC | Format scraped data into different structured formats (markdown, HTML, JSON) |
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 4 tools
Each tool has a clearly distinct purpose: formatResult handles output formatting, while the three scraping tools are well-differentiated by their approach (balanced, deep, and focused). The descriptions explicitly clarify their trade-offs (coverage vs. speed vs. thoroughness), leaving no ambiguity about when to use each.
The scraping tools follow a consistent 'scrapeAdjective' pattern (scrapeBalanced, scrapeDeep, scrapeFocused), which is clear and predictable. However, formatResult deviates from this pattern with a verb_noun structure, creating a minor inconsistency in the overall naming scheme.
With 4 tools, this server is well-scoped for web scraping and data formatting. Each tool earns its place by covering distinct aspects of the workflow (three scraping strategies and one formatting tool), avoiding bloat while providing essential functionality for the domain.
The toolset covers core scraping operations with multiple strategies and includes formatting capabilities, addressing key needs in the web scraping domain. A minor gap exists in lacking explicit tools for configuration (e.g., setting headers or proxies) or post-processing beyond formatting, but agents can likely work around this with the provided tools.