JSONPad documentation MCP Server

by jsonpad Your server? Claim it

answering

JSONPad documentation is answering right now. Last checked 8 min ago. 39 installs a week from npm. It exposes 14 tools.

JSONPad docs, API, SDK and CLI references, and offline checkers for write rules and flows.

Installs per day peak 72 · avg 5 · -54% w/w

a month agotoday

Uptime history 11 days of history

11 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

374 ms

Response time

average over 24h

Installs / week

npm and PyPI

What the code does

We have not read this server's code yet · tools taken from the live server

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

Claims local-only, but ships network tools get_api_endpoint, list_api_endpoints

заявлено «локально, без передачи данных», но есть get_api_endpoint

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch JSONPad documentation and you get told the day something new turns up.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add docs --transport http https://mcp.jsonpad.io/docs

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "docs": {
      "url": "https://mcp.jsonpad.io/docs"
    }
  }
}

~/.codex/config.toml

[mcp_servers.docs]
url = "https://mcp.jsonpad.io/docs"

.cursor/mcp.json

{
  "mcpServers": {
    "docs": {
      "url": "https://mcp.jsonpad.io/docs"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "docs": {
      "url": "https://mcp.jsonpad.io/docs"
    }
  }
}

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

api

get_api_endpoint

The full contract of one REST API endpoint: parameters, headers, request body, responses and examples, and the JavaScript SDK method that calls it. Find it by id (the docs page slug, e.g. "item-restore"), by method and path (templates or concrete paths both work: "/lists/my-list/items/abc"), or by a description.

list_api_endpoints

List the REST API endpoints an API token can use, as method, path and title. Get one in full with get_api_endpoint.

docs

list_docs

List the documentation pages by section, with a description of each: the table of contents.

search_docs

Search the JSONPad documentation, the JavaScript SDK references and the command line tool reference. Returns the best-matching sections with a snippet and their jsonpad.io URL; read one with read_doc. Exact identifiers work well: error codes and names, headers, SDK methods, CLI commands, $jsonpad-var variables, "POST /lists/{listId}/items".

validate

validate_sync_document

Check a schema sync document (sync-v1) as far as possible without an account: against the JSON schema the API uses, the API's rules for keys and indexes, and every rule set and flow in it with their tests. Documents that reference files (rulesFile, flowFile and their tests) are checked too if the files' contents are given in files. What a sync would change needs the account: the API server's plan_schema_sync, or jsonpad sync-schema --dry-run.

validate_token_permissions

Check an API token's permission rules against the schema the API uses, say which rule shape a broken one was meant to be, and warn about valid rules that probably don't do what was meant (rule order, restore without view, sync-schema alone, allow "*").

cli

get_cli_command

The usage, arguments and options of a jsonpad command line tool (@basementuniverse/jsonpad-cli) command, and whether it works offline. Find it by name ("rules test", "jsonpad sync-schema --dry-run") or by what it does.

doc

read_doc

Read a documentation page as markdown, or one section of it. Give a page slug ("indexing"), a /docs path, a jsonpad.io URL (with or without .md, and with an optional #anchor), "sdk/jsonpad-sdk", "sdk/jsonpad-realtime-sdk", "cli/reference" or "cli/readme". Long pages are cut at a section boundary; read on with the returned nextSection.

eval

eval_write_rule

Check one write against a rule set, as the API would, and say whether it would be allowed, denied (403) or failed (400), which statement decided it, and (with trace) what every expression evaluated to. The write is shaped like a rule test case: action, identity, token, old, new, patch, merge, now. Costs nothing and sees no data.

flow

check_flow

Compile a flow document (flows-v1) with the same engine the API uses, and run its tests (flow-tests-v1) against in-memory data. Returns diagnostics (with JSON pointers into the document), what the flow reads and writes, and why each failing test failed. Costs nothing and sees no data.

lookup

lookup_error

What a JSONPad API error code means, its HTTP status, and the guides that explain it. Give the numeric code (10013) or the name (QUOTA_EXCEEDED), as found in an error response's "code" and "name".

plan

get_plan_limits

The limits of each public plan (Free, Indie, Pro, Scale): requests per month and minute, the minimum gap between requests, storage, item size, versions kept, tokens, identities, realtime connections, webhooks and flows. null means unlimited. Sizes are in bytes, rateLimit in milliseconds, prices in GBP.

rules

check_write_rules

Compile a list's write rules with the same engine the API uses, and run their tests (a rules-tests-v1 document). Returns every diagnostic with its line and column, and for each failing test what it expected, what happened, and how each rule came out. Costs nothing and sees no data: lookups find the test document's items. Use it before saving rules.

sdk

get_sdk_method

The signature, description and example of a method in the JavaScript SDK (@basementuniverse/jsonpad-sdk) or the realtime SDK, and the REST endpoint it calls. Find it by name ("restoreItem") or by what it does.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.jsonpad.io/docs	streamable-http	answering	343 ms	8 min ago

Alternatives to JSONPad documentation

same job, measured the same way

Qiskit Documentation MCP Server

by qiskit

MCP server for querying and retrieving Qiskit documentation, guides, and API references

469 installs/wk local only

Docs MCP

by redpanda

Get authoritative answers about Redpanda documentation and search API references.

5 tools answering

Gemmein

by gemmein

Gemmein docs, API reference, error explainers and a live integration check for coding agents.

1 037 installs/wk local only

SiteGPT Docs

by sitegpt

Search the SiteGPT documentation: setup, features, API reference, troubleshooting.

3 tools answering

ConnectIQ MCP Server

by deugene

MCP server for Garmin ConnectIQ SDK documentation and resources

51 installs/wk local only

Ignite UI MCP Server

by igniteui

Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding

711 installs/wk local only

Unswell

by stokaro

Offline self-checking to reduce AI-style wording in source code and documentation.

local only

OpenDocs

by opendocs

Write, organize and publish documentation sites, help centers and SOPs on OpenDocs.cloud.

answering

JSONPad documentation — questions

Answers built from our own checks of this server.

What can JSONPad documentation do?

It exposes 14 tools, read directly from the server on our last check. Among them: check_flow, check_write_rules, eval_write_rule, get_api_endpoint, get_cli_command, get_plan_limits and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is JSONPad documentation mostly used for?

Its tools cluster around api, validate and docs. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is JSONPad documentation working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 374 ms. The bar chart above shows every period we have measured.

How do I connect JSONPad documentation?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does JSONPad documentation need an API key?

No. JSONPad documentation completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is JSONPad documentation?

It answers our handshake in 374 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use JSONPad documentation?

The npm package @basementuniverse/jsonpad-docs-mcp was installed 39 times in the last week. Week over week that is -54%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.