How to Use the Ugosign MCP in LlamaIndex

Q: How do I query document history using Ugosign and LlamaIndex?

You first use listdocuments to find the IDs, then pass those to getdocument. Indexing these results lets you build a semantic search over historical files.

Q: Can Ugosign and LlamaIndex help with compliance checks?

Yes. You can use getorganization to pull regulatory context, then index it alongside signature requests. This grounds your answers in real-world compliance data.

Q: How do I track all active requests using Ugosign and LlamaIndex?

Start by calling listsignaturerequests. The output provides a list you can index. If you need details on one, use getsignaturerequest.

Index Ugosign API data into a searchable knowledge base for LlamaIndex.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Ugosign MCP to LlamaIndex

Create your Vinkius account to connect Ugosign to LlamaIndex 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

Setup Ugosign with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Search Document Histories

Use `list_documents` to get metadata, and then use `get_document` to pull the actual details. Indexing this output lets you semantically search past files, answering questions like 'What was in that contract last quarter?' The results from these calls become part of your unified index. You're not just calling an API; you're building a searchable knowledge base from it.

Query Signature Request Status

When you call `list_signature_requests`, the resulting status list can be indexed. Then, when querying, you get answers grounded in actual API data about pending signatures, not just guesses. This is huge for RAG apps. You combine live signature data with static documents into one queryable source.

Cross-Reference Signatories and Files

Combine context by calling `get_organization` to pull company profiles, and then use that info when creating a request via `create_signature_request`. The entire sequence is indexed. Your index now understands relationships: 'Which signature requests involve an organization with X details?' You get answers based on real data.

Setup guide

Set up Ugosign MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Ugosign MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Ugosign tools.",
)
response = await agent.run("List recent Ugosign data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Ugosign. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

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

Connect Ugosign now

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 LlamaIndex

You first use `list_documents` to find the IDs, then pass those to `get_document`. Indexing these results lets you build a semantic search over historical files.

Yes. You can use `get_organization` to pull regulatory context, then index it alongside signature requests. This grounds your answers in real-world compliance data.

The server touches document details and signature request data. Indexing these two types of information is key to answering detailed, complex questions about signing workflows.

Start by calling `list_signature_requests`. The output provides a list you can index. If you need details on one, use `get_signature_request`.

Absolutely. You can chain calls like listing documents and then using the resulting data to create a signature request. Indexing all these steps gives you maximum context for your RAG application.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript