Skip to main content
Glama

TOCA MCP Server

Google Drive의 TOCA_OS 비즈니스 소스 오브 트루스를 따르는 ChatGPT용 결정적 실행 계층입니다.

프로덕션 상태

이 저장소는 부트스트랩 단계를 지났습니다. 현재 프로덕션 기반에는 다음이 포함됩니다:

  • /mcp의 비공개 Streamable HTTP MCP 전송

  • 헬스/준비 상태 경계

  • Meta OAuth, 웹훅 및 시크릿 관리 경계

  • 공급자 기반 Instagram 기록/인사이트 읽기

  • Meta Ads 읽기 기능

  • 영구 PostgreSQL 스케줄링

  • TOCA 관리 Instagram 스케줄링 도구

  • PostgreSQL에서 기한이 도래한 작업을 가져오는 자율 단일 인스턴스 Cloud Run 데몬

  • 재시도 전 공급자 기반 조정을 통한 멱등적 Instagram 게시

  • 단기 서명 URL을 통한 비공개 GCS 자산 전달

  • 감사, 데드 레터 및 실패 시 잠금 실행 제어

TOCA_OS / Google Drive는 비즈니스 소스 오브 트루스로 유지됩니다. GitHub는 코드, 스키마, 테스트 및 인프라의 소스 오브 트루스입니다. 외부 공급자는 외부 부작용에 대한 권위 있는 소스로 유지됩니다.

Related MCP server: genpark-workplace-goal-to-artifact-dag-orchestrator-skill

활성 프로덕션 토폴로지

ChatGPT
  -> TOCA_OS business policy/context
  -> private TOCA MCP service
       -> typed MCP tools
       -> PostgreSQL scheduled_jobs / audit_events / provider_publications
  -> TOCA-managed Instagram daemon (singleton Cloud Run service)
       -> claimDue()
       -> approval/audit gate
       -> provider reconciliation
       -> idempotent Instagram publication
       -> provider confirmation

스케줄링은 애플리케이션 작업이며 보호된 instagram.toca_schedule.* MCP 표면을 사용해야 합니다. Git 커밋과 애플리케이션 재배포는 일반적인 게시 시계나 스케줄링 API가 아닙니다.

품질 게이트

승격되는 모든 변경 사항은 다음을 통과해야 합니다:

pnpm install --frozen-lockfile
pnpm format:check
pnpm architecture:check
pnpm lint
pnpm typecheck
pnpm test
pnpm build

현재 계약에 대해서는 docs/architecture/README.md, docs/architecture/routes-capabilities-v1.md, docs/architecture/toca-managed-instagram-scheduler-v1.md 및 docs/operations/infrastructure-control-plane.md를 참조하세요.

Available Tools

12 tools
toca.approval.getGet TOCA ApprovalA
Read-onlyIdempotent

Read one ApprovalRecord owned by the authenticated requester.

Inputs: approvalId (required).

toca.approval.requestRequest TOCA ApprovalB

Create a formal ApprovalRecord bound to the exact typed execution payload and authenticated requester.

Inputs: payload (required), evidence (required), expiresAt (required), capabilityId (required), +1 more.

toca.audit.queryQuery TOCA AuditB
Read-onlyIdempotent

Read immutable audit-ledger records by correlation inside the authenticated tenant boundary.

Inputs: correlationId (required), limit, executionId.

toca.capabilities.describeDescribe TOCA CapabilityA
Read-onlyIdempotent

Resolve aliases and return the canonical typed, policy and lifecycle contract for one capability.

Inputs: capabilityId (required).

toca.capabilities.searchSearch TOCA CapabilitiesB
Read-onlyIdempotent

Search the canonical capability catalog without materializing one MCP tool per capability.

Inputs: limit, query, routeId, provider, +1 more.

toca.event.getGet TOCA EventRecordA
Read-onlyIdempotent

Read one canonical EventRecord inside the authenticated tenant boundary.

Inputs: eventId (required).

toca.executeExecute TOCA CapabilityC

Resolve identity, capability, typed schema, policy, risk, approval, idempotency, handler, provider read-back and audit before reporting success.

Inputs: payload (required), capabilityId (required), correlationId (required), approvalId.

toca.system.healthTOCA Core HealthA
Read-onlyIdempotent

Return deterministic TOCA Core MCP surface and persistence readiness metadata.

Inputs: no named parameters.

toca.verifyVerify TOCA ExecutionB
Read-onlyIdempotent

Verify the immutable audit chain, exact execution descriptor and fresh provider state for side effects.

Inputs: result (required), payload (required), executionId (required), capabilityId (required), +1 more.

toca.workflow.advanceAdvance TOCA WorkflowD

Apply one explicit, evidence-bearing transition through the existing durable workflow engine.

toca.workflow.createCreate TOCA WorkflowB
Idempotent

Create a durable tenant-scoped workflow using the existing workflow engine and transactional outbox.

Inputs: steps (required), routeId (required), definitionId (required), correlationId (required), +3 more.

toca.workflow.getGet TOCA WorkflowA
Read-onlyIdempotent

Read one durable workflow inside the authenticated tenant boundary.

Inputs: workflowId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., toca.workflow.create vs toca.workflow.get vs toca.workflow.advance). The exception is toca.system.health versus toca.verify—both touch on readiness/state but from different angles. Minor overlap is acceptable.

    Naming Consistency5/5

    All tool names follow a consistent pattern of 'toca.<domain>.<verb>' with clear verbs (get, create, advance, query) and nouns (capability, workflow, approval, audit, event). No mixing of styles or conventions.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range. Each tool covers a distinct operation across core domains (system, capabilities, workflows, approvals, audit, events), and the count feels appropriately scoped for the server's purpose.

    Completeness3/5

    The server covers key operations but has notable gaps: workflow lacks an update/abort/delete, approval only has create/get (no approve/deny), and there is no event publishing—only reading. The execute tool is comprehensive but may serve as a generic workaround, yet missing lifecycle operations could still cause agent failures in certain flows.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to interact with Instagram by scraping profiles, posts, reels, DMs, and business insights through a robust, DOM-agnostic browser orchestration engine that bypasses Instagram's anti-automation measures.
      28
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to break high-level business objectives into dependency-ordered sub-task graphs and then directly generate the finished deliverables, such as financial spreadsheets, executive presentations, and analytical reports. It runs as a zero-dependency Python MCP server over JSON-RPC stdio, adding deterministic authorization, role-boundary validation, and telemetry.
      7
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to operate Instagram Business and Creator accounts through Meta's official API with OAuth 2.1 authentication, covering publishing images, carousels, reels and stories, content scheduling, comment moderation, Direct messaging, and account and media insights across multiple connected accounts. An optional read-only private-session reader exposes Direct inbox threads, and a webhook-backed archive accumulates conversation history that Meta's API cannot return on demand.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients like Claude and Cursor to read and act on Instagram, Facebook, WhatsApp and SMS inboxes, contacts, appointments, flows, comment automation, Content Studio posts, market intel and a knowledge base through the ChatGenius REST API. Exposes 105 scope-capped tools, with destructive actions marked for client approval and idempotency keys guarding every write.
      105
      206 npm
      MIT