PDFGate MCP Server vs North Dakota Code

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

PDFGate MCP Server logoPDFGate MCP ServerLegal · Local subprocess (stdio)MCP server for the PDFGate API. Generate PDFs, manage documents and handle e-signatures.61GoodAuth: api key requiredNorth Dakota Code logoNorth Dakota CodeLegal · Local subprocess (stdio)North Dakota Century Code — state statutes by citation and by topic.45FairAuth: no auth required

Verdict: choose PDFGate MCP Server for legal work as a local process; choose North Dakota Code for legal as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

PDFGate MCP Server logoChoose PDFGate MCP Server when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: PDFGATE_API_KEY.
  • You want tools like generate_pdf, upload_file, get_document.
Explore PDFGate MCP Server

North Dakota Code logoChoose North Dakota Code when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore North Dakota Code

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPDFGate MCP Server logoPDFGate MCP ServerNorth Dakota Code logoNorth Dakota Code
CategoryLegalLegal
Quality signal61/100 · Good45/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNo auth required
PricingBYOK (pay the provider)Free
Required env varsPDFGATE_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 5 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools24Not listed

Tools & capabilities

PDFGate MCP Server tools 24

  • generate_pdfGenerate a PDF from a URL or raw HTML. Provide either 'url' or 'html', not both.
  • upload_fileUpload a PDF to PDFGate so it can be referenced by other operations. Provide either 'filePath' (local path) or 'url'.
  • get_documentRetrieve metadata for a stored PDFGate document by its ID.
  • delete_documentDelete a PDFGate document.
  • flatten_pdfFlatten an interactive PDF into a static, non-editable PDF. Creates a new document; does not overwrite the original.
  • extract_form_dataExtract form field values from a fillable PDF. Returns a JSON object mapping field names to their values.
  • add_form_fieldsAdd interactive form fields to a stored PDF — from placeholder tags (refined via fieldOverrides) and/or explicitly positioned fields.
  • compress_pdfCompress/optimise a PDF to reduce file size without changing visual content.
  • protect_pdfEncrypt a PDF with a password and optional permission restrictions. Produces a new document; the original is unchanged.
  • watermark_pdfApply a text or image watermark to a PDF. For type='text' provide 'text'; for type='image' provide 'watermarkImagePath'.
  • download_fileDownload the raw PDF bytes of a stored document, returned as an embedded resource. For a shareable link instead, use get_document.
  • create_envelopeCreate a signing envelope from one or more existing PDFGate documents. Each recipient is given either as email and name or as the recipientId of a stored recipient. Recipients marked embedded sign inside your application via create_embed_link and receive no emails. Use signingOrder to make recipients sign in sequence. Returns an envelope in 'created' status; call send_envelope to dispatch signing emails.
  • +12 more on the listing page

North Dakota Code 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.

PDFGate MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-server-37": {
      "command": "npx",
      "args": [
        "-y",
        "@pdfgate/mcp-server"
      ],
      "env": {
        "PDFGATE_API_KEY": "YOUR_PDFGATE_API_KEY_HERE"
      }
    }
  }
}

North Dakota Code

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "north-dakota-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-north-dakota-code"
      ]
    }
  }
}

Frequently asked questions

PDFGate MCP Server is categorized under Legal and uses a local stdio subprocess. North Dakota Code belongs to Legal and uses a local stdio subprocess. Pick PDFGate MCP Server for legal work and North Dakota Code for legal.

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.

PDFGate MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. North Dakota Code 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 mcp-server-37 and north-dakota-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, PDFGate MCP Server has a quality signal of 61/100 (Good) with 5 views, 0 installs and 0 GitHub stars. North Dakota Code has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.