QuickBase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging (set to quickbase-mcp:* for all logs) | |
| QB_REALM | Yes | Your QuickBase realm hostname (e.g., seanngates.quickbase.com) | |
| QB_APP_ID | Yes | The QuickBase application ID to connect to | |
| QB_USER_TOKEN | Yes | Your QuickBase user token for authentication | |
| QB_MAX_RETRIES | No | Maximum number of retry attempts for failed API requests | 3 |
| MCP_SERVER_NAME | No | The name of the MCP server | quickbase-mcp |
| MCP_SERVER_VERSION | No | The version of the MCP server | 1.0.0 |
| QB_DEFAULT_TIMEOUT | No | Default timeout for QuickBase API requests in milliseconds | 30000 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quickbase_get_app_infoC | Get information about the QuickBase application |
| quickbase_get_tablesB | Get list of all tables in the application |
| quickbase_test_connectionB | Test connection to QuickBase |
| quickbase_create_tableC | Create a new table in QuickBase |
| quickbase_get_table_infoC | Get detailed information about a specific table |
| quickbase_delete_tableC | Delete a table from QuickBase |
| quickbase_get_table_fieldsC | Get all fields for a table |
| quickbase_create_fieldC | Create a new field in a table |
| quickbase_update_fieldC | Update an existing field |
| quickbase_delete_fieldC | Delete a field from a table |
| quickbase_query_recordsC | Query records from a table with optional filtering and sorting |
| quickbase_get_recordC | Get a specific record by ID |
| quickbase_create_recordC | Create a new record in a table |
| quickbase_update_recordC | Update an existing record |
| quickbase_delete_recordC | Delete a record from a table |
| quickbase_bulk_create_recordsC | Create multiple records at once |
| quickbase_search_recordsC | Search for records containing specific text |
| quickbase_create_relationshipC | Create a parent-child relationship between tables |
| quickbase_get_relationshipsC | Get relationships for a table |
| quickbase_get_reportsC | Get all reports for a table |
| quickbase_run_reportC | Run a specific report |
| quickbase_create_advanced_relationshipC | Create a comprehensive table relationship with automatic lookup fields |
| quickbase_create_lookup_fieldC | Create a lookup field to pull data from a related table |
| quickbase_validate_relationshipC | Validate the integrity of a table relationship |
| quickbase_get_relationship_detailsB | Get detailed information about table relationships including lookup fields |
| quickbase_create_junction_tableC | Create a junction table for many-to-many relationships |
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 26 tools
Every tool has a clearly distinct purpose targeting specific QuickBase operations like table/field/record management, relationships, queries, and app info. No ambiguity exists between tools—each name precisely indicates its function (e.g., quickbase_create_field vs. quickbase_update_field).
All tools follow a perfect verb_noun pattern with the 'quickbase_' prefix, using consistent snake_case throughout (e.g., quickbase_create_table, quickbase_get_record). The naming is highly predictable and readable across all 26 tools.
With 26 tools, the count is borderline heavy for a single server, though QuickBase's complexity as a database platform justifies many operations. It feels comprehensive but could overwhelm agents; a more modular approach might improve scoping.
The toolset provides complete CRUD/lifecycle coverage for QuickBase's domain, including tables, fields, records, relationships, queries, reports, and app info. No obvious gaps exist—agents can perform all essential operations without dead ends.