SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Templated MCP with Claude Agent SDK

Connect Claude Agent SDK to Templated MCP. Generate invoice pdf from customer data, list all available image templates, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Templated logoTemplated
Api Key

Templated is a platform for designing templates and automating the creation of images and PDFs via API. It lets you dynamically generate branded content and documents at scale.

30 Tools

Introduction

This guide walks you through connecting Templated to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Templated agent that can generate images and PDFs from templates, create and clone templates, organize folders, tag templates, and merge renders through natural language commands.

This guide will help you understand how to give your Claude Agent 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

Claude CodeClaude CoworkOpenAI Agents SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Templated
  • Configure an AI agent that can use Templated as a tool
  • Run a live chat session where you can ask the agent to perform Templated operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

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

What is Composio SDK?

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

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

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

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

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Templated account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Templated functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Templated
  const session = await composio.create(USER_ID, {
    toolkits: ['templated'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Templated
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Templated tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Templated
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Templated and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['templated']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Templated tools via Composio.',
    maxTurns: 10,
  };

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

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Templated through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

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

Add Tags to Template

Tool to append new tags to an existing template without overwriting existing tags.

Clone Template

Tool to clone an existing template.

Count Template Clones

Tool to get the count of cloned templates for a specific source template.

Create Folder

Tool to create a new folder for organizing templates and renders.

Create Template Render

Create document renders from templates.

Create Template

Tool to create a new template with specified dimensions and layers.

Delete Folder

Tool to delete a folder by its ID.

Delete Render

Tool to delete a specific render by its ID.

Delete Template

Tool to delete a template by its unique ID.

Duplicate Template Render

Tool to duplicate an existing render with the same settings and template.

Get Account Information

Tool to retrieve account information, including email, name, team name, API usage statistics, and subscription plan.

List All Templates

Tool to list all templates of a user.

List Folder Renders

List renders in a specified folder by ID, with optional pagination.

List Folders

List folders in the account, with optional name filtering and pagination.

List Folder Templates

List templates in a specified folder with optional pagination.

List Fonts

Tool to list all available fonts including Google Fonts and user-uploaded custom fonts.

List Gallery Templates

Tool to list templates from the public gallery.

List All Renders

List renders in the account with optional pagination.

List Template Clones

List cloned templates in the account with optional pagination and filtering by source template ID or external ID.

List Template Renders

List renders for a specified template by ID, with optional pagination.

List Uploads

List uploaded images in the account with optional search, tag filtering and pagination.

Merge Template Renders

Tool to merge multiple renders into a single PDF output.

Move Render to Folder

Tool to move a render to a specific folder.

Move Template to Folder

Tool to move a template to a folder.

Remove Template Tags

Tool to remove specific tags from a template.

Retrieve Template Render

Tool to retrieve details of a specific render by its ID.

Retrieve Template

Tool to retrieve a single Template by its unique ID.

Update Folder

Update the name of an existing folder by its ID.

Update Template

Tool to update an existing template including its properties and layers.

Update Template Tags

Tool to overwrite all tags on a template.

FRAMEWORKS

How to build Templated MCP Agent with another framework

Claude Code logo

Claude Code

Use Templated MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Templated MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Templated MCP with OpenAI Agents SDK

Codex logo

Codex

Use Templated MCP with Codex

OpenClaw logo

OpenClaw

Use Templated MCP with OpenClaw

Hermes logo

Hermes

Use Templated MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Templated MCP with Atomic Agent

Google ADK logo

Google ADK

Use Templated MCP with Google ADK

LangChain logo

LangChain

Use Templated MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Templated MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Templated MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Templated MCP with LlamaIndex

CrewAI logo

CrewAI

Use Templated MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Templated MCP with Pydantic AI

AutoGen logo

AutoGen

Use Templated MCP with AutoGen

FAQ

Frequently asked questions

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.

Yes, you can. Claude Agent SDK 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.

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.

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.

Start with Templated.It takes 30 seconds.

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

Start building