Softr
Read and write records in a Softr app's own Database tables, manage its tables and users, over the Softr Database API and Studio Users API.
About
Softr ships in the w6w first-party pack. It declares 18 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.softr- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Databases · Spreadsheets · Productivity
Overview
Softr lets you build internal tools, client portals and websites on top of a data source — most often its own built-in Softr Database, a native multi-table store with fields, views and (optionally) AI-assisted columns.
This app covers the Softr Database API end to end: list and inspect databases, tables and views, then read, search, create, update and delete the records inside a table. Search supports Softr’s full filter grammar (binary/unary/ternary/composite conditions, relative date tokens), not just a flat equality match.
A second, separately-hosted surface — the Studio Users API — manages the people signed up to a published Softr app: create, delete, activate, deactivate and invite a user, generate a magic sign-in link, and trigger a user sync. It shares the same Personal Access Token as the Database API but talks to a different host and is scoped per-app by a domain header rather than by an app-scoped path.
One documented endpoint is deliberately not implemented: validating a Softr-issued user JWT (POST /v1/api/users/validate-token) is called against the Softr app’s own live domain — a value that varies per app and per customer rather than a fixed API host — so it cannot be reached through a static network allowlist. See the README for the full reasoning.
Build with Softr
Three routes to the same 18 actions. The Workflow tab is generated from Softr's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Table Views
table-views-list List the views defined on a table, for use with Get Records' viewId filter.
Deactivate User
user-deactivate Deactivate a user in a published Softr app. Deactivated users cannot log in and don't count toward the plan's user limit, but their record is retained.
Invite User
user-invite Send an invitation email to an existing user of a published Softr app. The app must be published for the invitation to be sent.
Generate Magic Link
user-magic-link-generate Generate a Magic Link sign-in for a user of a published Softr app.
Sync Users
user-sync Re-sync one, several, or (leave Emails empty) all users of a published Softr app.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Softr's real ids.
{
"manifestVersion": "2",
"name": "softr-example",
"steps": [
{
"id": "database-get",
"uses": {
"app": "io.w6w.softr",
"action": "database-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"databaseId": "<databaseId>"
}
}
]
}Here are some of the things you can do
-
Get Database
readdatabase-get -
List Databases
searchdatabase-list -
Create Record
performrecord-create -
Get Single Record
readrecord-get -
Get Records
searchrecord-list
+13 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Softr, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Softr. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "database-get",
payload: {
databaseId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action database-get --payload '{"databaseId":"<value>"}'Give an AI agent Softr — without giving it Softr's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.softr#database-get",
"input": {
"databaseId": "<databaseId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Softr connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Softr's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Softr itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Softr declares its own checks, so its health is a property of the app rather than something the host guesses at.