Quickbase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging (true/false, default: false) | false |
| LOG_LEVEL | No | Logging level (DEBUG/INFO/WARN/ERROR, default: INFO) | INFO |
| QUICKBASE_APP_ID | No | Default application ID | |
| QUICKBASE_CACHE_TTL | No | Cache duration in seconds (default: 3600) | 3600 |
| QUICKBASE_REALM_HOST | Yes | Your Quickbase realm (e.g., company.quickbase.com) | |
| QUICKBASE_USER_TOKEN | Yes | Your Quickbase API token | |
| QUICKBASE_CACHE_ENABLED | No | Enable caching (true/false, default: true) | true |
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 |
|---|---|
| check_configurationC | Check if Quickbase configuration is properly set up |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'check_configuration' has a single, clear purpose that cannot be confused with any other tool in the set.
The tool name 'check_configuration' follows a consistent verb_noun pattern. Since there is only one tool, there is no inconsistency in naming conventions to evaluate.
A single tool is too few for a server named 'Quickbase MCP Server', which implies broader functionality for interacting with Quickbase (e.g., CRUD operations on records, tables, or apps). This minimal set feels incomplete and under-scoped for the apparent domain.
The tool set is severely incomplete for a Quickbase integration server. It only provides a configuration check, lacking any operations to create, read, update, or delete data, manage tables or apps, or perform other core Quickbase workflows, leaving significant gaps that will cause agent failures.