Integration

Softr integration

Softr is a no-code builder for web apps and client portals with its own built-in database (Softr Databases). Manage the database: list, read, create, rename and delete databases and tables, read a table's views, add, read, change and delete fields, and list, search (filter, sort, page), read, create, update and delete records. Manage the users of a published Softr app: create a user, delete one, send an invitation email, and sync users from the app's user source. Records and app users hold whatever personal data your app stores. Not exposed: deactivating and reactivating app users, generating magic login links, on their own or when creating a user (a magic link is a login credential, and the answer carrying it is undocumented) and validating a user's session token (called on the app's own domain). Authentication is a Personal Access Token created in the Softr dashboard under the workspace's API tokens, sent in the Softr-Api-Key header; app user tools also take the app's domain.

Connect Softr How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Softr.Built from the 25 Softr tools below, on the connection you add once.

What you can do with Softr

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Database, 5 operations

create_databaseCreate databasePOSTCreates a database in a workspace the token can access. Answers the new database with its id.
delete_databaseDelete databaseDELETEDeletes a database by id. Only an empty database is deleted unless force is true, which also deletes its tables and records.
get_databaseGet databaseGETReturns one database by id: name, description, workspace id, number of tables and dates.
list_databasesList databasesGETLists the Softr databases the token can access (in its authorized workspaces), each with its id, name, description, workspace id and number of tables.
update_databaseUpdate databasePUTRenames a database or changes its description. Softr does not document whether a value left out is kept or cleared, so send both name and description. Answers the updated database.

Record, 5 operations

create_recordCreate recordPOSTCreates a record in a table from a map of field ids to values (get_table lists the field ids). Answers the new record with its id.
delete_recordDelete recordDELETEDeletes a record (row) from a table by id. Cannot be undone.
get_recordGet recordGETReturns one record by id with its values, keyed by field id or, with fieldNames=true, by field name.
list_recordsList recordsGETLists the records of a table, a page at a time (offset and limit, at most 200 per page), optionally only those of one view. Each record's values are keyed by field id, or by field name with fieldNames=true.
update_recordUpdate recordPATCHPartially updates a record: only the fields sent change. Values are keyed by field ID. Answers the updated record.

Table, 5 operations

create_tableCreate tablePOSTCreates a table in a database, optionally naming its primary field and declaring its first fields. Answers the new table with its field ids.
delete_tableDelete tableDELETEDeletes a table by id. Only an empty table is deleted unless force is true, which also deletes its records.
get_tableGet tableGETReturns one table by id with its fields (id, name, type, options, read-only and required flags), primary field and default view. Use it to find the field ids that records are keyed by.
list_tablesList tablesGETLists the tables of a database, each with its fields (id, name, type, options), primary field and default view.
update_tableUpdate tablePUTChanges a table's name, its description, or both (Softr accepts either alone). Fields are changed with update_table_field. Answers the updated table.

App user, 4 operations

create_app_userCreate app userPOSTCreates a user in a published Softr app (identified by its domain) with a full name, an email and an optional password; Softr generates a password when none is given. The name and email are the person's personal data.
delete_app_userDelete app userDELETEDeletes a user, by email, from a published Softr app, with the personal data Softr holds on them. Cannot be undone.
invite_app_userInvite app userPOSTSends an invitation email to an existing user, by email, of a published Softr app; the user's status becomes Invited. The email is delivered to that person. The app must be published.
sync_app_usersSync app usersPOSTSyncs users of a published Softr app from its user data source: the listed emails, or every user when no email is sent.

Field, 4 operations

add_table_fieldAdd table fieldPOSTAdds a field (column) to a table with a name, a type and type-specific options (choices of a SELECT, currency, date format and so on). Answers the new field with its id.
delete_table_fieldDelete table fieldDELETEDeletes a field (column) from a table, together with the values every record held in it.
get_table_fieldGet table fieldGETReturns one field of a table by id: name, type, options, AI fill settings, and its read-only, required and locked flags.
update_table_fieldUpdate table fieldPUTChanges a field's name, type or type-specific options. Softr does not document whether a property left out is kept, so send the full options object you want, not only the changed part. Answers the updated field.

Search, 1 operation

search_recordsSearch recordsPOSTSearches the records of a table with a filter condition (IS, CONTAINS, GREATER_THAN, IS_ONE_OF, IS_EMPTY, IS_BETWEEN and more, nestable with AND and OR), sorting and paging. Conditions name fields by id.

View, 1 operation

list_table_viewsList table viewsGETLists the views of a table with their id and name. A view id filters list_records to that view.

Use Softr from Claude Code, Cursor or Codex

Connect Softr in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Softr operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Softr

Create your workspace
Sign up free. Nothing to install.
Connect Softr once
Add your Softr connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.