How to integrate Griptape MCP with Codex

Griptape logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Griptape MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Griptape with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Griptape MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on connect.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

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

The Griptape MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Griptape account. It provides structured and secure access to your Griptape platform, so your agent can create assistants, launch and monitor AI runs, retrieve logs, and analyze results automatically on your behalf.

  • Automated assistant creation and management: Easily direct your agent to create new assistants or list existing ones, making it simple to manage your AI resources in Griptape Cloud.
  • Launching and controlling assistant runs: Let your agent start new assistant runs, cancel ongoing executions, or fetch the status of any run for streamlined AI workflow management.
  • Real-time monitoring of assistant activities: Have your agent stream live run events, monitor progress, or retrieve detailed logs to keep tabs on every step of your generative AI processes.
  • Error handling and diagnostics: Ask your agent to fetch detailed error reports for failed runs, helping you troubleshoot and resolve issues quickly and efficiently.
  • Result retrieval and historical analysis: Automatically pull final outputs from completed runs and review historical execution data, empowering you to analyze and improve your generative AI pipelines over time.

Supported Tools & Triggers

Tools
Assistant CreationTool to create a new assistant.
List AssistantsTool to list all assistants.
Cancel Assistant RunTool to cancel an ongoing assistant run.
Assistant Run CreationTool to initiate a new assistant run.
Get Assistant Run Error DetailsTool to fetch detailed error information for a specific assistant run.
Stream Assistant Run EventsTool to stream real-time events for a specific Assistant run.
List Assistant RunsTool to list all runs for a given assistant.
Assistant Run Logs RetrievalTool to retrieve logs generated during the execution of a specific assistant run.
Assistant Run Result RetrievalTool to fetch the final result of a completed assistant run.
Retrieve Assistant RunTool to retrieve an assistant run's status and details.
Retry Assistant RunTool to retry a previously failed assistant run.
Get Ruleset by AliasTool to retrieve a ruleset by its alias.
List Embedding DriversTool to list available embedding drivers.
Ruleset CreationTool to create a new ruleset.
Create ToolTool to create a new tool in Griptape Cloud.
Get Tool Deployment StatusTool to retrieve status of a specific tool deployment.
List ToolsTool to list all tools.

Conclusion

You've successfully integrated Griptape with Codex using Composio's MCP server. Now you can interact with Griptape directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Griptape operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Griptape operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Griptape MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Griptape MCP?

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

Can I use Tool Router MCP with Codex?

Yes, you can. Codex 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 Griptape tools.

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

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.