Boxpdf vs Reactuse

A side-by-side look at the Boxpdf and Reactuse MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Boxpdf logoBoxpdfDeveloper Tools · Local subprocess (stdio)Resource-only MCP server with docs and templates for the boxpdf TypeScript PDF layout library.45FairAuth: not declaredReactuse logoReactuseDeveloper Tools · Local subprocess (stdio)MCP server for the ReactUse library — 110+ React Hooks (TypeScript-first, SSR-compatible, tree-shakable). Lets AI assistants discover hook signatures, demos, and usage patterns directly from the docs.63GoodAuth: no auth required

Verdict: choose Boxpdf for developer tools work as a local process; choose Reactuse for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Boxpdf logoChoose Boxpdf when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Boxpdf

Reactuse logoChoose Reactuse when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Reactuse

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBoxpdf logoBoxpdfReactuse logoReactuse
CategoryDeveloper ToolsDeveloper Tools
Quality signal45/100 · Fair63/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars181,065
Directory activity 0 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Boxpdf tools

No tool names declared yet. Check the project README from the listing page.

Reactuse tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Boxpdf

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "boxpdf": {
      "command": "npx",
      "args": [
        "-y",
        "boxpdf"
      ]
    }
  }
}

Reactuse

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "childrentime-reactuse": {
      "command": "npx",
      "args": [
        "-y",
        "@reactuses/mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Boxpdf is categorized under Developer Tools and uses a local stdio subprocess. Reactuse belongs to Developer Tools and uses a local stdio subprocess. Pick Boxpdf for developer tools work and Reactuse for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Boxpdf has no declared pricing — check the project's own site. Reactuse is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add boxpdf and childrentime-reactuse as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Boxpdf has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 18 GitHub stars. Reactuse has 63/100 (Good) with 4 views, 0 installs and 1,065 GitHub stars.