mcp-baserow-schema
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BASEROW_API_URL | Yes | The URL of your Baserow instance (e.g., https://your-baserow-instance.com). | |
| BASEROW_PASSWORD | Yes | Your Baserow account password. | |
| BASEROW_USERNAME | Yes | Your Baserow account email. | |
| BASEROW_TOTP_SECRET | Yes | Your Baserow TOTP secret in base32 format. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_databasesA | List all databases (applications) in a workspace. Returns database id, name, and type. Use workspace_id=1 for the default workspace. |
| list_tablesA | List all tables in a database. Returns table id, name, order, and other metadata. |
| create_tableB | Create a new table in a database. Optionally provide initial data rows. |
| delete_tableA | Delete a table by ID. This action is irreversible and will delete all fields and rows. |
| list_fieldsA | List all fields (columns) in a table with their types and options. |
| create_fieldA | Create a new field (column) in a table. The 'type' parameter must be one of: text, long_text, url, email, number, rating, boolean, date, last_modified, last_modified_by, created_on, created_by, duration, link_row, file, single_select, multiple_select, phone_number, formula, count, rollup, lookup, multiple_collaborators, uuid, autonumber, password, ai. |
| update_fieldB | Update an existing field's name, type, or type-specific options. |
| delete_fieldA | Delete a field (column) from a table. This will remove all data in that field. |
| list_rowsA | List rows from a table with pagination, search, and sorting. Returns field values using human-readable field names by default. |
| create_rowB | Create a new row in a table. Provide field values as a JSON object with field names as keys. Uses human-readable field names. |
| update_rowB | Update an existing row in a table. Provide the row ID and the field values to update. |
| delete_rowA | Delete a single row from a table by row ID. |
| batch_create_rowsA | Create multiple rows in a table at once (up to 200). Each item is a key-value object with field names. |
| batch_update_rowsA | Update multiple rows at once (up to 200). Each item must include an 'id' field with the row ID, plus any fields to update. |
| batch_delete_rowsA | Delete multiple rows at once (up to 200) by providing an array of row IDs. |
| auth_statusA | Check the current authentication state including email, user ID, and token expiry. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool targets a distinct resource (databases, tables, fields, rows, auth) with clear verb prefixes like list, create, update, delete. Batch operations are clearly variants of row operations, and auth_status is uniquely separated.
All tool names follow a consistent lowercase snake_case pattern with a verb_noun structure (e.g., list_databases, create_field, delete_row). The only outlier, auth_status, remains consistent in style and clearly indicates a status check.
With 16 tools, the set is slightly above the typical 3-15 range but each tool serves a clear purpose, covering databases, tables, fields, rows, and authentication. The batch operations add some redundancy but are justified for efficiency.
Rows and fields have full CRUD coverage, and tables have create/delete/list but no update operation (e.g., rename table). Databases are only listed, not managed, which is reasonable for a schema-focused server but leaves minor gaps.