SDK, Cloud or MCP?

View as MarkdownMarkdown

Set up your AI agent

Give your coding agent live access to the GroupDocs documentation and API reference through the GroupDocs Docs MCP server — no install, no API key. Learn more

claude mcp add --transport http groupdocs-docs https://docs.groupdocs.com/mcp

Also process documents locally

The GroupDocs.Signature MCP server lets your agent work with files on your machine; they are never uploaded. It needs the .NET 10 SDK or Docker.

claude mcp add groupdocs-signature -- dnx GroupDocs.Signature.Mcp --yes
Folders, licensing and more →

GroupDocs.Signature reaches Python code in three ways. They share the signing engine but differ in where the documents are processed and who writes the code. This page helps you pick one.

At a glance

GroupDocs.Signature for Python via .NET (SDK)GroupDocs.Signature CloudGroupDocs.Signature MCP server
What it isA Python package (pip install groupdocs-signature-net)A hosted REST API with a Python SDKA Model Context Protocol server with signing tools
Who calls itYour Python codeYour code, over HTTPSAn AI agent (Claude, Cursor, GitHub Copilot and other MCP clients)
Where documents goStay on your machine or serverUploaded to GroupDocs Cloud storageStay on the machine that runs the server
Internet accessNot neededRequiredNot needed once installed
What you can doEvery signature type and operation: sign, search, verify, update, delete, previews, document infoSigning, verification and search through REST endpointsSign with text, QR code, barcode or digital signatures, verify signatures, read QR codes and barcodes
Runs onWindows x64, Linux x64, macOS 12+ (Intel and Apple Silicon); Python 3.5 - 3.14Any platform that can make HTTPS calls.NET server, or its Docker image; a Python launcher is planned
LicensingGroupDocs.Signature license (evaluation mode without one)GroupDocs Cloud subscriptionGroupDocs.Signature license

Choose the SDK when

  • Documents must not leave your environment (compliance, air-gapped systems, on-premise deployments).
  • You need the whole API: all eight signature types, appearance control, previews, search, update and delete.
  • You sign many documents in batch jobs and want no network round trips.

Start with Installation and the Quick Start Guide.

Choose GroupDocs.Signature Cloud when

  • You prefer a managed service to installing and updating a package.
  • Your application already works with cloud storage, or runs where installing native packages is not possible.

See GroupDocs.Signature Cloud for Python and its documentation.

Choose the MCP server when

  • An AI agent should sign or check documents itself, as a step in a conversation or a workflow, without you writing signing code.
  • You want local processing for an agent: the server runs next to your project, and documents stay on that machine.

See the GroupDocs.Signature MCP server documentation.

Combine them

  • SDK + documentation MCP server: when an AI coding assistant writes Python code against this package, connect it to the documentation MCP server and let it read the AGENTS.md shipped inside the package. See Agents and LLM Integration.
  • SDK in production, MCP server for prototyping: let an agent try signing scenarios through the MCP server, then implement the chosen workflow with the SDK.