Skip to main content
Connect the hosted Autype MCP server to Claude as a remote connector. You need an Autype account, an owner/admin role in the selected workspace, and Developer API access (an eligible plan or available qualifying automation credits). Exports and file-processing jobs consume existing automation credits. Autype supports Claude’s OAuth discovery, PKCE, Dynamic Client Registration, refresh tokens, and current remote MCP transport.

​
Add Autype from the directory

Connect Autype in Claude

Open Autype in the Claude connector directory. No server URL or API key to copy.
  1. Open Autype in Claude and choose Connect or Install.
  2. Sign in to Autype, select your organization, and review and approve the requested access.
  3. Start a conversation in Claude and enable Autype in the connectors menu if needed.
This works with Claude on the web and Claude Desktop using the same Claude account. Team or Enterprise administrators may need to enable the connector before members can connect their individual Autype accounts. If the listing is not visible yet, try again later or use the manual alternative below. The directory connection uses the dedicated /claude endpoint automatically.

​
Manual alternative

In Claude’s connector settings, add a custom remote connector named Autype with this URL, then complete the same Autype OAuth sign-in and consent flow:
No custom headers, API keys, or local configuration files are required. To remove access later, open Autype Settings → Connected Apps, select the Claude connection for the relevant workspace, and click Disconnect. You can reconnect it through Claude at any time.

​
Verify the connection

Ask Claude:
“Use Autype to list my projects. Do not create or modify anything.”
For a render test, ask:
“Use Autype to create a one-page A4 PDF called Claude connector test, then return its download link.”

​
What you can do

  • Create PDF, Word (DOCX) and OpenDocument (ODT) files from a brief.
  • Read and update documents in your authorized workspace.
  • Fill workspace templates and generate batches of up to 100 records, subject to your workspace limits and available credits.
  • Reuse existing workspace and built-in document styles.
  • Merge, split or compress PDFs, convert Word/OpenDocument files, and extract text or requested fields from supported attachments or files already stored in Autype.
Downloads are temporary signed links. PDF page previews cover one selected page and files up to 8 MB. DOCX and ODT exports have download links; a native document preview in Claude is not guaranteed. This connector does not include an embedded interactive app.

​
Files and permissions

Attach a supported file in Claude and ask Autype to process it. This requires Claude code execution with access to the original attachment and HTTPS network access to mcp.autype.com. Claude transfers the original bytes using a short-lived, single-use upload authorization; you do not copy an API key or upload the file a second time in Autype. The connector checks the file size and SHA-256 before accepting it into the connected workspace. Supported processing uploads include PDF, DOCX, ODT, Markdown, HTML and supported images, up to 30 MiB. Rendering images support PNG, JPEG and WebP up to 25 MiB. Availability and attachment limits in Claude can impose a lower limit. Raw CSV/XLSX imports are not part of this upload interface. If your Claude environment lacks original-file access or blocks the destination, the attachment workflow cannot run there. Ask your workspace administrator about the required domain access; no security restrictions are bypassed automatically. Existing Autype files can also be selected directly. Temporary uploads expire and may need to be uploaded again. An uncertain upload outcome should be checked in the file list before another attempt. Autype requests document read/write/render access, temporary-file management and permission to keep the connection active. Short-lived access tokens are renewed using rotating refresh tokens; routine token expiration does not require signing in again. Revoking the connection, losing workspace access or an expired/revoked refresh token can require reconnecting. The connector does not buy credits, change subscriptions, send email, sign contracts, manage templates or delete workspace documents. Updating document content does modify the selected document. DOCX inspection can create temporary image assets for embedded pictures. Batch and processing jobs can consume credits even though they leave the source document unchanged; duplicate submissions can create duplicate charges.

​
Data and troubleshooting

Only the arguments supplied to an Autype tool and the selected workspace data needed for that operation are processed by Autype. Requested document contents, variables and extracted fields can contain personal data. Handle confidential inputs according to your organization’s rules. See the privacy policy and terms for storage, processing and service terms. If a permission check fails, verify the workspace, role and granted scopes. If a file or download expired, refresh its status or upload the source again. A new render consumes credits. Extraction results should be checked against the source. For help, use Autype support.

​
Existing connections and Claude Code

Existing connections at https://mcp.autype.com/mcp remain supported with their broader legacy tool set. The directory connector uses the focused /claude endpoint. Claude Code can also connect using Streamable HTTP. See Claude Code (CLI) for configuration and the legacy API-key fallback. See Anthropic’s connector guide for current directory controls and workspace policies.