check_configuration
Check if Quickbase configuration is properly set up
Works both sides of a Quickbase app — query and write records, and create the tables, fields and relationships underneath them.
LABSCO SUMMARY
That is what separates it from a records-only integration: an agent can stand up a tracker, not just fill one in. Begin every session with check_configuration, because the server comes up cleanly even with the realm or token missing, and a missing variable then surfaces as a failing tool rather than a startup error.
A community-built MCP server over the Quickbase REST API, with caching and retry logic in front of it. Not an official Quickbase product, though it uses their public APIs.
A Quickbase account with API access, and Node.js 18+. Two required environment variables: QUICKBASE_REALM_HOST (your realm, such as company.quickbase.com) and QUICKBASE_USER_TOKEN; QUICKBASE_APP_ID sets a default application. The server starts whether or not they are set, and the tools only work once they are — so call check_configuration first. Optional settings: QUICKBASE_CACHE_ENABLED (default true), QUICKBASE_CACHE_TTL in seconds (default 3600), DEBUG and LOG_LEVEL. Run it over stdio with npx -y mcp-quickbase.
One command plus a key — npx -y mcp-quickbase, then supply credentials
USE CASES
Read the field definitions first so you can name them, then query with filters and sorting.
Create or update many records in a single call instead of one at a time.
Create the field, then read the table's fields back to confirm its ID and properties.
See what relationships already exist, then create the one that is missing.
Upload into a file attachment field, or pull an existing attachment back down.
Check the configuration is complete, then confirm the realm actually answers.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_configurationCheck if Quickbase configuration is properly set up
BEFORE YOU INSTALL
1 tool when we connected. Without QUICKBASE_REALM_HOST and QUICKBASE_USER_TOKEN only check_configuration appears; with both set, the documentation lists 25 tools.
CONTEXT COST
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
npx -y mcp-quickbase{
"mcpServers": {
"quickbase": {
"command": "npx",
"args": [
"-y",
"mcp-quickbase"
],
"env": {
"QUICKBASE_REALM_HOST": "<YOUR_REALM>.quickbase.com",
"QUICKBASE_USER_TOKEN": "<YOUR_QUICKBASE_USER_TOKEN>",
"QUICKBASE_APP_ID": "<YOUR_QUICKBASE_APP_ID>"
}
}
}
}Clone and build the server
Needs Node.js 18 or newer.
git clone https://github.com/danielbushman/MCP-Quickbase.git
cd MCP-Quickbase
npm install
npm run buildAdd this to claude_desktop_config.json
<YOUR_PATH_TO_MCP_QUICKBASE> is the full path of your clone.
{
"mcpServers": {
"quickbase": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_QUICKBASE>/dist/mcp-stdio-server.js"
],
"env": {
"QUICKBASE_REALM_HOST": "<YOUR_REALM>.quickbase.com",
"QUICKBASE_USER_TOKEN": "<YOUR_QUICKBASE_USER_TOKEN>",
"QUICKBASE_APP_ID": "<YOUR_QUICKBASE_APP_ID>"
}
}
}
}