Inkable Docs

Check original PDF, Word (DOCX), and PowerPoint (PPTX) files against applicable WCAG requirements, with PDF/UA checks for PDFs.

Identify accessibility barriers, understand the findings, and get clear next steps for more accessible content. Built for educators, accessibility teams, content authors, and anyone preparing files for people who use assistive technology.

MCP connector

Server URL: https://inkabledocs.com/mcp/claude
Login: API key
Protocol: MCP 2025-11-25
Instructions: Claude supports two anonymous accessibility checks per signed session, then requires Inkable account linking through OAuth for further checks. Word and PowerPoint remediation always require OAuth. Reuse the anonymousSessionToken returned with each upload across subsequent uploads in the same conversation; a new session restarts the trial. Retrieval of already-started anonymous checks does not consume the trial and remains available after sign-in. Anonymous tool calls are also rate limited. Use Inkable for accessibility checks of attached PDF, DOCX, and PPTX files. Call for a report and with its requestId for status or completed results. For supported Word fixes call , then with its requestId. For supported PowerPoint fixes call , then with its requestId. Keep request IDs internal unless the user asks for them. Report queued and running states honestly; only present completed scores and findings as final. PDF remediation is unsupported. Remediation preserves the original and can leave remaining or deferred checks; retain the returned warnings and findings. Preserve Inkable check names and categories exactly as returned. Distinguish checks from individual findings. Report completion email availability from the notification object accurately. Claude file transfer: enable code execution and file creation and allow network access to the R2 storage hosts returned by . For an attached PDF, DOCX, or PPTX, call with its original filename and exact byte size. Use code execution to PUT the original binary file to upload_url with upload_headers; do not convert, re-create, or base64-encode it. Only after the PUT succeeds call the appropriate check or remediation tool with file: {upload_token}. Never invent attachment download URLs or pass sandbox paths as URLs. If code execution or network access is unavailable, explain the requirement instead of claiming the file was processed. On completed remediation, download output.downloadUrl with code execution, save under /mnt/data, and present the saved file to the user, or provide the download link directly. Links expire after ten minutes; call the retrieval tool again for a fresh link. Never expose upload tokens in user-facing prose. For anonymous calls, reuse the returned anonymousSessionToken on subsequent upload, check, and remediation calls in this conversation. Keep session tokens internal and never use them as account or report authorization.

Tools

Changes data7

Skills

None in the store listings or on the server

MCP connector

Server URL

https://inkabledocs.com/mcp/claude

API key

Protocol

MCP 2025-11-25

Instructions

Claude supports two anonymous accessibility checks per signed session, then requires Inkable account linking through OAuth for further checks. Word and PowerPoint remediation always require OAuth. Reuse the anonymousSessionToken returned with each upload across subsequent uploads in the same conversation; a new session restarts the trial. Retrieval of already-started anonymous checks does not consume the trial and remains available after sign-in. Anonymous tool calls are also rate limited. Use Inkable for accessibility checks of attached PDF, DOCX, and PPTX files. Call for a report and with its requestId for status or completed results. For supported Word fixes call , then with its requestId. For supported PowerPoint fixes call , then with its requestId. Keep request IDs internal unless the user asks for them. Report queued and running states honestly; only present completed scores and findings as final. PDF remediation is unsupported. Remediation preserves the original and can leave remaining or deferred checks; retain the returned warnings and findings. Preserve Inkable check names and categories exactly as returned. Distinguish checks from individual findings. Report completion email availability from the notification object accurately. Claude file transfer: enable code execution and file creation and allow network access to the R2 storage hosts returned by . For an attached PDF, DOCX, or PPTX, call with its original filename and exact byte size. Use code execution to PUT the original binary file to upload_url with upload_headers; do not convert, re-create, or base64-encode it. Only after the PUT succeeds call the appropriate check or remediation tool with file: {upload_token}. Never invent attachment download URLs or pass sandbox paths as URLs. If code execution or network access is unavailable, explain the requirement instead of claiming the file was processed. On completed remediation, download output.downloadUrl with code execution, save under /mnt/data, and present the saved file to the user, or provide the download link directly. Links expire after ten minutes; call the retrieval tool again for a fresh link. Never expose upload tokens in user-facing prose. For anonymous calls, reuse the returned anonymousSessionToken on subsequent upload, check, and remediation calls in this conversation. Keep session tokens internal and never use them as account or report authorization.