JSONPad documentation

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 电脑或云端
• 传输方式: stdio, Streamable HTTP
• 分类: 开发者工具

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接
• npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

https://mcp.jsonpad.io/docs

{
  "mcpServers": {
    "docs": {
      "command": "npx",
      "args": [
        "-y",
        "@basementuniverse/jsonpad-docs-mcp"
      ]
    }
  }
}

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

claude mcp add docs -- npx -y @basementuniverse/jsonpad-docs-mcp

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

{
  "mcpServers": {
    "docs": {
      "command": "npx",
      "args": [
        "-y",
        "@basementuniverse/jsonpad-docs-mcp"
      ]
    }
  }
}

{
  "servers": {
    "docs": {
      "type": "http",
      "url": "https://mcp.jsonpad.io/docs"
    }
  }
}

{
  "servers": {
    "docs": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@basementuniverse/jsonpad-docs-mcp"
      ]
    }
  }
}

https://mcp.jsonpad.io/docs

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月8日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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 c

• 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

• list_docs

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

• 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.

• 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/

• 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.

• 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.

• 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".

• 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 milli

• 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 dat

• 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,

• 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

• 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 c

• 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 "*").

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（jsonpad.io）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 234 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 14 个工具描述，未发现针对 AI 的隐藏指令

与“开发者工具”中的其他服务器比较i

• 星标数多于此分类中其他 5558 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 5558 个服务器的 47% 更新
• 基础检查结果等于或优于此分类中其他 5558 个服务器的 22%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README