The MCP interface 🟡 Live ingress
The public OAuth-protected MCP ingress is live at https://greatbook.co/mcp, but ChatGPT and Claude behavior has not been exercised end to end.
Its public descriptor, pinned backend, and web release all carry registry 1.14.1.
The inventories below are current on the public service, but they do not prove provider behavior.
greatbook.co, and its /mcp path is declared by the live protected-resource and MCP metadata.
Current live surface
Registry 1.14.1 and its live transport contract are deliberately different inventories:
- 116 capability records across 26 domains describe stable business outcomes: 98 current, seven experimental, one queued, two deprecated and eight forbidden;
- 46 capability records are available through 32 shared typed MCP tools;
- the transport contract declares exactly 50 MCP tools, because capability and skill discovery, skill runs, evidence reads, typed reversal staging, guarded-proposal lifecycle and staged-workspace lifecycle are tools too;
- 18 MCP resources are released: 17 MCP Apps render selected tool results, and one authenticated JSON resource publishes the provider-neutral skill registry.
A product outcome can be current without an MCP adapter, several outcomes can share one typed tool, and a tool can have no dedicated App resource.
Discovery keeps those facts separate instead of turning a current screen or service into an invented action.
The current greatbook.accounting.event.reverse@1 record is available through the typed greatbook_business_reversal_stage tool and the shared staged-workspace App.
The tool reads the exact journal and its checksum server-side and creates temporary review state; it does not commit, accept caller-supplied accounting facts or add a dedicated Apps resource.
The 50 declared tools split as follows:
- 37 read-only tools for capability and skill discovery, grounded explanations, skill-run status, accounting events, AP aging, intake audit, dimensions, bank and audit evidence, Typewriter approval trails, Books families, close state, Matching evidence, Typewriter/W6/W7 facts, Accountant reads, guarded-action status and staged-workspace resume/read/receipt;
- one state-changing skill-run starter and one state-changing typed business-reversal staging tool, both limited to temporary review/run state;
- three state-changing tools for creating a compatibility guarded proposal, creating its single-use confirmation and executing that exact proposal;
- eight state-changing staged-workspace tools for temporary review state and the closed typed commit boundary.
The compatibility guarded-proposal allowlist contains only greatbook.workflow.resume.
It changes durable workflow metadata after exact revision, expiry, actor, organization, registry-pin, source-fingerprint, confirmation and idempotency checks.
The staged workspace preserves a checklist, proposed changes, exact money, immutable revisions, validation, exact selection and an itemized receipt across turns and reconnects.
Only the exact confirmed selection may reach the closed adapter registry.
That registry includes workflow resume, W3 Matching accept/reject/undo, Typewriter approve/submit, adjustment approve/reject, fiscal close/reopen and typed business reversal.
Each adapter binds an exact target version, verified role and organization, canonical validation, idempotency, maker-checker rule, audit evidence and reversal or compensation posture before calling its named domain writer.
There is still no arbitrary journal, settlement, payment, route or generic action dispatcher.
Discovery before operation
Deep discovery follows search, describe, recommend and resume without widening the tool surface:
- Search the role-filtered registry with
greatbook_capabilities_list.
- Describe one exact capability and its prerequisites with
greatbook_capability_get.
- Use the deterministic workflow recommendation contract to rank only registry-backed safe outcomes; the raw workflow recommend/start/get/resume endpoints remain application services rather than declared MCP tools.
- Call a named typed read, or resume an existing durable staged workspace with
greatbook_workspace_resume, retaining stable GreatBook references and the authoritative workspace revision.
- For a consequential supported outcome, validate and confirm the exact selection before the typed domain adapter commits it.
This path does not expose raw LangGraph nodes, graph state, SQL, HTTP routes, tables or a generic action name.
Workflow recommendation/start/get/resume services exist behind typed gateway operations, but the current MCP tool list does not advertise the raw workflow operations.
A compatible client using the live 1.14.1 contract receives the same entry catalogue, input/output schemas, ontology relationships and stable capability records.
The describe result includes the canonical business-logic owner, role and availability rules, prerequisites, conflicts, limitations, idempotency and reversal posture without inventing a callable tool.
Evidence UI
Seventeen optional MCP Apps resources render the current executable outcomes: discovery; accounting events; AP aging; Books overview, family, register and tie-out; close readiness and inventory; audit runs, findings and Assurance lineage; Typewriter documents; bank evidence/W6/W7 facets; Accountant reads; guarded workflow resume; and the staged workspace.
The eighteenth resource is the authenticated JSON skill registry, not a visual App.
Five additional resource designs remain queued and are absent from resources/list.
The model-readable structured result and GreatBook deep link remain sufficient when a component cannot load.
Widget selection and filters are ephemeral; authoritative records, permissions and durable workflow state remain on GreatBook servers.
Live-service and provider boundary
Public routing, OAuth protected-resource discovery, and the MCP descriptor are live.
The live descriptor is current with the release source at registry 1.14.1.
ChatGPT and Claude each still need client-specific OAuth, discovery, tool, UI-fallback, confirmation, tenant-isolation, and safety exercises.
This public page intentionally omits protected configuration names, credentials, private URLs, internal host details and operational commands.
This page intentionally does not infer a provider connection merely because the public endpoint exists.
