JSONPad
io.jsonpadv0.1.0Updated Oct 2, 2026
Build and run a JSONPad backend: lists, items, indexes, write rules, schema sync, history, flows.
Overview
AI-generated overview
Lets an assistant build and manage a JSONPad backend: lists, items, indexes, write rules, schema sync, history, and flows.
- What it does
- Connects an assistant to JSONPad so it can create and operate a JSON backend. Tools are grouped into toolsets: lists, items, indexes, history, rules, schema (the defaults), plus flows and identities. It can read and write data, manage indexes and write rules, sync schemas, and inspect history.
- When to use it
- Useful when you want an assistant to set up or maintain a JSONPad-backed API without leaving the chat: defining lists and schemas, adding or editing items, tuning indexes and rules, or reviewing history and flows.
- Requirements
- A JSONPad account and an API token, supplied as the JSONPAD_API_TOKEN environment variable or as an Authorization bearer header. The remote endpoint at mcp.jsonpad.io can also connect via OAuth without a token. The npm package @basementuniverse/jsonpad-mcp runs locally over stdio and needs Node.js.
Before you install
The token is a secret credential; keep it out of shared configuration. Tools can create, change, and delete lists, items, indexes, rules, and schemas, so set JSONPAD_READ_ONLY=true to register only non-mutating tools when you just want to inspect. Restrict JSONPAD_TOOLSETS to limit which capabilities are exposed.
Installation
In SourceWeft
- Open JSONPad in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"api": {
"type": "http",
"url": "https://mcp.jsonpad.io/api"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v0.1.0LatestOct 2, 2026
