How to integrate Templated MCP with Claude Code

Manage your Templated directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

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

Manage your Templated directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Templated with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Templated to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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.

Connecting Templated via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Templated) for even more tool search precision. It's secure and reliable.

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 step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Templated account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['templated'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http templated-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Templated. This URL will be used to connect Claude Code to Templated.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Templated
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Templated MCP to Claude Code

bash
claude mcp add --transport http templated-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (templated-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Templated MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your templated-composio entry in the list
  • This confirms that Claude Code can now access Templated tools

If everything is wired up, you should see your templated-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Templated

The first time you try to use Templated tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Templated
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Templated authorization flow
  • Return to the terminal and start using Templated through Claude Code

Once authenticated, you can ask Claude Code to perform Templated operations in natural language. For example:

  • "Generate invoice PDF from customer data"
  • "List all available image templates"
  • "Clone existing certificate template for edits"

Complete Code

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

import 'dotenv/config';
import { Composio } from '@composio/core';

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 composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['templated'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http templated-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Templated with Claude Code using Composio's MCP server. Now you can interact with Templated directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Templated operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Templated operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

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

Tool to list all renders in a specific folder.

List Folders

Tool to list all folders in the account.

List Folder Templates

Tool to list all templates in a specific folder.

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

Tool to list all renders in the account.

List Template Clones

Tool to list all cloned templates in the account.

List Template Renders

Tool to list all renders of a specific template.

List Uploads

Tool to list all uploaded images in the account.

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

Tool to update an existing folder's properties.

Update Template

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

Update Template Tags

Tool to overwrite all tags on a template.

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 Code 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