Quickbase MCP Server
Quickbase MCP-Server
Ein TypeScript-basierter Model Context Protocol (MCP)-Server für Quickbase, der für die nahtlose Integration mit Claude Desktop und anderen KI-Assistenten entwickelt wurde.
📋 Hinweis zum Gemeinschaftsprojekt
Dies ist eine von der Community entwickelte Integration und kein offizielles Quickbase-Produkt. Sie nutzt zwar die öffentlichen APIs von Quickbase, wird aber nicht offiziell von Quickbase, Inc. unterstützt. Dieses Projekt wird „im Ist-Zustand“ bereitgestellt und von der Community gepflegt. Offizielle Quickbase-Produkte und Support finden Sie unter quickbase.com .
🚀 Schnellstart für Claude Desktop
Einzeilige Setup-Prüfung
curl -fsSL https://raw.githubusercontent.com/danielbushman/MCP-Quickbase/main/check_dependencies.sh | bashClaude Desktop konfigurieren
Fügen Sie dies zu Ihrer Claude Desktop-Konfigurationsdatei hinzu:
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"
}
}
}
}Das war's! Starten Sie Claude Desktop neu und Sie können die Quickbase-Tools verwenden.
Related MCP server: crm-mcp
📦 Installationsoptionen
Option 1: NPM (empfohlen)
# Use directly with npx (no installation needed)
npx -y mcp-quickbase
# Or install globally
npm install -g mcp-quickbaseOption 2: Aus der Quelle
# Clone the repository
git clone https://github.com/danielbushman/MCP-Quickbase.git
cd MCP-Quickbase
# Install dependencies
npm install
# Build the project
npm run buildVerwenden Sie für die Quellinstallation diese Claude Desktop-Konfiguration:
{
"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"
}
}
}
}🔧 Konfiguration
Der Server kann ohne konfigurierte Umgebungsvariablen gestartet werden. Die Tools sind jedoch erst nach der korrekten Konfiguration funktionsfähig. Überprüfen Sie Ihre Konfiguration mit dem Tool check_configuration .
Erforderliche Umgebungsvariablen
QUICKBASE_REALM_HOST– Ihr Quickbase-Realm (z. B.company.quickbase.com)QUICKBASE_USER_TOKEN– Ihr Quickbase-API-Token ( Holen Sie sich hier eines )
Optionale Umgebungsvariablen
QUICKBASE_APP_ID– Standard-Anwendungs-ID
Optionale Einstellungen
QUICKBASE_CACHE_ENABLED– Caching aktivieren (true/false, Standard:true)QUICKBASE_CACHE_TTL– Cache-Dauer in Sekunden (Standard:3600)DEBUG- Debug-Protokollierung aktivieren (true/false, Standard:false)LOG_LEVEL– Protokollierungsebene (DEBUG/INFO/WARN/ERROR, Standard:INFO)
🛠️ Verfügbare Tools
Anschluss & Konfiguration
check_configuration- Überprüfen Sie, ob die Quickbase-Konfiguration richtig eingerichtet isttest_connection– Testen Sie die Verbindung zu Quickbaseconfigure_cache- Caching-Verhalten konfigurieren
Anwendungsmanagement
create_app- Neue Quickbase-Anwendungen erstellenupdate_app- Vorhandene Anwendungen aktualisierenlist_tables- Alle Tabellen in einer Anwendung auflisten
Tabellenoperationen
create_table- Neue Tabellen erstellenupdate_table- Tabelleneigenschaften aktualisierenget_table_fields- Feldinformationen für eine Tabelle abrufen
Feldverwaltung
create_field- Neue Felder in Tabellen erstellenupdate_field- Feldeigenschaften aktualisieren
Rekordvorgänge
query_records- Datensätze abfragen mit Filterung und Sortierungcreate_record- Einzelne Datensätze erstellenupdate_record- Vorhandene Datensätze aktualisierenbulk_create_records- Mehrere Datensätze erstellenbulk_update_records- Mehrere Datensätze aktualisieren
Dateioperationen
upload_file- Dateien in Dateianhangfelder hochladendownload_file- Dateien aus Datensätzen herunterladen
Berichterstattung
run_report- Quickbase-Berichte ausführen
📚 Anwendungsbeispiele
Grundlegende Datensatzabfrage
Query all customers from the Customers tableErstellen eines neuen Datensatzes
Create a new customer record with name "Acme Corp" and status "Active"Eine Datei hochladen
Upload invoice.pdf to the Documents field in record 123🔒 Sicherheit
API-Token werden sicher behandelt und niemals protokolliert
Alle Dateivorgänge werden in einer Sandbox auf das Arbeitsverzeichnis verschoben.
Unterstützt Berechtigungen und Zugriffskontrollen auf Feldebene
📋 Voraussetzungen
Node.js 18 oder höher
Gültiges Quickbase-Konto mit API-Zugriff
Claude Desktop (für MCP-Integration)
🤝 Beitragen
Beiträge sind willkommen! Senden Sie gerne einen Pull Request.
📄 Lizenz
Dieses Projekt ist unter der MIT-Lizenz lizenziert – Einzelheiten finden Sie in der Datei LICENSE .
🔗 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.
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
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.
Maintenance
Related MCP Connectors
ClickUp MCP — wraps the ClickUp REST API v2 (BYO API key)
Any REST/SOAP/GraphQL/OData/SQL API as MCP tools for Claude & ChatGPT. 486 connectors: SAP, ERP.
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.
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.-
- AlicenseCqualityDmaintenanceProvides 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
- AlicenseBqualityDmaintenanceEnables Claude to interact with FileMaker databases through the FileMaker Data API, supporting multi-database connections, CRUD operations, script execution, and metadata discovery.1111MIT