Quickbase MCP Server
The Quickbase MCP Server enables AI assistants like Claude to interact with Quickbase databases through a comprehensive set of tools:
Connection & Configuration: Verify setup, test connections, and configure caching behavior and environment variables (realm, tokens, app IDs)
Application Management: Create and update Quickbase applications, list all tables within an application
Table Operations: Create/update tables and retrieve field information
Field Management: Create, retrieve, update, and delete fields within tables
Record Operations: Query records with filtering, sorting, and grouping; create or update single records; perform bulk creation and updates
File Operations: Upload and download file attachments to/from records
Relationship Management: Get, create, update, and delete table relationships
Reporting: Execute existing Quickbase reports
Requires Node.js 14 or higher as a prerequisite for running the MCP server that connects to the Quickbase API.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Quickbase MCP Serverquery all active customers from the Customers table"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Quickbase MCP Server
A TypeScript-based Model Context Protocol (MCP) server for Quickbase, designed for seamless integration with Claude Desktop and other AI assistants.
📋 Community Project Notice
This is a community-developed integration that is not an official Quickbase product. While it uses Quickbase's public APIs, it is not officially supported by Quickbase, Inc. This project is provided "as is" and maintained by the community. For official Quickbase products and support, please visit quickbase.com.
🚀 Quick Start for Claude Desktop
One-Line Setup Check
curl -fsSL https://raw.githubusercontent.com/danielbushman/MCP-Quickbase/main/check_dependencies.sh | bashConfigure Claude Desktop
Add this to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"quickbase": {
"command": "npx",
"args": ["-y", "mcp-quickbase"],
"env": {
"QUICKBASE_REALM_HOST": "your-realm.quickbase.com",
"QUICKBASE_USER_TOKEN": "your-user-token",
"QUICKBASE_APP_ID": "your-app-id"
}
}
}
}That's it! Restart Claude Desktop and you can start using Quickbase tools.
Related MCP server: crm-mcp
📦 Installation Options
Option 1: NPM (Recommended)
# Use directly with npx (no installation needed)
npx -y mcp-quickbase
# Or install globally
npm install -g mcp-quickbaseOption 2: From Source
# Clone the repository
git clone https://github.com/danielbushman/MCP-Quickbase.git
cd MCP-Quickbase
# Install dependencies
npm install
# Build the project
npm run buildFor source installation, use this Claude Desktop configuration:
{
"mcpServers": {
"quickbase": {
"command": "node",
"args": ["/path/to/MCP-Quickbase/dist/mcp-stdio-server.js"],
"env": {
"QUICKBASE_REALM_HOST": "your-realm.quickbase.com",
"QUICKBASE_USER_TOKEN": "your-user-token",
"QUICKBASE_APP_ID": "your-app-id"
}
}
}
}🔧 Configuration
The server can start without environment variables configured, but tools will not be functional until proper configuration is provided. Use the check_configuration tool to verify your setup.
Required Environment Variables
QUICKBASE_REALM_HOST- Your Quickbase realm (e.g.,company.quickbase.com)QUICKBASE_USER_TOKEN- Your Quickbase API token (Get one here)
Optional Environment Variables
QUICKBASE_APP_ID- Default application ID
Optional Settings
QUICKBASE_CACHE_ENABLED- Enable caching (true/false, default:true)QUICKBASE_CACHE_TTL- Cache duration in seconds (default:3600)DEBUG- Enable debug logging (true/false, default:false)LOG_LEVEL- Logging level (DEBUG/INFO/WARN/ERROR, default:INFO)
🛠️ Available Tools (25)
Connection & Configuration
check_configuration- Check if Quickbase configuration is properly set uptest_connection- Test connection to Quickbaseconfigure_cache- Configure caching behavior
Application Management
create_app- Create new Quickbase applicationsupdate_app- Update existing applicationslist_tables- List all tables in an application
Table Operations
create_table- Create new tablesupdate_table- Update table propertiesget_table_fields- Get field information for a table
Field Management
create_field- Create new fields in tablesget_field- Get properties of a specific fieldupdate_field- Update field propertiesdelete_field- Delete a field from a table
Record Operations
query_records- Query records with filtering, sorting, and groupBycreate_record- Create single recordsupdate_record- Update existing recordsbulk_create_records- Create multiple recordsbulk_update_records- Update multiple records
File Operations
upload_file- Upload files to file attachment fieldsdownload_file- Download files from records
Relationship Management
get_relationships- Get table relationshipscreate_relationship- Create a new table relationshipupdate_relationship- Update an existing relationshipdelete_relationship- Delete a table relationship
Reporting
run_report- Execute Quickbase reports
📚 Usage Examples
Basic Record Query
Query all customers from the Customers tableCreate a New Record
Create a new customer record with name "Acme Corp" and status "Active"Upload a File
Upload invoice.pdf to the Documents field in record 123🔒 Security
API tokens are handled securely and never logged
All file operations are sandboxed to the working directory
Supports field-level permissions and access controls
📋 Requirements
Node.js 18+
Valid Quickbase account with API access
Claude Desktop (for MCP integration)
🤝 Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
🔗 Links
Available Tools
1 toolcheck_configurationC
Check if Quickbase configuration is properly set up
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It implies a read-only check but doesn't disclose behavioral traits like what happens if configuration is invalid, whether it requires authentication, or what the output indicates. This leaves significant gaps in understanding the tool's operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with no wasted words, making it efficient and front-loaded. However, it could be more structured by including key details like output format or usage context, slightly reducing its completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (a configuration check with no parameters) and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'properly set up' means, what the check entails, or what results to expect, leaving the agent with insufficient context for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could have mentioned implicit inputs like environment settings. Baseline is 4 due to the lack of parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool's purpose as checking Quickbase configuration setup, which is clear but vague about what 'properly set up' entails. It uses a specific verb ('check') and resource ('Quickbase configuration'), but lacks detail on scope or criteria for proper setup, making it moderately informative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool, such as before other operations or in troubleshooting scenarios. With no sibling tools, differentiation isn't needed, but the description doesn't offer any usage context or prerequisites, leaving it as a basic statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.0- Changed
check_configuration1 field changed- removed
Input schema / additionalPropertiesRemoved value: -false
1 tool update
- First observed
check_configuration
TDQS
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.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
ClickUp MCP — wraps the ClickUp REST API v2 (BYO API key)
Let AI agents query data and act across all your business apps via MCP.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
- OneOAuthai.withone
Search, document and execute authenticated API calls across 700+ apps via one MCP server
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceThis read-only MCP Server allows you to connect to Quickbase data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at https://www.cdata.com/solutions/mcp2MIT
- FlicenseNot gradedqualityCmaintenanceBridges Claude Code to the Rowan Rose CRM, translating MCP tool calls into REST API requests for contacts, cases, documents, and more.-
- AlicenseCqualityBmaintenanceProvides complete QuickBooks Online API integration for Claude Code and other MCP-compatible clients, enabling full CRUD operations on 29 entity types and 11 financial reports.100Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables Claude to interact with FileMaker databases through the FileMaker Data API, supporting multi-database connections, CRUD operations, script execution, and metadata discovery.11MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielbushman/MCP-Quickbase'
If you have feedback or need assistance with the MCP directory API, please join our Discord server