# How to integrate Placid MCP with Mastra AI

```json
{
  "title": "How to integrate Placid MCP with Mastra AI",
  "toolkit": "Placid",
  "toolkit_slug": "placid",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/placid/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/placid/framework/mastra-ai.md",
  "updated_at": "2026-05-12T10:22:11.363Z"
}
```

## Introduction

This guide walks you through connecting Placid to Mastra AI using the Composio tool router. By the end, you'll have a working Placid agent that can create a linkedin banner template for me, delete last week's event flyer template, list all pdf template collections in your account through natural language commands.
This guide will help you understand how to give your Mastra AI agent real control over a Placid account through Composio's Placid MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Placid with

- [OpenAI Agents SDK](https://composio.dev/toolkits/placid/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/placid/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/placid/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/placid/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/placid/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/placid/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/placid/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/placid/framework/cli)
- [Google ADK](https://composio.dev/toolkits/placid/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/placid/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/placid/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/placid/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/placid/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Set up your environment so Mastra, OpenAI, and Composio work together
- Create a Tool Router session in Composio that exposes Placid tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Placid tool definitions and attach them as a toolset
- Build a Mastra agent that can reason, call tools, and return structured results
- Run an interactive CLI where you can chat with your Placid agent

## What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.
Key features include:
- MCP Client: Built-in support for Model Context Protocol servers
- Toolsets: Organize tools into logical groups
- Step Callbacks: Monitor and debug agent execution
- OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

## What is the Placid MCP server, and what's possible with it?

The Placid MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Placid account. It provides structured and secure access to your creative automation workspace, so your agent can perform actions like creating image templates, managing template collections, and deleting designs on your behalf.
- Template creation and customization: Instantly generate new Placid templates with defined dimensions, tags, or custom metadata—perfect for automating banners, graphics, and more.
- Template deletion and lifecycle management: Direct your agent to safely remove obsolete or unused templates by their unique IDs, keeping your workspace organized and clutter-free.
- Collection retrieval and organization: Have your agent fetch and list all template collections, making it easy to browse, search, or group creative assets programmatically.
- Automated workflow integration: Integrate template management into larger creative pipelines, allowing your agent to handle content operations without manual intervention.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `PLACID_CREATE_COLLECTION` | Create Collection | Tool to create a new template collection to group multiple templates. Use when organizing templates into collections with custom metadata. |
| `PLACID_CREATE_TEMPLATE` | Create Template | Tool to create a new Placid template. Use when you need a template with specific dimensions and optional tags or custom metadata. Example: "Create a social-media banner." |
| `PLACID_DELETE_COLLECTION` | Delete Collection | Tool to delete a template collection by its ID. Use after confirming the collection is no longer needed. Note: This does not delete the templates within the collection. |
| `PLACID_DELETE_TEMPLATE` | Delete Template | Tool to delete a specific template identified by UUID. Use after confirming the template is no longer needed. |
| `PLACID_GET_COLLECTION` | Get Collection | Tool to retrieve a single collection by its ID. Use when you need details about a specific collection including its title, custom data, and associated template UUIDs. |
| `PLACID_GET_COLLECTIONS` | Get Collections | Tool to retrieve a list of all template collections. Use after authentication to paginate through your Placid collections. |
| `PLACID_GET_TEMPLATE` | Get Template | Tool to retrieve a template by UUID. Returns template details including title, thumbnail, tags, and layers. |
| `PLACID_LIST_NL_TEMPLATES` | List NL Templates | Tool to list all available templates via the Natural Language API. Use when you need to discover available templates for generating images. |
| `PLACID_LIST_TEMPLATES` | List Templates | Tool to retrieve a list of templates from your project. Returns 20 items per page with cursor pagination. Use to browse templates, optionally filtered by collection or title. |
| `PLACID_UPDATE_COLLECTION` | Update Collection | Tool to update an existing template collection. Use to modify title, custom_data, or manage templates (replace all, or incrementally add/remove specific templates). |
| `PLACID_UPDATE_TEMPLATE` | Update Template | Tool to update an existing Placid template. Use when you need to modify the title, tags, or custom_data of a template. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Placid MCP server is an implementation of the Model Context Protocol that connects your AI agent to Placid. It provides structured and secure access so your agent can perform Placid 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 starting, make sure you have:
- Node.js 18 or higher
- A Composio account with an active API key
- An OpenAI API key
- Basic familiarity with TypeScript

### 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 need credits or a connected billing setup to use the models.
- Store the key somewhere safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.
- This key lets your Mastra agent talk to Composio and reach Placid through MCP.

### 2. Install dependencies

Install the required packages.
What's happening:
- @composio/core is the Composio SDK for creating MCP sessions
- @mastra/core provides the Agent class
- @mastra/mcp is Mastra's MCP client
- @ai-sdk/openai is the model wrapper for OpenAI
- dotenv loads environment variables from .env
```bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio
- COMPOSIO_USER_ID tells Composio which user this session belongs to
- OPENAI_API_KEY lets the Mastra agent call OpenAI models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import libraries and validate environment

What's happening:
- dotenv/config auto loads your .env so process.env.* is available
- openai gives you a Mastra compatible model wrapper
- Agent is the Mastra agent that will call tools and produce answers
- MCPClient connects Mastra to your Composio MCP server
- Composio is used to create a Tool Router session
```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) 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 as string,
});
```

### 5. Create a Tool Router session for Placid

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "placid" for Placid access
- session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
```typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["placid"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Placid MCP URL:", composioMCPUrl);
```

### 6. Configure Mastra MCP client and fetch tools

What's happening:
- MCPClient takes an id for this client and a list of MCP servers
- The headers property includes the x-api-key for authentication
- getTools fetches the tool definitions exposed by the Placid toolkit
```typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
```

### 7. Create the Mastra agent

What's happening:
- Agent is the core Mastra agent
- name is just an identifier for logging and debugging
- instructions guide the agent to use tools instead of only answering in natural language
- model uses openai("gpt-5") to configure the underlying LLM
```typescript
const agent = new Agent({
    name: "placid-mastra-agent",
    instructions: "You are an AI agent with Placid tools via Composio.",
    model: "openai/gpt-5",
  });
```

### 8. Set up interactive chat interface

What's happening:
- messages keeps the full conversation history in Mastra's expected format
- agent.generate runs the agent with conversation history and Placid toolsets
- maxSteps limits how many tool calls the agent can take in a single run
- onStepFinish is a hook that prints intermediate steps for debugging
```typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\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({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        placid: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    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 { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) 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 as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["placid"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      placid: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "placid-mastra-agent",
    instructions: "You are an AI agent with Placid tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { placid: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();
```

## Conclusion

You've built a Mastra AI agent that can interact with Placid through Composio's Tool Router.
You can extend this further by:
- Adding other toolkits like Gmail, Slack, or GitHub
- Building a web-based chat interface around this agent
- Using multiple MCP endpoints to enable cross-app workflows

## How to build Placid MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/placid/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/placid/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/placid/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/placid/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/placid/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/placid/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/placid/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/placid/framework/cli)
- [Google ADK](https://composio.dev/toolkits/placid/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/placid/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/placid/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/placid/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/placid/framework/crew-ai)

## Related Toolkits

- [Figma](https://composio.dev/toolkits/figma) - Figma is a collaborative interface design tool for teams and individuals. It streamlines design workflows with real-time collaboration and easy sharing.
- [Abyssale](https://composio.dev/toolkits/abyssale) - Abyssale is a creative automation platform for generating images, videos, GIFs, PDFs, and HTML5 content programmatically. It streamlines and scales visual content production for marketing, design, and operations teams.
- [Alttext ai](https://composio.dev/toolkits/alttext_ai) - AltText.ai is a service that generates alt text for images automatically. It helps boost accessibility and SEO for your visual content.
- [Bannerbear](https://composio.dev/toolkits/bannerbear) - Bannerbear is an API-driven platform for generating images and videos automatically at scale. It helps businesses create custom graphics, social visuals, and marketing assets using powerful templates.
- [Canva](https://composio.dev/toolkits/canva) - Canva is a drag-and-drop design suite for creating professional graphics, presentations, and marketing materials. It makes it easy for anyone to design with beautiful templates and a vast library of elements.
- [Claid ai](https://composio.dev/toolkits/claid_ai) - Claid.ai delivers AI-driven image editing APIs for tasks like background removal, upscaling, and color correction. It helps automate and enhance image workflows with powerful, developer-friendly tools.
- [Cloudinary](https://composio.dev/toolkits/cloudinary) - Cloudinary is a cloud-based platform for managing, uploading, and transforming images and videos. It streamlines media workflows and delivers optimized assets globally.
- [Cults](https://composio.dev/toolkits/cults) - Cults is a digital marketplace for 3D printing models, connecting designers and makers. It lets creators share, sell, and discover a huge variety of printable designs easily.
- [DeepImage](https://composio.dev/toolkits/deepimage) - DeepImage is an AI-powered image enhancer and upscaler. Get higher-quality images with just a few clicks.
- [Dreamstudio](https://composio.dev/toolkits/dreamstudio) - DreamStudio is Stability AI’s platform for generating and editing images with AI. It lets you easily turn ideas into stunning visuals, fast.
- [Dynapictures](https://composio.dev/toolkits/dynapictures) - Dynapictures is a cloud-based platform for generating personalized images at scale. Instantly create hundreds of custom visuals using your data sources, like Google Sheets.
- [Fal.ai](https://composio.dev/toolkits/fal_ai) - Fal.ai is a generative media platform offering 600+ AI models for images, video, voice, and audio. Developers use Fal.ai for fast, scalable access to cutting-edge generative AI tools.
- [Gamma](https://composio.dev/toolkits/gamma) - Gamma is an AI-powered platform for making beautiful, interactive presentations and documents. It lets anyone create and share engaging decks with minimal effort.
- [Html to image](https://composio.dev/toolkits/html_to_image) - Html to image converts HTML and CSS into images or captures web page screenshots. Instantly generate visuals from code or web content—no manual screenshots needed.
- [Imagior](https://composio.dev/toolkits/imagior) - Imagior is an AI-powered image generation platform that lets you create and customize images using dynamic templates and APIs. Perfect for businesses and creators needing fast, scalable visuals without design hassle.
- [Imejis io](https://composio.dev/toolkits/imejis_io) - Imejis io is an API-based image generation platform with powerful customization and template support. It lets you create and modify images in seconds, no manual design work required.
- [Imgix](https://composio.dev/toolkits/imgix) - Imgix is a real-time image processing and delivery service for developers. It helps you optimize, transform, and deliver images efficiently at any scale.
- [Kraken io](https://composio.dev/toolkits/kraken_io) - Kraken.io is an image optimization and compression platform. It helps you shrink image file sizes while keeping visual quality intact.
- [Logo dev](https://composio.dev/toolkits/logo_dev) - Logo.dev is an API and database for high-resolution company logos and brand metadata. Instantly fetch official logos from any domain without scraping or manual searching.
- [Miro](https://composio.dev/toolkits/miro) - Miro is a collaborative online whiteboard platform for teams to brainstorm, design, and manage projects visually. It streamlines teamwork by enabling real-time idea sharing, diagramming, and workflow planning in a single space.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Placid MCP?

With a standalone Placid MCP server, the agents and LLMs can only access a fixed set of Placid tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Placid and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra AI 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 Placid tools.

### Can I manage the permissions and scopes for Placid while using Tool Router?

Yes, absolutely. You can configure which Placid 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 Placid data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
