InkDraft

DEVELOPER REFERENCE ยท CHECKED NOVEMBER 18, 2026

Read the current document correctly.

InkDraft exposes a remote, read-only MCP interface for one account's current synced iPad document. A useful integration must handle authorization, original images, complete reads, and revision changes.

Protocol support is not a compatibility guarantee. The published consumer setup covers ChatGPT and Claude, subject to each account and conversation's availability. Gemini's current test is blocked at registration; consumer compatibility remains unestablished. The synthetic evidence below does not test any consumer model or OAuth login.

Connection and supported setup paths

Use the ChatGPT or Claude listing and setup instructions for those products. Sign into the same InkDraft account and sign-in method as on iPad, authorize paper reading, and enable the connector in the actual conversation. A local CLI connection does not configure a separate cloud chat. InkDraft Cloud and the assistant's own eligibility are separate requirements; see product facts.

For an independently configured client, the remote endpoint is:

https://inkdraft-accounts-565660877538.us-central1.run.app/mcp

The client needs Streamable HTTP, OAuth discovery, PKCE S256, a supported client-registration path, and image-content handling. Use the host's OAuth flow; do not paste an iPad credential or client secret into an assistant. The existing setup guide provides optional local CLI commands. This reference does not install a connection.

The implementation is stateless and handles MCP requests through HTTP POST with JSON responses. All MCP calls, including initialization and tool listing, require account authorization with paper.read. offline_access is requested for continued access where the host supports it. Remote readers have no ink-writing tool. Document tools also require an active cloud entitlement; profile identification alone does not prove document access.

Public, credential-free discovery check:

curl -i https://inkdraft-accounts-565660877538.us-central1.run.app/mcp

An unauthenticated request should return HTTP 401 and a WWW-Authenticate challenge pointing to protected-resource metadata. That is an authorization boundary, not a successful connection. Follow the discovered metadata through the client's normal flow. Do not repeatedly register clients to diagnose a registration failure.

Five tools, one current document

get_profile({})
Returns the connected InkDraft account's identifier and display name. Compare the connection with your iPad account if the document is empty or unexpected. Account identifiers and page content should not be copied into public bug reports.
get_document({})
Returns current metadata, revision and all ordered page IDs. It returns no page images. Metadata discovery alone is not a read of the handwriting.
get_full_document({cursor?})
Start with empty arguments. Follow each returned nextCursor using this same tool until complete: true and nextCursor: null. Each response contains up to four original images within a byte limit, with page numbers and total page count. Fewer than four images need not mean completion.
get_pages({documentId, revision, pageIds})
Request one to four distinct page IDs at the exact current revision. Use IDs returned by metadata; they are UUIDs, not page numbers. Follow remainingPageIds if the byte limit leaves requested pages unread. A historical revision is not a history lookup.
get_document_changes({documentId, sinceRevision, cursor?})
Use only after a complete read exists in this conversation. Keep the original document ID and sinceRevision fixed across continuation calls; follow nextCursor until it is null. Apply returned images, removedPageIds, title and pageOrder, then advance the baseline. Unchanged images are omitted. A response with no images may still carry ordering or title information.

Document tool results contain JSON text plus structuredContent metadata. PNGs arrive as MCP content blocks with type: "image" and mimeType: "image/png", in the same order as the returned page metadata. The JSON does not duplicate the image bytes or supply an InkDraft OCR transcript. Native editable ink is not returned to remote readers.

The accessible scope is the entire current synced document, including all pages. It is not the local folders, inactive documents, Trash, or retrievable historical server versions. Opening another document on iPad switches the cloud slot after sync. Reading does not edit the document, trigger a new assistant turn, or authorize unrelated actions.

Reproducible request sequence

Use these tools/call parameters in an already initialized, authorized MCP client. The JSON request templates include complete JSON-RPC envelopes. They are examples, not captured results; replace continuation and identity placeholders with values returned by your own connection.

  1. Identify the account with {"name":"get_profile","arguments":{}}. Check the current metadata with {"name":"get_document","arguments":{}}.
  2. Begin the whole-document read with {"name":"get_full_document","arguments":{}}. If it is incomplete, pass the returned cursor in {"name":"get_full_document","arguments":{"cursor":"RETURNED_NEXT_CURSOR"}}. Repeat to completion, retaining the image blocks as well as metadata.
  3. Save the completed document ID and revision. Make a small non-sensitive edit on iPad, wait for Synced, then call get_document_changes with that ID and revision in sinceRevision. Finish every continuation before accepting the new baseline.
  4. Compare the updated image with the iPad page. Do not put the expected new answer into the assistant prompt if you are checking whether it actually read the edit. Correct output alone does not prove a fresh fetch when the answer was already in chat context.

No output, timing or handwriting-accuracy result is promised by this sequence. Do not poll an idle account without the user's request.

Failures and recovery boundaries

HTTP 401 or insufficient scope
Use the host's normal account connection/reauthorization flow and ensure paper reading is granted. Do not substitute native write credentials. A valid login to the assistant is not by itself InkDraft authorization.
Registration does not complete
Stop before claiming compatibility. Record the non-secret error and client name for support. A public discovery endpoint or successful tool listing elsewhere does not establish that this host can register and read images. Gemini remains unestablished.
Empty or wrong document
Check the connected profile, the same InkDraft sign-in method, the open iPad document, and sync status. An empty account can legitimately return status: "empty" with no images. Do not interpret that as permission to search another account or local library.
revision_conflict
The document changed during an exact-revision or paginated read. Tool failures set isError: true; this code appears in the JSON text error. Discard partial or mixed-revision results. Restart get_full_document without a cursor for a complete baseline, or refresh metadata before a selected-page read.
resync_required
This is a changed-page result status, not an instruction to retry the old cursor. Discard the old baseline and perform a new full read. It can follow a document switch or a revision outside the supported incremental range.
Only text or only some pages arrive
Ensure the host exposes image blocks to a vision-capable model and follows continuation. Text-only metadata, one incomplete batch, and changed pages alone are not a whole-document read. A protocol-compatible client can still have model or UI limitations.
Earlier answers do not change
Expected: editing the iPad does not rewrite chat history. Wait for sync and explicitly request a fresh read. No success claim should depend on the assistant merely saying it read the update.

Evidence and limits

The tool names, arguments, image format, pagination and recovery paths above were checked against InkDraft's current document-tool and storage implementation on November 18, 2026, plus the existing setup documentation. The synthetic read/edit/reread demonstration and its eight-check receipt exercise four document tools in memory. They do not exercise the production profile tool, authentication, cloud sync, a physical iPad or any consumer model.

The MCP authorization specification explains the discovery and authorization mechanisms. The product's actual client coverage still needs per-client evidence. Set up a supported connection or report a non-secret interoperability problem.