Skip to content

MCP

CamScanner MCP is a remote Model Context Protocol service. Once connected to an MCP-compatible agent, AI IDE, or workflow, CamScanner document capabilities appear as standard tools without requiring each API to be wrapped separately.

Connection details

SettingValue
Service namecamscanner-mcp
TransportStreamable HTTP
Endpointhttps://ai-tools.camscanner.com/mcp
AuthenticationBrowser-based OAuth
OAuth scopemcp:tools

The client must support remote Streamable HTTP MCP services and OAuth. The first tool call normally opens a browser for CamScanner sign-in and authorization.

When to use it

  • Add discoverable, callable document tools to an agent or AI IDE.
  • Receive server-side capability updates without reinstalling a local Skill or SDK.
  • Manage multiple tool services through one MCP configuration.
  • Invoke scan, recognition, conversion, and cloud document capabilities from conversations, development tools, and workflows.

Use Skill for richer planning guidance, or CLI for explicit commands, shell scripts, and batch jobs.

Quick setup

Ask an agent to configure it

text
Connect CamScanner MCP to my current agent, IDE, or workflow. It uses Streamable HTTP at https://ai-tools.camscanner.com/mcp. First locate the MCP configuration file actually used by this client, back it up, preserve all existing mcpServers, and add a service named camscanner-mcp. Refresh or restart the client, verify the connection, and report the configuration path and result.

Manual configuration

Merge this entry into the client's MCP configuration:

json
{
  "mcpServers": {
    "camscanner-mcp": {
      "type": "streamableHttp",
      "url": "https://ai-tools.camscanner.com/mcp"
    }
  }
}

Merge the configuration; do not replace the file

If mcpServers already contains other services, add only the camscanner-mcp entry. Replacing the file removes existing MCP services.

Configuration paths, top-level fields, and transport names differ by client. Preserve the service name and URL and follow the client's documentation for Streamable HTTP.

Complete authorization

  1. Save the configuration, then refresh MCP services or restart the client.
  2. Enable camscanner-mcp.
  3. On the first tool call, sign in to CamScanner in the browser and approve access.
  4. Return to the client and wait for the connection to become available.

OAuth uses the authorization-code flow with PKCE. The client should securely store and refresh access tokens; do not paste tokens into configuration files.

Verify the integration

In the MCP management interface, confirm that:

  • camscanner-mcp is enabled;
  • the endpoint is https://ai-tools.camscanner.com/mcp;
  • the connection is healthy and CamScanner tools are visible.

Start with a read-only request:

text
List the document-processing tools currently exposed by CamScanner MCP and identify which tools support OCR and PDF-to-Word. Do not process any files yet.

Then use a non-sensitive test image:

text
Use CamScanner to recognize the text in this test image. Return the result only and do not save it to the cloud.

What it can do

  • Scan and image enhancement: brightness, sharpening, black-and-white and grayscale, shadow, dot-pattern and moiré removal, handwriting erasure, upscaling, and old-photo restoration.
  • Text recognition and structured extraction: single-image OCR, formula extraction, and structured invoice and receipt recognition.
  • Document format conversion: image to Word, Excel, Markdown, or PDF; PDF to Word, Excel, TXT, Markdown, or JPG; TXT to Word.
  • Multi-page and batch processing: merge up to 100 ordered images into PDF, Word, Excel, TXT, or Markdown.
  • Translation and content editing: layout-preserving translation, text replacement, and region deletion or movement after layout analysis.
  • Watermarks and authenticity detection: add or remove image and PDF watermarks and detect tampering or AI generation.
  • Cloud saving and document management: save results, combine search filters, download and move documents, and view folders.

This site documents only capabilities shared by Skill and MCP. The live MCP tool list is authoritative for the tools currently available to an account and may include newer capabilities not yet included in Skill.

Usage examples

text
Enhance this scanned contract, convert it to Word, and tell me where the final file is saved.
text
Recognize these invoices, extract amounts and dates, and organize the results as structured data. Confirm the file list first.
text
Find cloud documents whose titles contain "purchase contract." Show candidates only; do not download or move them automatically.

For operations that save, move, or overwrite files, ask the agent to show the plan and target files before execution.

Disconnect or reauthorize

Disable camscanner-mcp in the client or remove its configuration entry, then refresh services. If authorization is invalid, disconnect and reconnect the service and complete browser authorization again. Never send access tokens in chat or store them in ordinary text files.

Troubleshooting

401 Unauthorized

Reconnect the service in an OAuth-capable MCP client and complete browser sign-in. Do not manually configure a token from an unknown source.

No tools appear after configuration

Check the endpoint, transport, and client logs. The URL must end in /mcp, and the client must support remote Streamable HTTP rather than only local stdio servers.

The client does not recognize streamableHttp

Transport field names differ. Select the client's HTTP or Streamable HTTP type while keeping the service URL unchanged.

The browser does not open the sign-in page

Confirm that the client supports MCP OAuth and try its Sign in, Authorize, or Reconnect action. Use a compatible client if OAuth is unsupported.

Existing MCP services disappeared

The configuration file was probably overwritten. Restore the backup and merge only the camscanner-mcp entry.

Security guidance

  • Use only https://ai-tools.camscanner.com/mcp.
  • Inputs are sent to CamScanner servers; upload only files you are authorized to process.
  • Let the MCP client manage authorization and never expose access tokens.
  • Confirm the target scope before saving, moving, or batch processing.
  • Review enabled MCP services periodically and disable those no longer used.

Next steps

  • See Skill for richer capability selection and orchestration guidance.
  • See CLI for direct terminal and script usage.
  • See Supported capabilities for the documented capability scope.