# How to integrate Agility cms MCP with OpenAI Agents SDK

```json
{
  "title": "How to integrate Agility cms MCP with OpenAI Agents SDK",
  "toolkit": "Agility cms",
  "toolkit_slug": "agility_cms",
  "framework": "OpenAI Agents SDK",
  "framework_slug": "open-ai-agents-sdk",
  "url": "https://composio.dev/toolkits/agility_cms/framework/open-ai-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/agility_cms/framework/open-ai-agents-sdk.md",
  "updated_at": "2026-05-12T10:00:33.438Z"
}
```

## Introduction

This guide walks you through connecting Agility cms to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Agility cms agent that can list all authors for our blog, fetch content items tagged 'product-launch', show sitemap paths for the main website through natural language commands.
This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Agility cms account through Composio's Agility cms MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Agility cms with

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

## TL;DR

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

## What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.
Key features include:
- Hosted MCP Tools: Connect to external services through hosted MCP endpoints
- SQLite Sessions: Persist conversation history across interactions
- Simple API: Clean interface with Agent, Runner, and tool configuration
- Streaming Support: Real-time response streaming for interactive applications

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

The Agility cms MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Agility CMS account. It provides structured and secure access to your content models, pages, authors, categories, and more, so your agent can fetch content, retrieve metadata, manage sitemaps, and automate content discovery on your behalf.
- Content item and list retrieval: Instantly fetch specific content items by ID or pull paginated lists by reference name, complete with filtering and sorting.
- Dynamic schema and model insights: Allow your agent to get details on content models and page modules, so it can adapt to schema changes and build flexible digital experiences.
- Page and sitemap management: Retrieve detailed information about pages—including metadata, content zones, and components—or pull the flat sitemap for custom routing and navigation logic.
- Author, category, and tag lookup: Effortlessly list all authors, categories, and tags within your CMS instance to enable rich content filtering and assignment workflows.
- Log and sync monitoring: Access recent sync logs to keep tabs on content updates and ensure your agent is always working with the latest data.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `AGILITY_CMS_GET_API_TYPES` | Get API Types | Tool to retrieve all enum types used throughout the Agility CMS Management API. Use when you need to understand available values for status codes, types, permissions, and other enumerated fields. |
| `AGILITY_CMS_GET_CONTENT_ITEM` | Get Content Item | Tool to fetch details of a content item by Content ID. Use when you need item fields and metadata from Agility CMS. |
| `AGILITY_CMS_GET_CONTENT_LIST` | Get Content List | Retrieves a paginated list of content items by reference name from Agility CMS. Use this action to: - Fetch multiple content items of a specific type (e.g., blog posts, products, authors) - Retrieve content with pagination, filtering, and sorting capabilities - Expand linked content to specified depths Required parameters: instance GUID, API type (fetch/preview), locale code, and lowercase reference name. Tip: Use Get Content Models action first to discover available reference names for your instance. |
| `AGILITY_CMS_GET_CONTENT_MODELS` | Get Content Models | Tool to retrieve content models and page modules. Use when you need schema definitions to dynamically build content structures. |
| `AGILITY_CMS_GET_LOGS` | Get Logs | Retrieve sync items (content change logs) from Agility CMS using the Content Sync API. This tool implements incremental content synchronization: - Use syncToken='0' for initial full sync (retrieves all content) - Use the returned syncToken in subsequent calls to get only new/updated content - Maximum pageSize is 500 items per request - Continue pagination until syncToken='0' is returned (indicating you're up to date) Typical workflow: 1. Call with syncToken='0' to get initial content batch 2. Store the returned syncToken 3. On next sync, pass the stored syncToken to get only changes since last sync 4. Repeat until syncToken='0' (no more updates) |
| `AGILITY_CMS_GET_PAGE` | Get Page | Tool to retrieve details of a Page, including metadata, content zones, and components. Use after you know the page_id to fetch. |
| `AGILITY_CMS_GET_PAGE_MODULES` | Get Page Modules | Retrieves page module definitions from Agility CMS. Page modules are UI components that can be added to pages. This action fetches all model definitions and filters to return only page modules (definitions without contentReferenceNames). Use this to understand what page modules are available for building pages. For content type definitions, use Get Content Models instead. |
| `AGILITY_CMS_GET_SITEMAP_FLAT` | Get Sitemap Flat | Retrieves the flat sitemap for a specific channel and locale in Agility CMS. Returns a dictionary mapping page paths to sitemap items containing page metadata, SEO info, and routing details. Use this when you need to get all pages and their URLs for implementing page routing, generating sitemaps, or navigating the site structure. Required: instance GUID, API type (fetch/preview), locale code, and channel name. |
| `AGILITY_CMS_SYNC_PAGES` | Sync Pages | Retrieves all page items from Agility CMS in paged format with sync tokens for incremental updates. Use this to synchronize local page data with the CMS. Start with syncToken=0 for initial sync, then use the returned syncToken in subsequent calls to get only changed pages. Each response includes page metadata, SEO fields, visibility settings, and script configurations. |

## Supported Triggers

None listed.

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

The Agility cms MCP server is an implementation of the Model Context Protocol that connects your AI agent to Agility cms. It provides structured and secure access so your agent can perform Agility cms 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:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Agility cms project
- Some knowledge of Python or 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'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).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

What's happening:
- You're importing all necessary libraries.
- The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Agility cms.
```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
```

```typescript
dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only agility_cms.
- The router checks the user's Agility cms connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Agility cms.
- This approach keeps things lightweight and lets the agent request Agility cms tools only when needed during the conversation.
```python
# Create a Agility cms Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["agility_cms"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Agility cms
const session = await composio.create(userId as string, {
  toolkits: ['agility_cms'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Agility cms. "
        "Help users perform Agility cms operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Agility cms. Help users perform Agility cms operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

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

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
```

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["agility_cms"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Agility cms. "
        "Help users perform Agility cms operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['agility_cms'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Agility cms. Help users perform Agility cms operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

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

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});
```

## Conclusion

This was a starter code for integrating Agility cms MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Agility cms.
Key features:
- Hosted MCP tool integration through Composio's Tool Router
- SQLite session persistence for conversation history
- Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## How to build Agility cms MCP Agent with another framework

- [Claude Agent SDK](https://composio.dev/toolkits/agility_cms/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/agility_cms/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/agility_cms/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/agility_cms/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/agility_cms/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/agility_cms/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/agility_cms/framework/cli)
- [Google ADK](https://composio.dev/toolkits/agility_cms/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/agility_cms/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/agility_cms/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/agility_cms/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/agility_cms/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/agility_cms/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.
- [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.
- [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.
- [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.
- [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.
- [Docmosis](https://composio.dev/toolkits/docmosis) - Docmosis generates PDF and Word documents from user-defined templates. It's perfect for merging data fields to quickly produce reports, invoices, and business letters.
- [Docnify](https://composio.dev/toolkits/docnify) - Docnify is a digital signing platform that streamlines the way you sign and manage documents. It brings together tools like Figma, Jira, Trello, and Google Docs for a unified document workspace.
- [Docparser](https://composio.dev/toolkits/docparser) - Docparser is a cloud-based document parsing and automation platform. It streamlines data extraction from PDFs and documents for faster workflows.
- [DocRaptor](https://composio.dev/toolkits/docraptor) - DocRaptor is a powerful API for converting HTML to PDF or XLSX documents. It enables fast, high-quality document generation from your applications.
- [Docsautomator](https://composio.dev/toolkits/docsautomator) - Docsautomator is an automation platform for Google Docs. It lets you create, manage, and generate documents from templates quickly.
- [Docsumo](https://composio.dev/toolkits/docsumo) - Docsumo is an AI-powered platform for automating document data extraction and analysis. It helps you turn PDFs, invoices, and forms into structured, actionable data with minimal manual effort.
- [Docugenerate](https://composio.dev/toolkits/docugenerate) - Docugenerate turns Word templates and JSON data into polished PDF documents. Streamline document automation for tasks like contracts, invoices, and certificates.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Agility cms MCP?

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

### Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents 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 Agility cms tools.

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

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

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