4,500+ servers built on MCP Fusion
Vinkius
Ugosign logo
Vinkius
Claude Desktop logo

How to Use the Ugosign MCP in Claude

Handle eSignatures and Docs from anywhere with Claude Desktop.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Ugosign MCP on Cursor AI Code Editor MCP Client Ugosign MCP on Claude Desktop App MCP Integration Ugosign MCP on OpenAI Agents SDK MCP Compatible Ugosign MCP on Visual Studio Code MCP Extension Client Ugosign MCP on GitHub Copilot AI Agent MCP Integration Ugosign MCP on Google Gemini AI MCP Integration Ugosign MCP on Lovable AI Development MCP Client Ugosign MCP on Mistral AI Agents MCP Compatible Ugosign MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Claude Desktop

Connect Ugosign MCP to Claude Desktop

Create your Vinkius account to connect Ugosign to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Manage Signature Requests in Code

To start a new signature process, just call `create_signature_request`. This tool takes data as a JSON string so you can pass exactly what's needed. You don't have to leave the chat window or context switch to handle initiation. You can also check status updates by calling `list_signature_requests`. It gives you an overview of every ongoing signing workflow, letting you track who signed and when.

List Documents and Get Details

`list_documents` shows you a catalog of files stored in the system. You can then use `get_document` to fetch specific details about any listed document. This is helpful for checking compliance status before sending it out. If you need more context on the organization involved, calling `get_organization` gives you key details. It's a quick way to verify who the signer needs to be.

Check Status and Details

Need to know what happened with an old request? The tool `get_signature_request` pulls all the specific details for a single signature workflow. This helps you debug or confirm historical data. Furthermore, if you're running into trouble finding files, `list_documents` gives you the necessary list of available documents to work from.

Setup guide

Set up Ugosign MCP in Claude Web or Desktop

  1. 1

    Open Claude Settings

    Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

  2. 2

    Add Custom Connector

    Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

  3. 3

    Start a conversation

    Open a new chat. The Ugosign MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Ugosign MCP in Claude Desktop

You call the `create_signature_request` tool directly within your chat. Your AI client sends the required JSON data, and the server handles the initiation of the eSignature process. It works whether you're using the native Desktop app or the web connector.
Yes, simply call `list_documents`. The tool returns a list of every document available through the MCP Server. This is useful for checking which documents are ready to be signed or reviewed.
This server handles signature request details and general organization information via tools like `get_signature_request` and `get_organization`. Specifically, it touches metadata related to the signing workflow.
Since you can connect the remote MCP server URL in the web browser version, any user across Free, Pro, Max, Team, or Enterprise plans gets access. The tool relies on standard HTTPS connectivity to run.
Absolutely. If you use the native Desktop App, you can configure a local stdio server. This lets developers test the tools—like `get_document`—against local databases or dev servers without needing external network access.

Start using the Ugosign MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 6 tools

We've already built the connector for Ugosign. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.