Create and revise
Build documents in controlled stages, edit focused regions, manage variables, and preserve surrounding structure.
Remote MCP server for documents
Give your AI agent a professional document engine.
Connect Claude, ChatGPT, Codex, Cursor, Gemini, GitHub Copilot, or any compatible AI client to Autype. Create, revise, validate, render, and deliver real business documents without leaving the conversation.
One URL. Secure OAuth. No API key to paste into your AI client.
Connect Autype to your AI
Streamable HTTP · secure remote connection
1
Copy the Autype MCP URL
This is the only server address your compatible AI client needs.
2
Open Settings → Connectors
Add a custom connector in Claude or Claude Desktop, name it Autype, and paste the server URL.
3
Sign in, approve, and start
Autype opens a secure OAuth screen. Review the requested permissions, approve them, and ask your agent to create or inspect a document.
Create an accountAlready have Autype? OAuth signs you into your existing workspace.Detailed setup and troubleshooting
Connect in minutesCopy one remote MCP URL and authorize your Autype account.
Permission-scoped OAuthReview access before connecting and revoke clients at any time.
Real document outputThe same engine produces final PDF, DOCX, ODT, and page images.
Documents, not text snippets
Your agent can finish the document work.
Autype exposes focused tools for the complete document lifecycle, backed by the same structured model, renderer, and workspace resources as the web editor.
Apply approved design
Reuse system or workspace templates, document styles, reusable blocks, records, and authorized media.
Render and inspect
Generate the real pages, inspect page images, validate references, and catch output issues before delivery.
Export and transform
Deliver PDF, DOCX, ODT, or page images and run focused conversion, protection, and PDF operations.
One request, a controlled workflow
The agent plans. Autype builds and verifies.
Your AI stays in the interface you already use. Autype supplies the document-specific model, tools, resources, rendering, and export pipeline behind it.
Builder Mode keeps long document creation stable and token-efficient.
Targeted reads and patches avoid rewriting unrelated document regions.
Readiness checks and page renders keep the final file reviewable.
Your prompt
Create a branded quarterly report from these figures, reuse our approved style, check the final pages, and return PDF and DOCX.
Plan sections
Reuse style
Render and verify
Quarterly report · ready
Validated structure · final pages inspected
PDFDOCXImages
Use what your team already approved
The agent works with your document system, not around it.
MCP gives the model concise access to the right resources instead of forcing it to recreate branding, boilerplate, data, or file logic in every prompt.
Templates
Discover system templates or fill organization-owned templates.
Document styles
Apply reusable typography, page design, headers, footers, and brand rules.
Reusable blocks
Insert approved clauses, sections, tables, and recurring content.
Records and variables
Bind structured business data without copying it into every instruction.
Authorized files
Use scoped source files and media that the connected user can access.
Document tools
Convert, merge, split, watermark, protect, inspect, and prepare outputs.
Secure by default
A remote connection you can understand and control.
Autype uses browser-based OAuth for remote MCP clients. Credentials stay out of chat configuration, and access remains tied to the user and organization that approved it.
OAuth instead of pasted secrets
Sign in through Autype and never expose your password or API key to the AI client.
Explicit scopes
The authorization screen shows document, resource, file, and rendering permissions before approval.
Revocable clients
Disconnect OAuth clients centrally from your Autype account when access is no longer needed.
Workspace boundaries
Organization permissions, file access, and resource visibility remain enforced for every tool call.
MCP FAQ
Everything needed before you connect.
The practical answers for adding Autype to an AI client and using it safely.
Do I need an Autype API key?+
No. Compatible remote MCP clients use OAuth. Add the server URL, sign in to Autype in the browser, review the permissions, and approve the connection.
Which AI clients work with Autype MCP?+
Autype uses Streamable HTTP and standard remote MCP authentication. It works with compatible clients such as Claude, ChatGPT custom apps, Codex, Gemini clients, GitHub Copilot, Cursor, Windsurf, and other MCP-capable tools. Exact availability can depend on the client plan and version.
Can the agent edit existing documents?+
Yes. It can list and read authorized documents, retrieve focused chunks, apply revision-aware changes, use resources, render the result, and export the final document.
Can I control what the client may access?+
Yes. OAuth scopes, Autype organization permissions, resource ownership, and file authorization are enforced together. Review the requested scopes before approving a client.
How is MCP usage billed?+
Access follows your Autype plan. Metered headless operations use Automation Credits; current allowances and operation costs are shown on the pricing page and in the Engine usage view.
Can I disconnect the client later?+
Yes. Remove the connector in your AI client and revoke the OAuth client from Autype. Refresh tokens and future access are then invalidated.
Give your agent professional document tools.
Connect Autype once, keep working in your preferred AI client, and deliver structured documents instead of copied text.
Remote MCP · OAuth authorization · no API key in the client