Best for
- Developers using Deno as their runtime who want reliable structured output for AI agents.
- Agent integrations that need to reduce token usage and avoid parsing terminal text.
P
Pare Deno
Community
Structured Deno runtime operations as typed JSON.
- Category
- Dev Tools #362 of 438
- Stars
- ★ 138 Popular
- Transport
- stdio (local process)
- Runtime
- Node.js >=20
- Credentials
- No credential needed
- License
- MIT
- Last commit
39FMRS · D
The Pare Deno server focuses on structured output for Deno runtime operations, providing typed JSON via MCP to reduce token consumption and avoid text parsing issues. It wraps only the Deno tool, making it suitable for agent scenarios that require reliable data sets.
Strongest · Maintenance 14/20 Weakest · Reliability 4/20
Why each score
- Reliability 4/20
- Only the manifest and README were supplied, with no source, tests, CI, or tool list for packages/server-deno. Server startup, MCP initialization handshake, and tool/behavior consistency cannot be verified; missing evidence lowers the score.
- Security and permissions 5/20
- No permission model, command execution boundary, confirmation mechanism, or data-flow disclosure for this server was supplied. As a Deno runtime wrapper it may execute arbitrary commands, yet there is no evidence of least-privilege scoping or dangerous-operation confirmation. No red-line issue was found, but the security posture is entirely opaque, so points are deducted.
- Maintenance 14/20
- The README and manifest show an MIT license, CI/codecov/npm/OpenSSF badges, and version 0.22.0, indicating an active repository. Deductions are made for the lack of per-server release evidence, dependency update trail, security-response channel, and the presence of 17 open issues.
- Documentation 7/20
- The README provides general installation, configuration, and troubleshooting guidance, and the manifest identifies the npm package, but no server-deno-specific tool parameters, output schemas, limitations, or examples were provided. The documentation gap for this specific server lowers the score.
- Setup experience 9/20
- The manifest provides the npm package identifier and stdio transport, and the README gives general npx and client configuration methods, making the install path plausible. Deductions are made for the absence of a deno-specific configuration example and the lack of verifiable execution evidence, with the static-review cap of 15 applied.
Static review · not runListed 2026-08-07
Read the FMRS scoring method →Fit and risk
What it can accessRuns commands or code
Not for
- Simple Deno interactions where structured output is not required.
- Projects using other runtimes (e.g., Node.js).
Required permissions
- System permissions to execute Deno commands.
- Access to files in the working directory (depending on the Deno commands run).
Risks and side effects
- Malicious or misconfigured Deno commands could cause system damage.
- Exposing too many tools without proper filtering could increase attack surface.
Setup
Before you start
Runtime：Node.js >=20
Other optional settings (2)
PARE_TOOLS
Universal tool filter across all Pare servers, formatted as server:tool pairs (e.g. 'git:status,npm:install'); takes precedence over per-server filters.
MCP_TIMEOUT
MCP connection timeout in milliseconds for Claude Code; set to 30000 if you hit connection timeouts.
Install the @paretools/deno package via npm and configure it in your MCP client with stdio transport. For example, in Claude Desktop's config, add something like "command": "npx", "args": ["-y", "@paretools/deno"].
Check that it works
After starting the client, confirm the tools registered by the Pare deno server (@paretools/deno, stdio transport) appear in the tool list; you can also run npx @paretools/init doctor to validate, then ask the agent to run a Deno command and check the reply is structured JSON rather than raw terminal text.
Troubleshooting
- Ensure Node.js version >= 20.
- If npx is not found, use `cmd /c npx` (Windows) or an absolute path.
- First start may be slow; pre-cache by running `npx -y @paretools/deno`.
- If MCP connection times out, increase client timeout settings (e.g., `MCP_TIMEOUT`).
Things to try
Once connected, you can ask your AI assistant things like:
- Run the Deno tests for this project via the Pare deno server and give me a JSON summary of passes and failures.
- Format this Deno project's code and tell me which files changed.
- Run deno lint and organize all warnings into a structured list.
- List the tasks defined in this project's Deno configuration.
Use cases
Execute Deno scripts in AI coding assistants and obtain structured results.
Automate Deno project tasks (like running tests or installing dependencies) and integrate into agent workflows.
Supported clients
Claude Desktop
Claude Code
Cursor
VS Code
Windsurf
Cline
Roo Code
Codex
Gemini CLI
Zed
Continue
Listed from the project's documentation, not tested by this site.
Overview
Pare Deno is an MCP server from the Pare toolkit that wraps the Deno CLI to return structured, schema-validated JSON instead of raw terminal text. This provides AI agents with predictable, typed data they can act on directly, avoiding fragile text parsing. The server is distributed via the npm package @paretools/deno, uses stdio transport, and conforms to the Model Context Protocol.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
More servers from this repository
Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method