npm @parserelay/mcpstdioupdated 2mo ago
ParseRelay's scan operation as an MCP tool ā so any MCP host (Claude Desktop, Cursor, ā¦) can parse a document into structured, confidence-scored fields. Same contract as the REST API and the component; one tool, scan.
What can you do with ParseRelay?
@parserelay/mcp
ParseRelay's scan operation as an MCP tool ā so any
MCP host (Claude Desktop, Cursor, ā¦) can parse a document into structured, confidence-scored
fields. Same contract as the REST API and the <DeadSimpleMicroScanner> component; one tool,
scan.
The scan tool
Input mirrors the sync ScanRequest ā image (required), plus
schema, doc_type, engine, ocr, dry_run, model, model_key. (relay webhooks are
omitted: a tool call is synchronous, so you get the envelope back inline.) The result is the
full ScanEnvelope as JSON: fields, per-field confidence,
needs_review, field_source, and meta (engine, credits, tokens).
Set dry_run: true to preview which fields would trigger a paid rescue ā and the estimated
credits ā without spending anything.
Run it
stdio (Claude Desktop, Cursor)
{
"mcpServers": {
"parserelay": {
"command": "npx",
"args": ["-y", "@parserelay/mcp"],
"env": {
"PARSERELAY_API_KEY": "your-key",
"PARSERELAY_BASE_URL": "https://api.parserelay.app" // optional
}
}
}
}
streamable-HTTP (remote / hosted)
PARSERELAY_API_KEY=your-key PORT=8080 node node_modules/@parserelay/mcp/dist/http.js
# ā POST http://localhost:8080/mcp
Stateless: a fresh server per request, so it scales horizontally. Auth per request via
Authorization: Bearer <key>, falling back to PARSERELAY_API_KEY for single-tenant setups.
Programmatic
import { createMcpServer } from "@parserelay/mcp";
import { ParseRelayClient } from "@parserelay/client";
const server = createMcpServer(new ParseRelayClient({ apiKey }));
// then wire your own transport: await server.connect(transport)
Config
| Env var | Required | Default | Notes |
|---|---|---|---|
PARSERELAY_API_KEY |
stdio: yes | ā | HTTP can override per request via Authorization: Bearer. |
PARSERELAY_BASE_URL |
no | https://api.parserelay.app |
Point at a local worker for testing. |
PORT |
no | 8080 |
HTTP transport only. |
Install
Add ParseRelay to your client. Pick the one you use.
claude mcp add mcp -- npx -y @parserelay/mcpcodex mcp add mcp -- npx -y @parserelay/mcpamp mcp add mcp -- npx -y @parserelay/mcp{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@parserelay/mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@parserelay/mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"mcp","command":"npx","args":["-y","@parserelay/mcp"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@parserelay/mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@parserelay/mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@parserelay/mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"mcp": {
"type": "local",
"command": "npx",
"args": [
"-y",
"@parserelay/mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"mcp": {
"command": {
"path": "npx",
"args": [
"-y",
"@parserelay/mcp"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y @parserelay/mcpRun `goose configure`, choose **Add Extension ā Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation22/25
- Maintenance16/25
- Trust6/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 77 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint ā no local install
Version history
| Versions | Published |
|---|---|
| 0.1.1Latest | Jun 15, 2026 |