SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Rkvst MCP with Pydantic AI

Connect Pydantic AI to Rkvst MCP. Download attachment from latest asset event, show details of asset by uuid, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Rkvst logoRkvst
Api Key

Rkvst is an evidence management platform delivering reliable chain of custody for supply chain data. It ensures data authenticity, transparency, and trust across your digital records.

24 Tools

Introduction

This guide walks you through connecting Rkvst to Pydantic AI using the Composio tool router. By the end, you'll have a working Rkvst agent that can list assets and asset events, search events, download event attachments, browse public assets, and manage members through natural language commands.

This guide will help you understand how to give your Pydantic AI agent real control over a Rkvst account through Composio's Rkvst MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Rkvst with

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIAutoGen

TL;DR

Here's what you'll learn:
  • How to set up your Composio API key and User ID
  • How to create a Composio Tool Router session for Rkvst
  • How to attach an MCP Server to a Pydantic AI agent
  • How to stream responses and maintain chat history
  • How to build a simple REPL-style chat interface to test your Rkvst workflows

What is Pydantic AI?

Pydantic AI is a Python framework for building AI agents with strong typing and validation. It leverages Pydantic's data validation capabilities to create robust, type-safe AI applications.

Key features include:

  • Type Safety: Built on Pydantic for automatic data validation
  • MCP Support: Native support for Model Context Protocol servers
  • Streaming: Built-in support for streaming responses
  • Async First: Designed for async/await patterns

What is the Rkvst MCP server, and what's possible with it?

The Rkvst MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Rkvst account. It provides structured and secure access to your supply chain evidence data, so your agent can perform actions like retrieving asset details, verifying event authenticity, downloading attachments, and managing chain of custody records on your behalf.

  • Asset and event retrieval: Instantly fetch detailed information about assets, events, or public assets by their unique identifiers, including historical state data.
  • Chain of custody verification: Have your agent review event metadata and associated trails to ensure data authenticity and transparency throughout your supply chain.
  • Download evidence attachments: Let your agent securely download raw binary attachments associated with supply chain events for auditing or record-keeping.
  • App and member inspection: Effortlessly pull configuration and credential details for app registrations or retrieve member and IAM subject information to monitor access and permissions.
  • Tenancy and blob management: Retrieve tenancy details or access specific data blobs related to your supply chain records for better oversight and control.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account with an active API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio pydantic-ai python-dotenv

Install the required libraries.

What's happening:

  • composio connects your agent to external SaaS tools like Rkvst
  • pydantic-ai lets you create structured AI agents with tool support
  • python-dotenv loads your environment variables securely from a .env file
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your agent to Composio's API
  • USER_ID associates your session with your account for secure tool access
  • OPENAI_API_KEY to access OpenAI LLMs
5

Import dependencies

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()
What's happening:
  • We load environment variables and import required modules
  • Composio manages connections to Rkvst
  • MCPServerStreamableHTTP connects to the Rkvst MCP server endpoint
  • Agent from Pydantic AI lets you define and run the AI assistant
6

Create a Tool Router Session

python
async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Rkvst
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["rkvst"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")
What's happening:
  • We're creating a Tool Router session that gives your agent access to Rkvst tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
7

Initialize the Pydantic AI Agent

python
# Attach the MCP server to a Pydantic AI Agent
rkvst_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
agent = Agent(
    "openai:gpt-5",
    toolsets=[rkvst_mcp],
    instructions=(
        "You are a Rkvst assistant. Use Rkvst tools to help users "
        "with their requests. Ask clarifying questions when needed."
    ),
)
What's happening:
  • The MCP client connects to the Rkvst endpoint
  • The agent uses GPT-5 to interpret user commands and perform Rkvst operations
  • The instructions field defines the agent's role and behavior
8

Build the chat interface

python
# Simple REPL with message history
history = []
print("Chat started! Type 'exit' or 'quit' to end.\n")
print("Try asking the agent to help you with Rkvst.\n")

while True:
    user_input = input("You: ").strip()
    if user_input.lower() in {"exit", "quit", "bye"}:
        print("\nGoodbye!")
        break
    if not user_input:
        continue

    print("\nAgent is thinking...\n", flush=True)

    async with agent.run_stream(user_input, message_history=history) as stream_result:
        collected_text = ""
        async for chunk in stream_result.stream_output():
            text_piece = None
            if isinstance(chunk, str):
                text_piece = chunk
            elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                text_piece = chunk.delta
            elif hasattr(chunk, "text"):
                text_piece = chunk.text
            if text_piece:
                collected_text += text_piece
        result = stream_result

    print(f"Agent: {collected_text}\n")
    history = result.all_messages()
What's happening:
  • The agent reads input from the terminal and streams its response
  • Rkvst API calls happen automatically under the hood
  • The model keeps conversation history to maintain context across turns
9

Run the application

python
if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • The asyncio loop launches the agent and keeps it running until you exit

Complete Code

Here's the complete code to get you started with Rkvst and Pydantic AI:

python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStreamableHTTP

load_dotenv()

async def main():
    api_key = os.getenv("COMPOSIO_API_KEY")
    user_id = os.getenv("USER_ID")
    if not api_key or not user_id:
        raise RuntimeError("Set COMPOSIO_API_KEY and USER_ID in your environment")

    # Create a Composio Tool Router session for Rkvst
    composio = Composio(api_key=api_key)
    session = composio.create(
        user_id=user_id,
        toolkits=["rkvst"],
    )
    url = session.mcp.url
    if not url:
        raise ValueError("Composio session did not return an MCP URL")

    # Attach the MCP server to a Pydantic AI Agent
    rkvst_mcp = MCPServerStreamableHTTP(url, headers={"x-api-key": COMPOSIO_API_KEY})
    agent = Agent(
        "openai:gpt-5",
        toolsets=[rkvst_mcp],
        instructions=(
            "You are a Rkvst assistant. Use Rkvst tools to help users "
            "with their requests. Ask clarifying questions when needed."
        ),
    )

    # Simple REPL with message history
    history = []
    print("Chat started! Type 'exit' or 'quit' to end.\n")
    print("Try asking the agent to help you with Rkvst.\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "bye"}:
            print("\nGoodbye!")
            break
        if not user_input:
            continue

        print("\nAgent is thinking...\n", flush=True)

        async with agent.run_stream(user_input, message_history=history) as stream_result:
            collected_text = ""
            async for chunk in stream_result.stream_output():
                text_piece = None
                if isinstance(chunk, str):
                    text_piece = chunk
                elif hasattr(chunk, "delta") and isinstance(chunk.delta, str):
                    text_piece = chunk.delta
                elif hasattr(chunk, "text"):
                    text_piece = chunk.text
                if text_piece:
                    collected_text += text_piece
            result = stream_result

        print(f"Agent: {collected_text}\n")
        history = result.all_messages()

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've built a Pydantic AI agent that can interact with Rkvst through Composio's Tool Router. With this setup, your agent can perform real Rkvst actions through natural language. You can extend this further by:
  • Adding other toolkits like Gmail, HubSpot, or Salesforce
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows (for example, Gmail + Rkvst for workflow automation)
This architecture makes your AI agent "agent-native", able to securely use APIs in a unified, composable way without custom integrations.
TOOLS

Supported Tools

Every Rkvst action and event your agent gets out of the box.

Download Event Attachment

Tool to download an attachment from a specified Event on an Asset.

Get App Registration

Retrieve an App Registration's configuration and credentials by ID.

Get Asset

Retrieve a DataTrails asset by UUID.

Get Blob

Tool to retrieve details of a Blob by ID.

Get Event

Retrieve a DataTrails event by UUID to inspect its details and attributes.

Get IAM Subject

Retrieve details of a DataTrails IAM subject by its ID.

Get Member

Retrieve details for a DataTrails member by member UUID.

Get Public Asset

Tool to retrieve details for a public asset.

Get Public Asset Event

Tool to retrieve a specific public asset event.

Get Tenancy

Retrieve tenancy details by ID, or the authenticated current tenancy using self.

List App Registrations

List a page of App Registrations registered under the tenant.

List Asset Events

List events for a DataTrails asset by UUID, with pagination.

List Assets

List assets with optional pagination and filters.

List IAM Subjects

List IAM subjects, optionally filtering by display name.

List Members

List tenant members, optionally filtered by member state.

List Public Asset Events

Tool to list events for a specific public asset.

List Public Assets

List public assets found through a page of public events.

List Tenancies

Retrieve the current DataTrails tenancy's details as a list.

Promote Member

Promote a DataTrails tenant member to the OWNER role by member UUID to elevate their permissions.

Retrieve asset attachment metadata

Tool to retrieve metadata for an attachment on a specified Asset.

Retrieve Caps

Retrieve resource limit quotas for a specified service to check availability before provisioning.

Retrieve Event Attachment Metadata

Tool to retrieve metadata for an attachment on a specified Event.

Search Events

Retrieve DataTrails events with an optional result limit of 1 to 50.

Update App Registration

Partially update an app registration by ID, changing its display name, custom claims, or both.

FRAMEWORKS

How to build Rkvst MCP Agent with another framework

Claude Code logo

Claude Code

Use Rkvst MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Rkvst MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Rkvst MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Rkvst MCP with Claude Agent SDK

Grok Bot logo

Grok Bot

Use Rkvst MCP with Grok Bot

Codex logo

Codex

Use Rkvst MCP with Codex

OpenClaw logo

OpenClaw

Use Rkvst MCP with OpenClaw

Hermes logo

Hermes

Use Rkvst MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Rkvst MCP with Atomic Agent

Google ADK logo

Google ADK

Use Rkvst MCP with Google ADK

LangChain logo

LangChain

Use Rkvst MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Rkvst MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Rkvst MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Rkvst MCP with LlamaIndex

CrewAI logo

CrewAI

Use Rkvst MCP with CrewAI

AutoGen logo

AutoGen

Use Rkvst MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Rkvst MCP server, the agents and LLMs can only access a fixed set of Rkvst tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Rkvst and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Pydantic AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Rkvst tools.

Yes, absolutely. You can configure which Rkvst scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Rkvst data and credentials are handled as safely as possible.

Start with Rkvst.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Rkvst tool your agent needs.Free to start.

Start building