How to integrate Apiflash MCP with Codex

Apiflash logo
Codex logo
divider

Introduction

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

Also integrate Apiflash 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 Apiflash 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 dashboard.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 Apiflash MCP server, and what's possible with it?

The Apiflash MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Apiflash account. It provides structured and secure access to high-quality website screenshot capture, so your agent can capture web pages, manage batches of screenshots, retrieve quota usage, and access screenshot metadata on your behalf.

  • Single and batch website screenshot capture: Instantly direct your agent to take high-resolution screenshots of one or many web pages at once, perfect for monitoring, archiving, or sharing site visuals.
  • Customizable screenshot requests: Let your agent use advanced options with POST requests to tailor captures using form data and specific parameters for precise results.
  • API quota monitoring: Check your remaining screenshot credits and quota status in real time, so your automations never hit unexpected usage limits.
  • Screenshot metadata retrieval: Pull detailed information about previously taken screenshots, including file size and dimensions, for reporting or further processing.

Supported Tools & Triggers

Tools
Batch Capture ScreenshotsTool to capture screenshots for multiple urls in a single request.
Capture Website Screenshot (POST)Tool to capture a screenshot of a website via http post.
Get Quota InformationTool to retrieve current api quota usage and limits.
Get Screenshot MetadataTool to retrieve metadata for a previously captured screenshot.

Conclusion

You've successfully integrated Apiflash with Codex using Composio's MCP server. Now you can interact with Apiflash 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 Apiflash 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 Apiflash operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Apiflash MCP Agent with another framework

FAQ

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

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

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

Yes, absolutely. You can configure which Apiflash 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 Apiflash 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.