JSONPad docs, API, SDK and CLI references, and offline checkers for write rules and flows.
Scored across 14 tools
Each tool targets a distinct purpose: doc discovery (list_docs/search_docs/read_doc), targeted accessors (get_api_endpoint/get_sdk_method/get_cli_command/get_plan_limits/lookup_error), and document validators (check_flow/check_write_rules/eval_write_rule/validate_sync_document/validate_token_permissions). The only mild overlap is that read_doc can also read sdk/cli pages that get_sdk_method and get_cli_command serve, but the descriptions clearly delineate targeted lookup versus full-page reading.
Every name follows a clean verb_noun snake_case pattern: check_*, eval_*, get_*, list_*, lookup_*, read_doc, search_docs, validate_*. No mixed conventions or ambiguous verbs.
14 tools sit right in the well-scoped sweet spot, and each earns its place by covering a distinct doc category or validation type. Nothing feels redundant or padded.
The surface comprehensively covers documentation discovery, API/SDK/CLI reference, error codes, plan limits, and local validation of flows, rules, sync documents and token permissions. Minor gaps exist (e.g. no dedicated quickstart/getting-started accessor), but read_doc covers those pages as a workaround.
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.
Inputs: flow (required), tests, knownLists. Returns: ok, diagnostics
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.
Inputs: rules (required), tests, knownLists. Returns: ok, diagnostics
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.
Inputs: rules (required), write (required), items, trace, +1 more. Returns: ok
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.
Inputs: id, path, query, method. Returns: endpoint
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.
Inputs: name, query. Returns: command
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.
Inputs: plan, limit. Returns: plans
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.
Inputs: name, query, package. Returns: method
List the REST API endpoints an API token can use, as method, path and title. Get one in full with get_api_endpoint.
Inputs: resource. Returns: endpoints
List the documentation pages by section, with a description of each: the table of contents.
Inputs: section. Returns: sections
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".
Inputs: code, name. Returns: error
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.
Inputs: page (required), section, maxChars. Returns: url, title, markdown, truncated
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".
Inputs: query (required), limit, section. Returns: results
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.
Inputs: document (required), files. Returns: ok, problems
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 "*").
Inputs: permissions (required). Returns: ok
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Build and run a JSONPad backend: lists, items, indexes, write rules, schema sync, history, flows.
Write, organize and publish documentation sites, help centers and SOPs on OpenDocs.cloud.
Claspine docs, API reference and code checks for AI agents: guides, recipes, errors, upgrades.
Create, validate, edit, export (markdown/svg/png/mermaid), and search JSON Canvas files.
Add one secure layer between your agents and this server.