get-schema and get-perms hand back the current state — and, if you do not have the local files yet, how to produce them — while push-schema and push-perms send the edited versions up. Because query and transact run against the live app, a schema change can be checked with a real query instead of an assurance that it worked.
A wrapper around the Instant Platform SDK. It works against one of your InstantDB apps by id — reading and pushing schema and permissions, and running queries and transactions against the live data.
- An app's schema fetched by app id, and local instant.schema.ts changes pushed back up — get-schema, push-schema
- The same round trip for permissions, through instant.perms.ts — get-perms, push-perms
- InstaQL queries run against an app and returned as JSON, including where clauses and nested relations — query
- Transactions in the platform's step format — update, link and unlink — transact
- An orientation tool for a model that has no context on InstantDB yet — learn
A personal access token from your Instant dashboard. Instant hosts the server at https://mcp.instantdb.com — /mcp for clients that speak Streamable HTTP, /sse for older ones. To run it yourself instead: npx -y @instantdb/mcp --token <token>, or put the token in INSTANT_ACCESS_TOKEN. Every tool except learn takes an appId.
One command plus a key — npx -y @instantdb/mcp --token <token>, then supply credentials