Skip to main content
Glama
deenesjakoruzh
danielbushman

Quickbase MCP Server

by danielbushman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Quickbase MCP 服务器

Quickbase 的基于 TypeScript 的模型上下文协议 (MCP) 服务器，旨在与 Claude Desktop 和其他 AI 助手无缝集成。

📋 社区项目通知
这是一个社区开发的集成项目，并非 Quickbase 官方产品。虽然它使用了 Quickbase 的公共 API，但 Quickbase, Inc. 并未提供官方支持。本项目“按原样”提供，并由社区维护。如需 Quickbase 官方产品及支持，请访问quickbase.com 。

🚀 Claude 桌面快速入门

单线设置检查

curl -fsSL https://raw.githubusercontent.com/danielbushman/MCP-Quickbase/main/check_dependencies.sh | bash

配置 Claude 桌面

将其添加到您的 Claude Desktop 配置文件中：

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"
      }
    }
  }
}

**就这样！**重启 Claude Desktop，您就可以开始使用 Quickbase 工具了。

Related MCP server: crm-mcp

📦安装选项

选项 1：NPM（推荐）

# Use directly with npx (no installation needed)
npx -y mcp-quickbase

# Or install globally
npm install -g mcp-quickbase

选项 2：从源头

# Clone the repository
git clone https://github.com/danielbushman/MCP-Quickbase.git
cd MCP-Quickbase

# Install dependencies
npm install

# Build the project
npm run build

对于源安装，请使用此 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"
      }
    }
  }
}

🔧 配置

服务器无需配置环境变量即可启动，但工具只有在正确配置后才能正常运行。请使用check_configuration工具来验证您的设置。

必需的环境变量

  • QUICKBASE_REALM_HOST - 您的 Quickbase 领域（例如company.quickbase.com ）

  • QUICKBASE_USER_TOKEN - 您的 Quickbase API 令牌（在此获取）

可选环境变量

  • QUICKBASE_APP_ID - 默认应用程序 ID

可选设置

  • QUICKBASE_CACHE_ENABLED - 启用缓存（ true / false ，默认值： true ）

  • QUICKBASE_CACHE_TTL - 缓存持续时间（秒）（默认值： 3600 ）

  • DEBUG - 启用调试日志记录（ true / false ，默认值： false ）

  • LOG_LEVEL - 日志级别（ DEBUG / INFO / WARN / ERROR ，默认值： INFO ）

🛠️ 可用工具

连接和配置

  • check_configuration - 检查 Quickbase 配置是否正确设置

  • test_connection - 测试与 Quickbase 的连接

  • configure_cache - 配置缓存行为

应用程序管理

  • create_app - 创建新的 Quickbase 应用程序

  • update_app - 更新现有应用程序

  • list_tables - 列出应用程序中的所有表

表操作

  • **create_table**创建新表

  • update_table - 更新表属性

  • get_table_fields - 获取表的字段信息

现场管理

  • **create_field**在表中创建新字段

  • update_field - 更新字段属性

记录操作

  • query_records - 通过过滤和排序查询记录

  • create_record - 创建单个记录

  • update_record - 更新现有记录

  • bulk_create_records - 创建多个记录

  • bulk_update_records - 更新多条记录

文件操作

  • upload_file - 将文件上传到文件附件字段

  • download_file - 从记录中下载文件

报告

  • run_report - 执行 Quickbase 报告

📚 使用示例

基本记录查询

Query all customers from the Customers table

创建新记录

Create a new customer record with name "Acme Corp" and status "Active"

上传文件

Upload invoice.pdf to the Documents field in record 123

🔒 安全

  • API 令牌得到安全处理，并且不会被记录

  • 所有文件操作均在工作目录中进行沙盒化

  • 支持字段级权限和访问控制

📋 要求

  • Node.js 18 或更高版本

  • 具有 API 访问权限的有效 Quickbase 帐户

  • Claude Desktop（用于 MCP 集成）

🤝 贡献

欢迎贡献代码！欢迎提交 Pull 请求。

📄 许可证

该项目根据 MIT 许可证获得许可 - 有关详细信息，请参阅LICENSE文件。

🔗 链接

Available Tools

1 tool
check_configurationC

Check if Quickbase configuration is properly set up

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

C2.8/5.0
Behavior2/5

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.

Conciseness4/5

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.

Completeness2/5

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.

Parameters4/5

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.

Purpose3/5

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.

Usage Guidelines2/5

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. 1 tool updatev1.0.0
    • Changedcheck_configuration1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
  2. 1 tool update
    • First observedcheck_configuration
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

C2.9/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness1/5

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

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Quickbase MCP Server by CData by CDataSoftware

    Quickbase MCP Server by CDataofficial

    CDataSoftware
    A
    license
    Not graded
    quality
    D
    maintenance
    This 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/mcp
    2
    MIT

  • crm-mcp

    RRS-repositories
    F
    license
    Not graded
    quality
    C
    maintenance
    Bridges Claude Code to the Rowan Rose CRM, translating MCP tool calls into REST API requests for contacts, cases, documents, and more.
    -

  • QuickBooks Online MCP Server

    Brax-Tech-Internal
    A
    license
    C
    quality
    D
    maintenance
    Provides 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.
    100
    Apache 2.0

  • MCP-Claude-FileMaker

    datacraftdevelopment
    A
    license
    B
    quality
    D
    maintenance
    Enables Claude to interact with FileMaker databases through the FileMaker Data API, supporting multi-database connections, CRUD operations, script execution, and metadata discovery.
    11
    11
    MIT

Appeared in Searches