# How to integrate Dock certs MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Dock certs MCP with Vercel AI SDK v6", "toolkit": "Dock certs", "toolkit_slug": "dock_certs", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/dock_certs/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/dock_certs/framework/ai-sdk.md", "updated_at": "2026-05-12T10:09:01.376Z" } ``` ## Introduction This guide walks you through connecting Dock certs to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Dock certs agent that can list all credentials issued this month, delete a credential by its id, create a webhook for credential updates through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Dock certs account through Composio's Dock certs MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Dock certs with - [OpenAI Agents SDK](https://composio.dev/toolkits/dock_certs/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/dock_certs/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/dock_certs/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/dock_certs/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/dock_certs/framework/codex) - [OpenClaw](https://composio.dev/toolkits/dock_certs/framework/openclaw) - [Hermes](https://composio.dev/toolkits/dock_certs/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/dock_certs/framework/cli) - [Google ADK](https://composio.dev/toolkits/dock_certs/framework/google-adk) - [LangChain](https://composio.dev/toolkits/dock_certs/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/dock_certs/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/dock_certs/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/dock_certs/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Dock certs integration - Using Composio's Tool Router to dynamically load and access Dock certs tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## What is the Dock certs MCP server, and what's possible with it? The Dock certs MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Dock certs account. It provides structured and secure access to your verifiable credentials and decentralized identity management, so your agent can perform actions like issuing credentials, managing API keys, retrieving credential details, and automating webhook notifications on your behalf. - Instant credential issuance and management: Easily have your agent issue new verifiable credentials, retrieve detailed credential metadata, or delete outdated credentials as needed. - Secure API key lifecycle management: Direct your agent to create, list, retrieve, or delete API keys, ensuring secure programmatic access for your organization. - Automated webhook setup and oversight: Let your agent create or delete webhook endpoints, so you can receive real-time event notifications from Dock certs to your own systems. - Credential retrieval and decryption: Ask your agent to fetch specific credentials by ID, with options for full retrieval if protected by a password, ensuring secure and flexible access. - Tag and metadata cleanup: Enable your agent to delete obsolete tags or credential metadata, keeping your Dock certs environment organized and up to date. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `DOCK_CERTS_CREATE_API_KEY` | Create API Key | Tool to create an API key. Use when you need to generate a new API key with optional alias and IP allowlist. | | `DOCK_CERTS_CREATE_WEBHOOK` | Create Webhook | Tool to create a webhook endpoint. Use when you need Dock.io to push event notifications to your service. | | `DOCK_CERTS_DELETE_API_KEY` | Delete API Key | Tool to delete a specific API key. Use after confirming the API key's ID via list_api_keys. | | `DOCK_CERTS_DELETE_CREDENTIAL` | Delete Credential | Tool to delete a verifiable credential. Use after confirming the credential is no longer needed. | | `DOCK_CERTS_DELETE_TAG` | Delete Tag | Tool to delete a specific tag. Use when you have a tag ID and want to permanently remove it. | | `DOCK_CERTS_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a specific webhook. Use after confirming the webhook's ID via list_webhooks. | | `DOCK_CERTS_RETRIEVE_API_KEY` | Retrieve API Key | Tool to retrieve details of an API key. Tries single-key endpoint first, then falls back to listing and filtering. | | `DOCK_CERTS_RETRIEVE_API_KEYS` | Retrieve API Keys | Tool to list all API keys. Use when you need to retrieve all API keys for the authenticated account. | | `DOCK_CERTS_RETRIEVE_CREDENTIAL` | Retrieve Credential | Tool to retrieve a verifiable credential by its unique ID. If a password was used to persist it, include the same password to decrypt and return the full credential. Otherwise, only metadata is returned. | | `DOCK_CERTS_RETRIEVE_CREDENTIALS` | Retrieve Credentials | Tool to retrieve a list of credential metadata. Use when you need to collect credential details with optional pagination or filtering after authentication. | | `DOCK_CERTS_RETRIEVE_DID` | Retrieve DID Document | Tool to retrieve a DID Document by its DID. Use after you have a valid DID to resolve and inspect its DID Document. | | `DOCK_CERTS_RETRIEVE_REGISTRIES` | Retrieve Revocation Registries | Tool to retrieve a list of revocation registries. Use when you need to list all registries created by the authenticated account with optional pagination and filtering. | | `DOCK_CERTS_RETRIEVE_WEBHOOK` | Retrieve Webhook | Tool to retrieve a specific webhook's details. Use after confirming you have a valid webhook ID. | | `DOCK_CERTS_RETRIEVE_WEBHOOKS` | Retrieve Webhooks | Tool to list configured webhooks. Use when you need to retrieve all webhook endpoints configured for your account. | | `DOCK_CERTS_VERIFY` | Verify Credential or Presentation | Tool to verify a verifiable credential or presentation. Use after receiving a credential or presentation from an issuer. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Dock certs MCP server is an implementation of the Model Context Protocol that connects your AI agent to Dock certs. It provides structured and secure access so your agent can perform Dock certs 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 you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 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'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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Dock certs tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Dock certs-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["dock_certs"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Dock certs tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to dock_certs, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Dock certs tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript 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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n๐Ÿ‘‹ Session ended."); 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 { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) 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, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["dock_certs"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to dock_certs, like summarize my last 5 emails, send an email, etc... :)))\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({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n๐Ÿ‘‹ Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Dock certs agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Dock certs MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/dock_certs/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/dock_certs/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/dock_certs/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/dock_certs/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/dock_certs/framework/codex) - [OpenClaw](https://composio.dev/toolkits/dock_certs/framework/openclaw) - [Hermes](https://composio.dev/toolkits/dock_certs/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/dock_certs/framework/cli) - [Google ADK](https://composio.dev/toolkits/dock_certs/framework/google-adk) - [LangChain](https://composio.dev/toolkits/dock_certs/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/dock_certs/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/dock_certs/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/dock_certs/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Dock certs MCP? With a standalone Dock certs MCP server, the agents and LLMs can only access a fixed set of Dock certs tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Dock certs and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 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 Dock certs tools. ### Can I manage the permissions and scopes for Dock certs while using Tool Router? Yes, absolutely. You can configure which Dock certs 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 Dock certs data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)