# How to integrate Templated MCP with Autogen ```json { "title": "How to integrate Templated MCP with Autogen", "toolkit": "Templated", "toolkit_slug": "templated", "framework": "AutoGen", "framework_slug": "autogen", "url": "https://composio.dev/toolkits/templated/framework/autogen", "markdown_url": "https://composio.dev/toolkits/templated/framework/autogen.md", "updated_at": "2026-05-12T10:28:08.798Z" } ``` ## Introduction This guide walks you through connecting Templated to AutoGen 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 AutoGen 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) - [Vercel AI SDK](https://composio.dev/toolkits/templated/framework/ai-sdk) - [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: - Get and set up your OpenAI and Composio API keys - Install the required dependencies for Autogen and Composio - Initialize Composio and create a Tool Router session for Templated - Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams - Configure an Autogen AssistantAgent that can call Templated tools - Run a live chat loop where you ask the agent to perform Templated operations ## What is AutoGen? Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows. Key features include: - Multi-Agent Systems: Build collaborative agent workflows - MCP Workbench: Native support for Model Context Protocol tools - Streaming HTTP: Connect to external services through streamable HTTP - AssistantAgent: Pre-built agent class for tool-using assistants ## 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 agents and assistants directly to Templated. Instead of manually wiring Templated APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely. 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 You will need: - A Composio API key - An OpenAI API key (used by Autogen's OpenAIChatCompletionClient) - A Templated account you can connect to Composio - Some basic familiarity with Autogen and Python async ### 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 dependencies Install Composio, Autogen extensions, and dotenv. What's happening: - composio connects your agent to Templated via MCP - autogen-agentchat provides the AssistantAgent class - autogen-ext-openai provides the OpenAI model client - autogen-ext-tools provides MCP workbench support ```bash pip install composio python-dotenv pip install autogen-agentchat autogen-ext-openai autogen-ext-tools ``` ### 3. Set up environment variables Create a .env file in your project folder. What's happening: - COMPOSIO_API_KEY is required to talk to Composio - OPENAI_API_KEY is used by Autogen's OpenAI client - USER_ID is how Composio identifies which user's Templated connections to use ```bash COMPOSIO_API_KEY=your-composio-api-key OPENAI_API_KEY=your-openai-api-key USER_ID=your-user-identifier@example.com ``` ### 4. Import dependencies and create Tool Router session What's happening: - load_dotenv() reads your .env file - Composio(api_key=...) initializes the SDK - create(...) creates a Tool Router session that exposes Templated tools - session.mcp.url is the MCP endpoint that Autogen will connect to ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Templated session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["templated"] ) url = session.mcp.url ``` ### 5. Configure MCP parameters for Autogen Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for. What's happening: - url points to the Tool Router MCP endpoint from Composio - timeout is the HTTP timeout for requests - sse_read_timeout controls how long to wait when streaming responses - terminate_on_close=True cleans up the MCP server process when the workbench is closed ```python # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) ``` ### 6. Create the model client and agent What's happening: - OpenAIChatCompletionClient wraps the OpenAI model for Autogen - McpWorkbench connects the agent to the MCP tools - AssistantAgent is configured with the Templated tools from the workbench ```python # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Templated assistant agent with MCP tools agent = AssistantAgent( name="templated_assistant", description="An AI assistant that helps with Templated operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) ``` ### 7. Run the interactive chat loop What's happening: - The script prompts you in a loop with You: - Autogen passes your input to the model, which decides which Templated tools to call via MCP - agent.run_stream(...) yields streaming messages as the agent thinks and calls tools - Typing exit, quit, or bye ends the loop ```python print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Templated related question or task to the agent.\n") # Conversation loop 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") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, "content") and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Templated session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["templated"] ) url = session.mcp.url # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Templated assistant agent with MCP tools agent = AssistantAgent( name="templated_assistant", description="An AI assistant that helps with Templated operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Templated related question or task to the agent.\n") # Conversation loop 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") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, 'content') and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You now have an Autogen assistant wired into Templated through Composio's Tool Router and MCP. From here you can: - Add more toolkits to the toolkits list, for example notion or hubspot - Refine the agent description to point it at specific workflows - Wrap this script behind a UI, Slack bot, or internal tool Once the pattern is clear for Templated, you can reuse the same structure for other MCP-enabled apps with minimal code changes. ## 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) - [Vercel AI SDK](https://composio.dev/toolkits/templated/framework/ai-sdk) - [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 Autogen? Yes, you can. Autogen 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)