# How to integrate Templated MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Templated MCP with Vercel AI SDK v6", "toolkit": "Templated", "toolkit_slug": "templated", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/templated/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/templated/framework/ai-sdk.md", "updated_at": "2026-05-12T10:28:08.798Z" } ``` ## Introduction This guide walks you through connecting Templated to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Templated agent that can generate invoice pdf from customer data, list all available image templates, clone existing certificate template for edits through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Templated account through Composio's Templated MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Templated with - [OpenAI Agents SDK](https://composio.dev/toolkits/templated/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/templated/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/templated/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/templated/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/templated/framework/codex) - [OpenClaw](https://composio.dev/toolkits/templated/framework/openclaw) - [Hermes](https://composio.dev/toolkits/templated/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/templated/framework/cli) - [Google ADK](https://composio.dev/toolkits/templated/framework/google-adk) - [LangChain](https://composio.dev/toolkits/templated/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/templated/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/templated/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/templated/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Templated integration - Using Composio's Tool Router to dynamically load and access Templated 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 Templated MCP server, and what's possible with it? The Templated MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Templated account. It provides structured and secure access to your templates and renders, so your agent can generate dynamic documents, manage templates, clone or tag designs, and retrieve render results on your behalf. - Automated document and image generation: Instantly have your agent render PDFs or images from any saved template, filling in dynamic variables to create invoices, certificates, or marketing materials. - Template management and organization: Let your agent list, retrieve, clone, or delete templates, keeping your template library organized and up-to-date without manual effort. - Dynamic tagging and categorization: Easily add or remove tags from templates, enabling smarter organization and fast searching for specific designs or document types. - Render tracking and retrieval: Ask your agent to list all renders for a template or fetch detailed information about a specific document render, making it simple to track document creation and usage history. - Account insights and validation: Have your agent retrieve account information to confirm API access, check account metadata, or audit usage details as needed. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `TEMPLATED_ADD_TAGS_TO_TEMPLATE` | Add Tags to Template | Tool to append new tags to an existing template without overwriting existing tags. Use when you already have the template ID and want to add additional tags. | | `TEMPLATED_CLONE_TEMPLATE_ACTION` | Clone Template | Tool to clone an existing template. Use after you have a template ID and want to duplicate it with a new name. Example: "Clone template tpl_123 as 'Copy of Template'". | | `TEMPLATED_COUNT_TEMPLATE_CLONES` | Count Template Clones | Tool to get the count of cloned templates for a specific source template. Use when you need to know how many clones exist for a particular template without retrieving the full list. | | `TEMPLATED_CREATE_FOLDER` | Create Folder | Tool to create a new folder for organizing templates and renders. Use when you need to organize templates into logical groups. | | `TEMPLATED_CREATE_RENDER` | Create Template Render | Create document renders from templates. Supports single/batch rendering with extensive customization. Returns a list of render objects (one per page for multi-page templates). | | `TEMPLATED_CREATE_TEMPLATE` | Create Template | Tool to create a new template with specified dimensions and layers. Use when you need to programmatically define a template with background images, text overlays, or shapes. | | `TEMPLATED_DELETE_FOLDER` | Delete Folder | Tool to delete a folder by its ID. The folder must be empty before deletion. Use when you have confirmed the folder ID and need to remove it permanently. | | `TEMPLATED_DELETE_RENDER` | Delete Render | Tool to delete a specific render by its ID. Use when you need to permanently remove a render and its associated output files. | | `TEMPLATED_DELETE_TEMPLATE` | Delete Template | Tool to delete a template by its unique ID. Use when you have confirmed the template ID and need to remove it permanently. | | `TEMPLATED_DUPLICATE_RENDER` | Duplicate Template Render | Tool to duplicate an existing render with the same settings and template. Use when you need to create a copy of a render. The duplicated render will use the same template and payload as the original. | | `TEMPLATED_GET_ACCOUNT_INFORMATION` | Get Account Information | Tool to retrieve account information, including email, name, team name, API usage statistics, and subscription plan. Use to check current API quota usage or verify API token validity. | | `TEMPLATED_LIST_ALL_TEMPLATES` | List All Templates | Tool to list all templates of a user. Use when you need to retrieve available templates with optional pagination. | | `TEMPLATED_LIST_FOLDER_RENDERS` | List Folder Renders | Tool to list all renders in a specific folder. Use when you need to retrieve all renders contained in a folder with optional pagination. | | `TEMPLATED_LIST_FOLDERS` | List Folders | Tool to list all folders in the account. Use when you need to retrieve available folders that help organize templates and renders. | | `TEMPLATED_LIST_FOLDER_TEMPLATES` | List Folder Templates | Tool to list all templates in a specific folder. Use when you need to retrieve templates contained in a folder. | | `TEMPLATED_LIST_FONTS` | List Fonts | Tool to list all available fonts including Google Fonts and user-uploaded custom fonts. Use when you need to retrieve the names and metadata of fonts available in the account. | | `TEMPLATED_LIST_GALLERY_TEMPLATES` | List Gallery Templates | Tool to list templates from the public gallery. Use when you need to browse available templates that can be cloned for use. | | `TEMPLATED_LIST_RENDERS` | List All Renders | Tool to list all renders in the account. Use when you need to retrieve all available renders for the authenticated user. | | `TEMPLATED_LIST_TEMPLATE_CLONES` | List Template Clones | Tool to list all cloned templates in the account. Use when you need to retrieve templates that were cloned from the gallery or other sources, with optional filtering by source template ID or external ID. | | `TEMPLATED_LIST_TEMPLATE_RENDERS` | List Template Renders | Tool to list all renders of a specific template. Use after obtaining a template ID when you need paginated render results. | | `TEMPLATED_LIST_UPLOADS` | List Uploads | Tool to list all uploaded images in the account. Returns upload details including URLs and metadata. Use when you need to retrieve available uploads with optional pagination. | | `TEMPLATED_MERGE_RENDERS` | Merge Template Renders | Tool to merge multiple renders into a single PDF output. Use when combining multiple images or pages into a unified document. When host=true, returns a URL to the hosted file. When host=false, returns the PDF binary for immediate download. | | `TEMPLATED_MOVE_RENDER_TO_FOLDER` | Move Render to Folder | Tool to move a render to a specific folder. Use when you need to organize renders by moving them into folders. | | `TEMPLATED_MOVE_TEMPLATE_TO_FOLDER` | Move Template to Folder | Tool to move a template to a folder. Use when you need to organize templates by moving them into specified folders. | | `TEMPLATED_REMOVE_TEMPLATE_TAGS` | Remove Template Tags | Tool to remove specific tags from a template. Use when you have a template ID and want to untag existing tags. | | `TEMPLATED_RETRIEVE_RENDER` | Retrieve Template Render | Tool to retrieve details of a specific render by its ID. Use after obtaining the render ID when you need details of a render. | | `TEMPLATED_RETRIEVE_TEMPLATE` | Retrieve Template | Tool to retrieve a single Template by its unique ID. Use after obtaining the template ID. | | `TEMPLATED_UPDATE_FOLDER` | Update Folder | Tool to update an existing folder's properties. Use when you need to change a folder's name or other attributes. | | `TEMPLATED_UPDATE_TEMPLATE` | Update Template | Tool to update an existing template including its properties and layers. Use replaceLayers=true to replace all layers (layers not in array will be removed), or false/omit to update existing layers and add new ones. | | `TEMPLATED_UPDATE_TEMPLATE_TAGS` | Update Template Tags | Tool to overwrite all tags on a template. Use when you need to replace the entire tag list for a specific template. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Templated MCP server is an implementation of the Model Context Protocol that connects your AI agent to Templated. It provides structured and secure access so your agent can perform Templated 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 Templated 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 Templated-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: ["templated"], }); 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 Templated 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 templated, 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 Templated 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: ["templated"], }); 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 templated, 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 Templated 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 Templated MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/templated/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/templated/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/templated/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/templated/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/templated/framework/codex) - [OpenClaw](https://composio.dev/toolkits/templated/framework/openclaw) - [Hermes](https://composio.dev/toolkits/templated/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/templated/framework/cli) - [Google ADK](https://composio.dev/toolkits/templated/framework/google-adk) - [LangChain](https://composio.dev/toolkits/templated/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/templated/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/templated/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/templated/framework/crew-ai) ## Related Toolkits - [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices. - [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze. - [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization. - [Affinda](https://composio.dev/toolkits/affinda) - Affinda is an AI-powered document processing platform that automates data extraction from resumes, invoices, and more. It streamlines document-heavy workflows by turning files into structured, actionable data. - [Agility cms](https://composio.dev/toolkits/agility_cms) - Agility CMS is a headless content management system for building and managing digital experiences across platforms. It lets teams update content quickly and deliver omnichannel experiences with ease. - [Algodocs](https://composio.dev/toolkits/algodocs) - Algodocs is an AI-powered platform that automates data extraction from business documents. It delivers fast, secure, and accurate processing without templates or manual training. - [Api2pdf](https://composio.dev/toolkits/api2pdf) - Api2Pdf is a REST API for generating PDFs from HTML, URLs, and documents using powerful engines like wkhtmltopdf and Headless Chrome. It streamlines document conversion and automation for developers and businesses. - [Aryn](https://composio.dev/toolkits/aryn) - Aryn is an AI-powered platform for parsing, extracting, and analyzing data from unstructured documents. Use it to automate document processing and unlock actionable insights from your files. - [Boldsign](https://composio.dev/toolkits/boldsign) - Boldsign is a digital eSignature platform for sending, signing, and tracking documents online. Organizations use it to automate agreements and manage legally binding workflows efficiently. - [Boloforms](https://composio.dev/toolkits/boloforms) - BoloForms is an eSignature platform built for small businesses, offering unlimited signatures, templates, and forms. It simplifies digital document signing and team collaboration at a predictable, fixed price. - [Box](https://composio.dev/toolkits/box) - Box is a cloud content management and file sharing platform for businesses. It helps teams securely store, organize, and collaborate on files from anywhere. - [Carbone](https://composio.dev/toolkits/carbone) - Carbone is a blazing-fast report generator that turns JSON data into PDFs, Word docs, spreadsheets, and more using flexible templates. It lets you automate document creation at scale with minimal code. - [Castingwords](https://composio.dev/toolkits/castingwords) - CastingWords is a transcription service specializing in human-powered, accurate transcripts via a simple API. Get seamless audio-to-text conversion for interviews, meetings, podcasts, and more. - [Cloudconvert](https://composio.dev/toolkits/cloudconvert) - CloudConvert is a powerful file conversion service supporting over 200 file formats. It streamlines converting, compressing, and managing documents, media, and more, all in one place. - [Cloudlayer](https://composio.dev/toolkits/cloudlayer) - Cloudlayer is a document and asset generation service for creating PDFs and images via API or SDKs. It lets you automate high-quality doc creation, saving dev time and reducing manual work. - [Cloudpress](https://composio.dev/toolkits/cloudpress) - Cloudpress is a content export tool for Google Docs and Notion. It automates publishing to your favorite Content Management Systems. - [Contentful graphql](https://composio.dev/toolkits/contentful_graphql) - Contentful graphql is a content delivery API that lets you access Contentful data using GraphQL queries. It gives you efficient, flexible ways to fetch and manage structured content for any digital project. - [Conversion tools](https://composio.dev/toolkits/conversion_tools) - Conversion Tools is an online service for converting documents between formats such as PDF, Word, Excel, XML, and CSV. It lets you automate complex document workflows with just a few clicks. - [Convertapi](https://composio.dev/toolkits/convertapi) - ConvertAPI is a robust file conversion service for documents, images, and spreadsheets. It streamlines programmatic format changes and lets developers automate complex workflows with a single API. - [Craftmypdf](https://composio.dev/toolkits/craftmypdf) - CraftMyPDF is a web-based service for designing and generating PDFs with templates and live data. It streamlines document creation by automating personalized PDFs at scale. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Templated MCP? With a standalone Templated MCP server, the agents and LLMs can only access a fixed set of Templated tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Templated 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 Templated tools. ### Can I manage the permissions and scopes for Templated while using Tool Router? Yes, absolutely. You can configure which Templated 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 Templated data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) ยท [Composio docs](https://docs.composio.dev/llms.txt)