Skip to main content
Glama

TOCA MCP Server

Deterministische Ausführungsebene für ChatGPT, gesteuert durch TOCA_OS, die geschäftliche Quelle der Wahrheit in Google Drive.

Produktionsstatus

Das Repository ist über das Bootstrap-Stadium hinaus. Die Produktionsgrundlage umfasst derzeit:

  • privater Streamable-HTTP-MCP-Transport unter /mcp;

  • Health-/Readiness-Grenzen;

  • Meta-OAuth-, Webhook- und Secret-Management-Grenzen;

  • anbietergestützte Lesezugriffe auf Instagram-Verlauf und -Insights;

  • Meta-Ads-Lesefunktionen;

  • persistentes PostgreSQL-Scheduling;

  • TOCA-verwaltete Instagram-Scheduling-Tools;

  • ein autonomer Singleton-Cloud-Run-Daemon, der fällige Aufträge aus PostgreSQL übernimmt;

  • idempotente Instagram-Veröffentlichung mit anbietergestütztem Abgleich vor dem Wiederholungsversuch;

  • private GCS-Asset-Bereitstellung über kurzlebige signierte URLs;

  • Audit-, Dead-Letter- und Fail-Closed-Ausführungskontrollen.

TOCA_OS / Google Drive bleibt die geschäftliche Quelle der Wahrheit. GitHub ist die Quelle der Wahrheit für Code, Schemas, Tests und Infrastruktur. Externe Anbieter bleiben maßgeblich für externe Seiteneffekte.

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

Aktive Produktionstopologie

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

Scheduling ist eine Anwendungsoperation und muss die geschützte MCP-Oberfläche instagram.toca_schedule.* verwenden. Git-Commits und Anwendungs-Redeployments sind nicht der normale Veröffentlichungstakt oder die Scheduling-API.

Qualitätsgate

Jede übernommene Änderung muss Folgendes bestehen:

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

Siehe docs/architecture/README.md, docs/architecture/routes-capabilities-v1.md, docs/architecture/toca-managed-instagram-scheduler-v1.md und docs/operations/infrastructure-control-plane.md für die aktuellen Verträge.

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