How to Use the Sproof MCP in Google ADK

Q: How do I audit a process using Sproof and Google ADK?

You call listaudittrail with the request ID. This immediately gives your agent a full, immutable history of actions taken on that specific signature request.

Q: What data does Sproof and Google ADK touch regarding user profiles?

The server exposes getprofile. Your agent uses this to fetch the current account profile details. This is necessary for verifying permissions before allowing a signing action.

Q: How do I check all existing signature requests with Sproof and Google ADK?

Use the listsignaturerequests tool. It gives your agent an overview of every request currently managed by the platform, letting you prioritize which ones need attention.

Q: If I'm building with Sproof and Google ADK, how do I manage signers?

The listsigners tool lets your agent pull a list of all required participants for any given signature request. This confirms who needs to act.

Q: If I'm building with Sproof and Google ADK, how do I confirm document details?

Run getdocument on the file ID. The agent will get all necessary metadata about that document, confirming its status or origin.

Build enterprise signing agents using Google ADK with Sproof's data tools.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Sproof MCP to Google ADK

Create your Vinkius account to connect Sproof to Google ADK 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 Sproof with Google ADK

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Initiating and Managing Signatures

To kick off a new workflow, your agent calls `create_signature_request`. It accepts all necessary inputs as a JSON string payload. This function is the starting point for any signing process. The agent can also get details on an existing request using `get_signature_request`. This lets you track progress and confirm which steps are complete without having to guess.

Document Retrieval and Context

Before running any signing process, the agent needs the right documents. Calling `list_documents` gives a comprehensive view of available files in your system. You know exactly what’s there. Furthermore, using `get_document` pulls all the specific details you need—it's better than just knowing the file name because it includes metadata that matters.

Workflow Auditing and Contact Management

Auditing is critical in enterprise settings. The `list_audit_trail` tool provides a complete, chronological log for any signature request, detailing every action taken by anyone. This builds the full compliance story. If you need to manage participants, run `list_contacts`. You'll see every contact record available, or use `create_contact` to add new people who will participate in signing.

Setup guide

Set up Sproof MCP in Google ADK

Prerequisites

Python 3.10+ installed
google-adk package (pip install google-adk)
Active Vinkius subscription with a valid endpoint token

1

Install Google ADK

Run pip install google-adk to install the Agent Development Kit. MCP support is included via the McpToolset class.
2

Connect via SSE transport

Use McpToolset.from_server() with SseServerParams pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create an LlmAgent

Pass the returned mcp_tools list directly to LlmAgent(tools=mcp_tools). The ADK maps each MCP tool to a native Gemini function call — no manual schema definitions required.
4

Run with any Gemini model

The agent works with any Gemini model (gemini-2.0-flash, gemini-2.5-pro, etc.). Copy the full example on the right to get started with Sproof tools in your ADK agent.

agent.py

from google.adk.agents import LlmAgent
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import SseServerParams

# Connect to the MCP via SSE
mcp_tools, exit_stack = await McpToolset.from_server(
    connection_params=SseServerParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    )
)

# Create your agent with auto-discovered tools
agent = LlmAgent(
    name="Sproof_agent",
    model="gemini-2.0-flash",
    instruction="You have access to Sproof tools via MCP.",
    tools=mcp_tools,
)

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 Sproof. 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 Sproof 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 Sproof MCP in Google ADK

You call `list_audit_trail` with the request ID. This immediately gives your agent a full, immutable history of actions taken on that specific signature request.

The server exposes `get_profile`. Your agent uses this to fetch the current account profile details. This is necessary for verifying permissions before allowing a signing action.

Use the `list_signature_requests` tool. It gives your agent an overview of every request currently managed by the platform, letting you prioritize which ones need attention.

The `list_signers` tool lets your agent pull a list of all required participants for any given signature request. This confirms who needs to act.

Run `get_document` on the file ID. The agent will get all necessary metadata about that document, confirming its status or origin.

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