Softr
Build custom apps and portals from Airtable in minutes with no-code. Softr provides user management and database APIs for building client portals, internal tools, and web applications.
Verdict
Common use cases
- Prototype a customer directory during design reviews
- Track bug reports in a custom table
- Bulk-add records from a CSV discussion
- Archive old databases after project wrap-up
- Spin up event registration tables on demand
Integration
- Vendor
- Softr
- Category
- other
- Auth
- API_KEY
- Tools
- 22
- Composio slug
softr
Tools
- Create Database
Tool to create a new database in a Softr workspace. Use when you need to set up a new database for storing data within a specific Softr workspace.
- Create Record
Creates a new record in a Softr database table. Use when you need to add new data to a specific table in your Softr database.
- Create Table
Tool to create a new table within a specified Softr database. Use when you need to add a new data structure with custom fields to organize information.
- Create Table Field
Tool to add a new field to a Softr table. Use when you need to add a new column to an existing table, such as adding an email field, a text field, or any other field type to store additional data.
- Delete databasedestructive
Tool to delete a specific database by its ID from Softr. Use when you need to remove a database. The database must be empty unless the 'force' parameter is set to true. This operation is irreversible.
- Delete Recorddestructive
Tool to delete a record from a Softr database table. Use when you need to permanently remove a specific record.
- Delete Tabledestructive
Tool to delete a specific table by its ID from a database. Use when you need to remove a table. The table must be empty unless the force parameter is set to true.
- Delete Table Fielddestructive
Tool to delete a field from a Softr database table. Use when you need to remove a field from a table. Returns success confirmation upon completion.
- Get Database
Tool to retrieve details for a specific database by ID. Use when you need to fetch information about a particular database in Softr.
- Get Databases
Tool to retrieve all databases available in the workspace. Use when you need to list or discover available databases for further operations.
- Get Record
Tool to retrieve a single record by its ID from a Softr database table. Use when you need to fetch detailed information about a specific record.
- Get records from table
Tool to retrieve a paginated list of records from a Softr table. Use when you need to fetch records from a specific table with optional pagination parameters.
- Get Table
Tool to retrieve details for a specific table by ID. Use when you need to inspect table structure, fields, or metadata.
- Get Table Field
Tool to retrieve a specific field from a Softr table by field ID. Use when you need detailed configuration information about a table field, including its type, options, and metadata.
- Get Table Fields
Tool to retrieve all fields for a specific table in a Softr database. Returns comprehensive field information including id, name, type, options, and metadata. Use when you need to inspect or work with table structure.
- Get Tables
Retrieves all tables within a specified Softr database. Use when you need to list or explore the tables available in a database.
- Get Table Views
Tool to retrieve all views for a specified table in a Softr database. Use when you need to list or inspect available views for a table.
- Search Records
Tool to search records in a Softr database table with filtering and pagination. Use when you need to retrieve records from a specific table, optionally filtered by field values and paginated for large result sets.
- Update a record
Tool to update an existing record's field values in a Softr table. Use when you need to modify specific fields of a record by providing the database ID, table ID, record ID, and the new field values.
- Update Database
Tool to update an existing database's name and/or description. Use when you need to modify database metadata after creation.
- Update Table
Tool to update a table's name and/or description in Softr Database. Use when you need to modify table metadata. To modify fields, use the field-specific endpoints instead.
- Update table field
Updates an existing field in a Softr table. Use when you need to modify a field's name, type, or configuration options. Note: The API requires both 'type' and 'options' fields even if only updating the name.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Softr and click Connect. 3. Log into your Softr account, go to Settings > API, and generate a new API key with read and write permissions for databases, tables, and records. 4. Paste the key into Switchy's connection dialog and click Authorize. 5. Return to any Space and type '@Softr list my databases' to confirm the connection works. 6. If you see your workspace databases listed, the integration is live. 7. To invoke a tool, @mention Softr in a message and describe what you want — for example, '@Softr create a table called Leads with fields for name, email, and status'. 8. Switchy will call the appropriate tool and show the result inline. 9. Keep your API key scoped to a single workspace to avoid accidental cross-workspace changes.
What teammates see: by default, memories from Softr are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Build Event RSVP Table
@Softr create a database called 'Q2 Events', then add a table named 'Registrations' with fields for full name, email, company, and attendance status.Open in a Space →
Add Customer Records
@Softr add three records to the Leads table: Alice Chen at alice@example.com status New, Bob Martinez at bob@example.com status Contacted, and Carol Wu at carol@example.com status Qualified.Open in a Space →
Expand Table Schema
@Softr add a 'referral source' text field to the Leads table so we can track where each lead came from.Open in a Space →
Clean Up Test Data
@Softr delete record ID rec_abc123 from the Registrations table — it was a test entry we no longer need.Open in a Space →
Archive Old Database
@Softr force-delete the database called 'Q1 Events' including all its tables and records — the project is complete and we've exported everything we need.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Softr list all tables in the 'Customer Portal' database and show me the field structure for each one
Found 4 tables in your Customer Portal database: 'Users' (8 fields: email, name, company, role, created_at, last_login, status, notes), 'Support Tickets' (6 fields: ticket_id, user_id, subject, description, priority, status), 'Invoices' (7 fields: invoice_number, user_id, amount, due_date, paid_date, status, pdf_url), and 'Feature Requests' (5 fields: title, description, votes, status, submitted_by). This illustrates how the MCP retrieves your Softr database schema for inspection or planning changes.
This read-heavy example shows the MCP's ability to surface database structure, useful before building new features or debugging data issues. Requires API key with read access to the workspace. Response shape depends on your actual table configuration—field types and counts will vary.
@Softr create a new table called 'Product Feedback' in the Customer Portal database with fields for title, description, user email, and submission date
Created table 'Product Feedback' (ID: tbl_9x4k2m) in Customer Portal database. Added 4 fields: 'title' (text, required), 'description' (long text), 'user_email' (email, required), 'submission_date' (date, auto-populated). Table is now live and ready to accept records. This example demonstrates the MCP's ability to provision new data structures on demand without touching the Softr UI.
This write example shows schema creation in action—useful when spinning up new workflows or extending an existing portal. Side-effect: the table exists immediately and can accept records. If you delete it later, use force=true if it contains data. API key must have write permissions.
@Softr pull all records from the Support Tickets table where status is 'open', then draft a summary email for our support lead highlighting the three highest-priority items
Retrieved 14 open tickets. Top 3 by priority: (1) 'Payment gateway timeout on checkout'—affects 12 users, submitted 2 days ago; (2) 'Mobile app crashes on iOS 17'—8 reports in last 24 hours; (3) 'Export feature missing data fields'—blocking 5 enterprise accounts. Draft email: 'Hi Sarah, we have 14 open tickets. Urgent attention needed on payment gateway issue (12 users impacted) and iOS crash (trending up). Export bug is blocking enterprise renewals. Let me know if you need the full ticket list.' This illustrates combining Softr data retrieval with AI reasoning for actionable insights.
This synthesis example pairs the MCP's record-fetching capability with the AI's summarization logic, turning raw database rows into a decision-ready brief. Useful for daily standups or triage. Note: the AI doesn't update ticket status—you'd need a separate '@Softr update record' prompt for that. Rate limits apply if querying large tables frequently.
Use-case deep-dives
When Softr MCP makes sense for custom client portals
A 6-person agency builds client portals in Softr—one per customer—and needs AI to sync intake form data into the right portal database without manual CSV uploads. The Softr MCP wins here because it exposes Create Record and Create Table tools that let the AI write directly to specific workspace databases via API key. The team prompts the AI with a client name and form payload; the AI creates the record in the correct table. This works cleanly for agencies managing 10-30 portals where each portal is a separate Softr workspace. If you're running a single multi-tenant app or need real-time webhooks, Softr's architecture isn't built for that—you'd want a headless CMS with event streams. For the agency use case, though, the MCP removes the export-import dance and keeps client data flowing into portals as soon as it arrives.
Softr MCP speeds up table design for non-technical builders
A solo founder prototyping a membership directory in Softr spends half their time clicking through the UI to add fields, rename columns, and restructure tables as the data model evolves. The Softr MCP's Create Table Field and Delete Table Field tools let the AI handle schema changes from a prompt: 'add a LinkedIn URL field to the members table' or 'remove the deprecated phone_alt column'. This cuts iteration time from minutes to seconds and keeps the founder in their chat thread instead of context-switching to the Softr dashboard. The trade-off: if you're managing complex relational schemas with foreign keys and cascading deletes, Softr's flat-table model hits a wall—you'd migrate to Airtable or Postgres. For MVPs and directories under 5 tables, the MCP makes schema work feel like conversation instead of admin.
When Softr MCP handles teardown and archival at scale
A 4-person dev shop maintains 40+ Softr workspaces for past clients and needs to archive or delete databases when contracts end. Manually logging into each workspace to force-delete tables and databases takes an afternoon per quarter. The Softr MCP's Delete Database and Delete Table tools—with the force parameter—let the AI batch-delete empty or non-empty structures from a list of workspace IDs. The team prompts 'delete all databases in workspace X' and the AI handles the API calls. This works when you control the API keys and have a clear list of what to tear down. If you need audit trails or rollback, the MCP doesn't log deletions—you'd script it yourself or use Softr's activity feed. For agencies doing quarterly cleanup, the MCP turns a manual slog into a 10-minute AI task.
Frequently asked
What does the Softr MCP let me do in Switchy?
It gives your AI agents full control over Softr's database layer — creating databases, tables, fields, and records, plus deleting them. Think of it as programmatic access to the data backend that powers your Softr apps, so agents can build or modify data structures on the fly without touching the Softr UI.
Do I need admin access to connect Softr via API key?
Yes. The API key must have workspace-level permissions to create and delete databases, tables, and records. Softr doesn't offer granular scopes for API keys, so whoever connects it in Switchy needs full workspace admin rights. If you're on a team plan, coordinate with your workspace owner.
Can the MCP publish or edit Softr pages and blocks?
No. This integration only touches the database layer — the backend data structures. It can't modify page layouts, blocks, or any front-end design elements. If you need to change how a Softr app looks or behaves, you still do that in the Softr builder manually.
Why use this instead of editing Softr databases directly in the app?
Speed and automation. If your workflow involves spinning up new tables or bulk-creating records based on external data, an AI agent can do it in seconds without you clicking through the Softr UI. It's overkill for one-off edits, but powerful for repetitive data ops or integrating Softr into larger workflows.
Who on the team should connect the Softr MCP?
Whoever owns the Softr workspace and is comfortable giving Switchy delete permissions. The API key has no read-only mode, so the person connecting it needs to trust that agents won't accidentally wipe tables. Typically that's a technical lead or the person who manages your Softr account day-to-day.