CrispParse MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRISPPARSE_API_KEY | No | Optional Bearer Macaroon API key from crispparse.com. Requests without a key receive an x402 Base USDC payment challenge. | |
| CRISPPARSE_API_URL | No | Optional upstream endpoint override. Defaults to https://api.crispparse.com/v1/extract. | https://api.crispparse.com/v1/extract |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crispparse_extractB | Extract clean, LLM-ready Markdown or structured JSON from any public URL using CrispParse. |
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 1 tool
With only a single tool in the server, there is no possibility of confusion or misselection between tools. The purpose of crispparse_extract is unambiguous.
The lone tool uses a clear, namespaced snake_case verb_noun pattern (crispparse_extract) that matches the server name. There is no competing convention to conflict with it.
A single tool is defensible for a narrow URL-to-Markdown extraction service, but it is thin: there is no companion tool for format discovery, batch extraction, or error/usage inspection. The surface feels minimal even for its focused scope.
For the core domain of fetching and converting a public URL into Markdown or structured JSON, one tool covers the primary operation end to end. Minor gaps remain around batch processing and explicit output-format/schema configuration, but agents can work around these via parameters.