Quickbase MCP Server
Servidor MCP de Quickbase
Un servidor de Protocolo de contexto de modelo (MCP) basado en TypeScript para Quickbase, diseñado para una integración perfecta con Claude Desktop y otros asistentes de IA.
Aviso del proyecto comunitario
Esta es una integración desarrollada por la comunidad y no es un producto oficial de Quickbase. Si bien utiliza las API públicas de Quickbase, no cuenta con soporte oficial de Quickbase, Inc. Este proyecto se ofrece "tal cual" y es mantenido por la comunidad. Para obtener información sobre los productos y el soporte técnico oficiales de Quickbase, visite quickbase.com .
🚀 Inicio rápido para Claude Desktop
Comprobación de configuración de una línea
curl -fsSL https://raw.githubusercontent.com/danielbushman/MCP-Quickbase/main/check_dependencies.sh | bashConfigurar Claude Desktop
Agregue esto a su archivo de configuración de Claude Desktop:
macOS : ~/Library/Application Support/Claude/claude_desktop_config.json
Ventanas : %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"
}
}
}
}¡Listo! Reinicia Claude Desktop y podrás empezar a usar las herramientas de Quickbase.
Related MCP server: crm-mcp
📦 Opciones de instalación
Opción 1: NPM (Recomendado)
# Use directly with npx (no installation needed)
npx -y mcp-quickbase
# Or install globally
npm install -g mcp-quickbaseOpción 2: Desde la fuente
# Clone the repository
git clone https://github.com/danielbushman/MCP-Quickbase.git
cd MCP-Quickbase
# Install dependencies
npm install
# Build the project
npm run buildPara la instalación de origen, utilice esta configuración de Claude Desktop:
{
"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"
}
}
}
}🔧 Configuración
El servidor puede iniciarse sin variables de entorno configuradas, pero las herramientas no funcionarán hasta que se configure correctamente. Utilice la herramienta check_configuration para verificar la configuración.
Variables de entorno requeridas
QUICKBASE_REALM_HOST: su dominio Quickbase (por ejemplo,company.quickbase.com)QUICKBASE_USER_TOKEN: su token de API de Quickbase ( obtenga uno aquí )
Variables de entorno opcionales
QUICKBASE_APP_ID- ID de aplicación predeterminada
Configuraciones opcionales
QUICKBASE_CACHE_ENABLED- Habilitar almacenamiento en caché (true/false, valor predeterminado:true)QUICKBASE_CACHE_TTL: Duración de la caché en segundos (valor predeterminado:3600)DEBUG- Habilitar el registro de depuración (true/false, valor predeterminado:false)LOG_LEVEL- Nivel de registro (DEBUG/INFO/WARN/ERROR, predeterminado:INFO)
🛠️ Herramientas disponibles
Conexión y configuración
check_configuration- Comprueba si la configuración de Quickbase está configurada correctamentetest_connection- Prueba la conexión a Quickbaseconfigure_cache- Configurar el comportamiento del almacenamiento en caché
Gestión de aplicaciones
create_app- Crea nuevas aplicaciones Quickbaseupdate_app- Actualizar aplicaciones existenteslist_tables- Lista todas las tablas en una aplicación
Operaciones de tabla
create_table- Crea nuevas tablasupdate_table- Actualizar las propiedades de la tablaget_table_fields- Obtener información de campo para una tabla
Gestión de campo
create_field- Crea nuevos campos en tablasupdate_field- Actualizar propiedades de campo
Operaciones de registro
query_records- Consultar registros con filtrado y ordenamientocreate_record- Crea registros individualesupdate_record- Actualizar registros existentesbulk_create_records- Crea múltiples registrosbulk_update_records- Actualizar varios registros
Operaciones con archivos
upload_file- Subir archivos a los campos de adjuntos de archivosdownload_file- Descargar archivos de los registros
Informes
run_report- Ejecutar informes de Quickbase
Ejemplos de uso
Consulta básica de registros
Query all customers from the Customers tableCrear un nuevo registro
Create a new customer record with name "Acme Corp" and status "Active"Subir un archivo
Upload invoice.pdf to the Documents field in record 123🔒 Seguridad
Los tokens API se manejan de forma segura y nunca se registran
Todas las operaciones de archivos se almacenan en el directorio de trabajo.
Admite permisos a nivel de campo y controles de acceso
📋 Requisitos
Node.js 18 o superior
Cuenta Quickbase válida con acceso API
Claude Desktop (para integración con MCP)
🤝 Contribuyendo
¡Agradecemos sus contribuciones! No dude en enviar una solicitud de incorporación de cambios.
📄 Licencia
Este proyecto está licenciado bajo la licencia MIT: consulte el archivo de LICENCIA para obtener más detalles.
🔗 Enlaces
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