Skip to main content
Glama
deenesjakoruzh
danielbushman

Quickbase MCP Server

by danielbushman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Quickbase MCP 서버

Claude Desktop 및 기타 AI 어시스턴트와의 원활한 통합을 위해 설계된 Quickbase용 TypeScript 기반 모델 컨텍스트 프로토콜(MCP) 서버입니다.

📋 커뮤니티 프로젝트 공지
이 통합 기능은 커뮤니티에서 개발한 것으로, 공식 Quickbase 제품이 아닙니다. Quickbase의 공개 API를 사용하지만 Quickbase, Inc.의 공식 지원은 제공되지 않습니다. 이 프로젝트는 "있는 그대로" 제공되며 커뮤니티에서 관리합니다. 공식 Quickbase 제품 및 지원은 quickbase.com을 방문하세요.

🚀 Claude Desktop 빠른 시작

한 줄 설정 확인

지엑스피1

Claude Desktop 구성

Claude Desktop 구성 파일에 다음을 추가하세요.

macOS : ~/Library/Application Support/Claude/claude_desktop_config.json
윈도우 : %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 통합용)

🤝 기여하기

기여를 환영합니다! 풀 리퀘스트를 제출해 주세요.

📄 라이센스

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다. 자세한 내용은 라이선스 파일을 참조하세요.

🔗 링크

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