# How to integrate Rkvst MCP with Mastra AI

```json
{
  "title": "How to integrate Rkvst MCP with Mastra AI",
  "toolkit": "Rkvst",
  "toolkit_slug": "rkvst",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/rkvst/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/rkvst/framework/mastra-ai.md",
  "updated_at": "2026-05-12T10:24:16.606Z"
}
```

## Introduction

This guide walks you through connecting Rkvst to Mastra AI using the Composio tool router. By the end, you'll have a working Rkvst agent that can download attachment from latest asset event, show details of asset by uuid, retrieve metadata for a specific event through natural language commands.
This guide will help you understand how to give your Mastra 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

- [OpenAI Agents SDK](https://composio.dev/toolkits/rkvst/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/rkvst/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/rkvst/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/rkvst/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/rkvst/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/rkvst/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/rkvst/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/rkvst/framework/cli)
- [Google ADK](https://composio.dev/toolkits/rkvst/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/rkvst/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/rkvst/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/rkvst/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/rkvst/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Set up your environment so Mastra, OpenAI, and Composio work together
- Create a Tool Router session in Composio that exposes Rkvst tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Rkvst tool definitions and attach them as a toolset
- Build a Mastra agent that can reason, call tools, and return structured results
- Run an interactive CLI where you can chat with your Rkvst agent

## What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.
Key features include:
- MCP Client: Built-in support for Model Context Protocol servers
- Toolsets: Organize tools into logical groups
- Step Callbacks: Monitor and debug agent execution
- OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

## 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `RKVST_DOWNLOAD_EVENT_ATTACHMENT` | Download Event Attachment | Tool to download an attachment from a specified Event on an Asset. Use when you have asset_uuid, event_uuid, and attachment uuid, and want the raw binary content. |
| `RKVST_GET_APP_REGISTRATION` | Get App Registration | Tool to retrieve details for a given App Registration ID. Use after obtaining the application's UUID to inspect its configuration and credentials. |
| `RKVST_GET_ASSET` | Get Asset | Tool to retrieve details for a given Asset. Use after you have its UUID; set `at_time` to get historical state. |
| `RKVST_GET_BLOB` | Get Blob | Tool to retrieve details of a Blob by ID. Use after confirming the Blob ID. |
| `RKVST_GET_EVENT` | Get Event | Tool to retrieve details of a specified Event. Use when you need full metadata, attributes, and associated trails of an existing event in DataTrails. |
| `RKVST_GET_IAM_SUBJECT` | Get IAM Subject | Tool to retrieve IAM subject details. Use when you need to fetch details for a specific IAM subject by its ID. |
| `RKVST_GET_MEMBER` | Get Member | Tool to retrieve details for a given Member ID. Use after obtaining a valid member UUID. |
| `RKVST_GET_PUBLIC_ASSET` | Get Public Asset | Tool to retrieve details for a public asset. Use when you have a public asset UUID. |
| `RKVST_GET_PUBLIC_ASSET_EVENT` | Get Public Asset Event | Tool to retrieve a specific public asset event. Use when you have public asset and event UUIDs. |
| `RKVST_GET_TENANCY` | Get Tenancy | Tool to retrieve details for a specific tenancy. Use after you have a tenancy ID. |
| `RKVST_LIST_APP_REGISTRATIONS` | List App Registrations | Tool to list all App Registrations. Use after acquiring a valid auth token to retrieve the applications registered under the tenant. |
| `RKVST_LIST_ASSET_EVENTS` | List Asset Events | Tool to list events for a specified asset. Use after confirming you have the asset UUID. |
| `RKVST_LIST_ASSETS` | List Assets | Tool to list all Assets with optional pagination and filters. Use when you need to retrieve asset metadata in batches via page_size and next_page_token. |
| `RKVST_LIST_IAM_SUBJECTS` | List IAM Subjects | Tool to list IAM subjects. Use when you need to retrieve provider-managed subjects, optionally filtering by display name. Use after authenticating the tenant. |
| `RKVST_LIST_MEMBERS` | List Members | Tool to list all tenant Members. Use when you need an overview of all users in your tenant. |
| `RKVST_LIST_PUBLIC_ASSET_EVENTS` | List Public Asset Events | Tool to list events for a specific public asset. Use when you need to retrieve the event history of a public asset after confirming its public availability. |
| `RKVST_LIST_PUBLIC_ASSETS` | List Public Assets | Tool to list all Public Assets. Use when you need to retrieve all assets made public. |
| `RKVST_LIST_TENANCIES` | List Tenancies | Tool to list all tenancies. Use after authenticating to retrieve the tenancy records available to the current tenant. |
| `RKVST_PROMOTE_MEMBER` | Promote Member | Tool to promote a tenant member to OWNER role. Use when you need to elevate permissions after verifying the member identity. |
| `RKVST_RETRIEVE_ASSET_ATTACHMENT_METADATA` | Retrieve asset attachment metadata | Tool to retrieve metadata for an attachment on a specified Asset. Use after obtaining asset and attachment UUIDs. |
| `RKVST_RETRIEVE_CAPS` | Retrieve Caps | Tool to retrieve resource limit quotas for a specified service. Use when checking quota availability before provisioning resources. |
| `RKVST_RETRIEVE_EVENT_ATTACHMENT_METADATA` | Retrieve Event Attachment Metadata | Tool to retrieve metadata for an attachment on a specified Event. Use when you have asset_uuid, event_uuid, and attachment uuid and need details like size, hash, and scan status. |
| `RKVST_SEARCH_EVENTS` | Search Events | Tool to search events matching filter criteria with pagination. Use when retrieving events by OData filter and paging through large result sets. |
| `RKVST_UPDATE_APP_REGISTRATION` | Update App Registration | Tool to update an application's display name or custom claims. Use after retrieving an App Registration to apply partial updates to its configuration. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Rkvst MCP server is an implementation of the Model Context Protocol that connects your AI agent to Rkvst. It provides structured and secure access so your agent can perform Rkvst operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Node.js 18 or higher
- A Composio account with an active API key
- An OpenAI API key
- Basic familiarity with TypeScript

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key.
- You need credits or a connected billing setup to use the models.
- Store the key somewhere safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.
- This key lets your Mastra agent talk to Composio and reach Rkvst through MCP.

### 2. Install dependencies

Install the required packages.
What's happening:
- @composio/core is the Composio SDK for creating MCP sessions
- @mastra/core provides the Agent class
- @mastra/mcp is Mastra's MCP client
- @ai-sdk/openai is the model wrapper for OpenAI
- dotenv loads environment variables from .env
```bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio
- COMPOSIO_USER_ID tells Composio which user this session belongs to
- OPENAI_API_KEY lets the Mastra agent call OpenAI models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import libraries and validate environment

What's happening:
- dotenv/config auto loads your .env so process.env.* is available
- openai gives you a Mastra compatible model wrapper
- Agent is the Mastra agent that will call tools and produce answers
- MCPClient connects Mastra to your Composio MCP server
- Composio is used to create a Tool Router session
```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
```

### 5. Create a Tool Router session for Rkvst

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "rkvst" for Rkvst access
- session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
```typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["rkvst"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Rkvst MCP URL:", composioMCPUrl);
```

### 6. Configure Mastra MCP client and fetch tools

What's happening:
- MCPClient takes an id for this client and a list of MCP servers
- The headers property includes the x-api-key for authentication
- getTools fetches the tool definitions exposed by the Rkvst toolkit
```typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
```

### 7. Create the Mastra agent

What's happening:
- Agent is the core Mastra agent
- name is just an identifier for logging and debugging
- instructions guide the agent to use tools instead of only answering in natural language
- model uses openai("gpt-5") to configure the underlying LLM
```typescript
const agent = new Agent({
    name: "rkvst-mastra-agent",
    instructions: "You are an AI agent with Rkvst tools via Composio.",
    model: "openai/gpt-5",
  });
```

### 8. Set up interactive chat interface

What's happening:
- messages keeps the full conversation history in Mastra's expected format
- agent.generate runs the agent with conversation history and Rkvst toolsets
- maxSteps limits how many tool calls the agent can take in a single run
- onStepFinish is a hook that prints intermediate steps for debugging
```typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        rkvst: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
```

## Complete Code

```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["rkvst"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      rkvst: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "rkvst-mastra-agent",
    instructions: "You are an AI agent with Rkvst tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { rkvst: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();
```

## Conclusion

You've built a Mastra AI agent that can interact with Rkvst through Composio's Tool Router.
You can extend this further by:
- Adding other toolkits like Gmail, Slack, or GitHub
- Building a web-based chat interface around this agent
- Using multiple MCP endpoints to enable cross-app workflows

## How to build Rkvst MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/rkvst/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/rkvst/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/rkvst/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/rkvst/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/rkvst/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/rkvst/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/rkvst/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/rkvst/framework/cli)
- [Google ADK](https://composio.dev/toolkits/rkvst/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/rkvst/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/rkvst/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/rkvst/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/rkvst/framework/crew-ai)

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand.
- [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.
- [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.
- [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses.
- [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research.
- [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction.
- [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation.
- [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Rkvst MCP?

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.

### Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra 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.

### Can I manage the permissions and scopes for Rkvst while using Tool Router?

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.

### How safe is my data with Composio Tool Router?

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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
