mcp-baserow-schema
Related Servers
Alternatives to mcp-baserow-schema
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables natural language interaction with Baserow databases, supporting workspace, database, table, and row operations with authentication and batch capabilities.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with PostgreSQL and Supabase databases through natural language. Supports secure database operations including queries, migrations, and schema management with user-provided credentials.8 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables comprehensive interaction with Airtable bases including record management with automatic type conversion for all field types. It supports batch operations, schema discovery, and secure authentication using Personal Access Tokens.10 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables remote access to Baserow workspaces over Streamable HTTP, allowing discovery of accessible tables and creation of rows using user-facing field names.MIT
- AlicenseNot gradedqualityDmaintenanceProvides full MCP integration with a self-hosted NocoDB instance, enabling LLMs to create, update, and delete bases, tables, fields, views, and records via 25 MCP tools.42 npm1MIT
- AlicenseAqualityDmaintenanceParses Mermaid ER diagrams to create PostgreSQL tables and automatically generates REST and GraphQL CRUD APIs.12MIT
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.