TOCA MCP Server
TOCA MCP Server
Google Drive 内の TOCA_OS ビジネスソース・オブ・トゥルースによって管理される ChatGPT 用の決定論的実行レイヤー。
本番ステータス
このリポジトリはブートストラップ段階を超えています。現在の本番基盤には以下が含まれます:
/mcpにおけるプライベートな Streamable HTTP MCP トランスポート;ヘルス/レディネス境界;
Meta OAuth、Webhook、シークレット管理の境界;
プロバイダー連携の 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 toolstoca.approval.getGet TOCA ApprovalARead-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 AuditBRead-onlyIdempotent
Read immutable audit-ledger records by correlation inside the authenticated tenant boundary.
Inputs: correlationId (required), limit, executionId.
toca.capabilities.describeDescribe TOCA CapabilityARead-onlyIdempotent
Resolve aliases and return the canonical typed, policy and lifecycle contract for one capability.
Inputs: capabilityId (required).
toca.capabilities.searchSearch TOCA CapabilitiesBRead-onlyIdempotent
Search the canonical capability catalog without materializing one MCP tool per capability.
Inputs: limit, query, routeId, provider, +1 more.
toca.event.getGet TOCA EventRecordARead-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 HealthARead-onlyIdempotent
Return deterministic TOCA Core MCP surface and persistence readiness metadata.
Inputs: no named parameters.
toca.verifyVerify TOCA ExecutionBRead-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 WorkflowBIdempotent
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 WorkflowARead-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
Scored across 12 tools
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.
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.
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.
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
Related MCP Connectors
Instagram for AI agents: publish, comments, DM by keyword, inbox, insights. Facebook Pages soon.
Instagram for AI agents: publish, read comments and DMs, insights, and engage from your account.
Agent-first social media publishing, scheduling, analytics, and unified inbox API + 16-tool MCP server across 18 social platforms (X, LinkedIn, Instagram, YouTube, TikTok, Threads, Bluesky, Reddit, Telegram, Discord, Mastodon, Facebook, Pinterest).
Publish and schedule Instagram posts, Reels and carousels from your AI assistant.
Related MCP Servers
- AlicenseAqualityFmaintenanceEnables 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.281Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables 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.7MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-

chatgenius-mcpofficial
AlicenseBqualityCmaintenanceEnables 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.105206 npmMIT