# How to integrate Storyblok MCP with Mastra AI

```json
{
  "title": "How to integrate Storyblok MCP with Mastra AI",
  "toolkit": "Storyblok",
  "toolkit_slug": "storyblok",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/storyblok/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/storyblok/framework/mastra-ai.md",
  "updated_at": "2026-03-29T06:51:51.822Z"
}
```

## Introduction

This guide walks you through connecting Storyblok to Mastra AI using the Composio tool router. By the end, you'll have a working Storyblok agent that can create a new blog post draft, list all unpublished blog posts, update page content for the homepage through natural language commands.
This guide will help you understand how to give your Mastra AI agent real control over a Storyblok account through Composio's Storyblok MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Storyblok with

- [OpenAI Agents SDK](https://composio.dev/toolkits/storyblok/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/storyblok/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/storyblok/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/storyblok/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/storyblok/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/storyblok/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/storyblok/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/storyblok/framework/cli)
- [Google ADK](https://composio.dev/toolkits/storyblok/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/storyblok/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/storyblok/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/storyblok/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/storyblok/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 Storyblok tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Storyblok 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 Storyblok 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 Storyblok MCP server, and what's possible with it?

The Storyblok MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Storyblok account. It provides structured and secure access so your agent can perform Storyblok operations on your behalf.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `STORYBLOK_FETCH_CONTENT_TYPE_ITEMS_GRAPHQL` | Fetch Content Type Items (GraphQL) | Fetch multiple stories/content items using Storyblok's GraphQL API with filtering and pagination. Use starts_with with language code prefix (e.g., 'es/*', 'hi/*') to retrieve translated content in specific languages. |
| `STORYBLOK_FETCH_GRAPHQL_CONTENT_ITEM` | Fetch GraphQL Content Item | Tool to fetch a single story in a specific language using Storyblok GraphQL API with field-level translations. For each content type (e.g., Page), Storyblok generates a ContentTypeItem field (e.g., PageItem). Use when you need to retrieve a specific story by ID or slug with optional language translation. |
| `STORYBLOK_GET_APP` | Get Extension/App | Tool to retrieve a Storyblok extension/app by ID using the Management API. Use when you need to fetch details about a specific extension or app installed in Storyblok. |
| `STORYBLOK_GET_DATASOURCE_ENTRIES` | Get Datasource Entries | Tool to retrieve datasource entries from Storyblok via GraphQL API. Use when you need to fetch datasource data. Returns datasource entries with fields like id, name, value, and dimension_value. |
| `STORYBLOK_GET_GRAPHQL_RATE_LIMIT` | Get GraphQL Rate Limit | Tool to retrieve rate limit information from Storyblok GraphQL API. Use when you need to check the maximum cost per request to calculate safe request rates (100 / maxCost = requests per second). |
| `STORYBLOK_GET_PAGE_ITEM` | Get Page Item | Tool to retrieve a single page item by ID or slug from Storyblok using GraphQL. Use when you need to fetch specific page content with custom field selection. Supports both draft and published versions. |
| `STORYBLOK_LIST_GRAPHQL_CONTENT_TYPE_ITEMS` | List GraphQL Content Type Items | Tool to retrieve multiple content items with pagination, filtering, and relation resolution for any Storyblok content type via GraphQL. Content types are dynamically generated as [ContentType]Items (e.g., PageItems, BlogArticleItems). Use when you need to query structured content with flexible field selection and filtering. |
| `STORYBLOK_QUERY_PAGE_ITEMS_VIA_GRAPHQL` | Query page items via GraphQL | Execute GraphQL queries to retrieve multiple page items from Storyblok with filtering options. Use when you need to fetch page content with filters like path prefix, publish date, or slug exclusions. |
| `STORYBLOK_RETRIEVE_LINKS_VIA_GRAPHQL` | Retrieve Links via GraphQL | Tool to retrieve links for navigation using Storyblok's GraphQL API. Use when you need to fetch navigation links with their metadata (id, uuid, slug, name, published status). |
| `STORYBLOK_RETRIEVE_TAGS_VIA_GRAPHQL` | Retrieve Tags via GraphQL | Tool to retrieve tags from Storyblok via GraphQL API. Use when you need to fetch available tags for content organization and filtering. |

## Supported Triggers

None listed.

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

The Storyblok MCP server is an implementation of the Model Context Protocol that connects your AI agent to Storyblok. It provides structured and secure access so your agent can perform Storyblok 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 Storyblok 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 Storyblok

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "storyblok" for Storyblok 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: ["storyblok"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Storyblok 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 Storyblok 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: "storyblok-mastra-agent",
    instructions: "You are an AI agent with Storyblok 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 Storyblok 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: {
        storyblok: 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: ["storyblok"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "storyblok-mastra-agent",
    instructions: "You are an AI agent with Storyblok 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: { storyblok: 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 Storyblok 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 Storyblok MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/storyblok/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/storyblok/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/storyblok/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/storyblok/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/storyblok/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/storyblok/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/storyblok/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/storyblok/framework/cli)
- [Google ADK](https://composio.dev/toolkits/storyblok/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/storyblok/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/storyblok/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/storyblok/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/storyblok/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 Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [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.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Reddit](https://composio.dev/toolkits/reddit) - Reddit is a social news platform with thriving user-driven communities (subreddits). It's the go-to place for discussion, content sharing, and viral marketing.
- [Facebook](https://composio.dev/toolkits/facebook) - Facebook is a social media and advertising platform for businesses and creators. It helps you connect, share, and manage content across your public Facebook Pages.
- [Linkedin](https://composio.dev/toolkits/linkedin) - LinkedIn is a professional networking platform for connecting, sharing content, and engaging with business opportunities. It's the go-to place for building your professional brand and unlocking new career connections.
- [Active campaign](https://composio.dev/toolkits/active_campaign) - ActiveCampaign is a marketing automation and CRM platform for managing email campaigns, sales pipelines, and customer segmentation. It helps businesses engage customers and drive growth through smart automation and targeted outreach.
- [ActiveTrail](https://composio.dev/toolkits/active_trail) - ActiveTrail is a user-friendly email marketing and automation platform. It helps you reach subscribers and automate campaigns with ease.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [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.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.

## Frequently Asked Questions

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

With a standalone Storyblok MCP server, the agents and LLMs can only access a fixed set of Storyblok tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Storyblok 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 Storyblok tools.

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

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

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