# How to integrate TinyFish MCP MCP with Codex

```json
{
  "title": "How to integrate TinyFish MCP MCP with Codex",
  "toolkit": "TinyFish MCP",
  "toolkit_slug": "tinyfish_mcp",
  "framework": "Codex",
  "framework_slug": "codex",
  "url": "https://composio.dev/toolkits/tinyfish_mcp/framework/codex",
  "markdown_url": "https://composio.dev/toolkits/tinyfish_mcp/framework/codex.md",
  "updated_at": "2026-06-18T10:13:20.738Z"
}
```

## Introduction

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

## Also integrate TinyFish MCP with

- [Claude Cowork](https://composio.dev/toolkits/tinyfish_mcp/framework/claude-cowork)

## TL;DR

### 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 1000+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

## Connect TinyFish MCP to Codex

### How to install TinyFish MCP MCP in Codex
### Run the setup command
Run this command in your terminal to add the Composio MCP server to Codex.

```bash
codex mcp add composio --url https://connect.composio.dev/mcp
```

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

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

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `TINYFISH_MCP_CANCEL_RUN` | Cancel run | Cancels a running or pending automation run by its ID. Idempotent: if the run is already in a terminal state (COMPLETED, FAILED, CANCELLED), returns the current status without error. Only PENDING and RUNNING runs will be actively cancelled. |
| `TINYFISH_MCP_DISCOVER_RUN` | Discover run | Discovers the currently running automation for this session. Returns runId if a run is active, or null if not yet started. |
| `TINYFISH_MCP_GET_RUN` | Get run | Retrieves details of a specific automation run by its ID. Returns status, result, error, and other metadata. IMPORTANT: Call this after run_web_automation errors or times out — the run is likely still executing. If you do not have a run_id, use list_runs to find it. Also use this to poll for completion after run_web_automation_async. Runs typically take a few minutes. Wait 30-60 seconds between polls. |
| `TINYFISH_MCP_GET_STEPS` | Get steps | Retrieves the steps taken during an automation run, including screenshots. |
| `TINYFISH_MCP_LIST_RUNS` | List runs | Lists automation runs with optional filtering by status and pagination support. Returns an array of runs with their details. Use this to find a recently created run when you do not have its run_id (e.g., after run_web_automation timed out before returning a run_id). Filter by status=RUNNING to find active runs. |
| `TINYFISH_MCP_POLL_STATUS` | Poll status | Polls the current status of an automation run. Returns status, step, progress, and other metadata. |
| `TINYFISH_MCP_RUN_WEB_AUTOMATION` | Run web automation | Executes web automation given a URL and a Natural Language description of the automation goal to be performed. Automation is mostly focused around navigating complex web pages and extracting data from web pages. Include _meta.progressToken in your request to receive progress notifications. WARNING: This tool may take several minutes. If it errors or times out, the run is STILL EXECUTING on the server. DO NOT call this tool again or call run_web_automation_async — both would create a duplicate run. Instead: if you have a run_id from progress notifications, call get_run. If you have no run_id, call list_runs to find it. Only create a new run after confirming the previous one finished. |
| `TINYFISH_MCP_RUN_WEB_AUTOMATION_ASYNC` | Run web automation async | Starts a NEW web automation run asynchronously and returns a run_id immediately without waiting for completion. WARNING: Do NOT use this to retry a failed run_web_automation call — that run is still executing. Use get_run or list_runs to check its status instead. Only use this tool for genuinely new tasks. Workflow: 1) Call this tool to get a run_id. 2) Wait 30-60 seconds. 3) Call get_run with the run_id to check status. 4) Repeat step 2-3 until status is COMPLETED, FAILED, or CANCELLED. |

## Supported Triggers

None listed.

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

The TinyFish MCP MCP server provides comprehensive access to TinyFish MCP operations through Composio. Once connected, you can perform all major TinyFish MCP actions directly from Codex using natural language commands.

## Complete Code

None listed.

## Conclusion

### Conclusion
You've successfully integrated TinyFish MCP with Codex using Composio's MCP server. Now you can interact with TinyFish MCP 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 TinyFish MCP operations
- Managed authentication through Composio
- Access to 20,000+ tools across 1000+ apps for cross-app workflows
- CodeAct workbench for complex tool chaining
Next steps:
- Try asking Codex to perform various TinyFish MCP operations
- Explore cross-app workflows by connecting more toolkits
- Build automation scripts that leverage Codex's AI capabilities

## How to build TinyFish MCP MCP Agent with another framework

- [Claude Cowork](https://composio.dev/toolkits/tinyfish_mcp/framework/claude-cowork)

## Related Toolkits

- [Apify MCP](https://composio.dev/toolkits/apify_mcp) - Apify MCP is the official MCP server for Apify's web scraping and browser automation platform. Use it to run actors, collect structured web data, and automate crawling workflows.
- [Apilio](https://composio.dev/toolkits/apilio) - Apilio is a home automation platform that lets you connect and control smart devices from different brands. It helps you build flexible automations with complex conditions, schedules, and integrations.
- [Basin](https://composio.dev/toolkits/basin) - Basin is a no-code form backend for quickly setting up reliable contact forms. It lets you collect and manage form submissions without writing any server-side code.
- [Bouncer](https://composio.dev/toolkits/bouncer) - Bouncer is an email validation platform that verifies the authenticity of email addresses in real-time and batch. It helps boost deliverability and reduce bounce rates for your communications.
- [Celigo](https://composio.dev/toolkits/celigo) - Celigo is an integration platform as a service for connecting apps, data, and business workflows. It helps teams automate cross-system processes without building every integration from scratch.
- [Conveyor](https://composio.dev/toolkits/conveyor) - Conveyor is a platform that automates security reviews with a Trust Center and AI-driven questionnaire automation. It streamlines compliance and vendor security processes for faster, hassle-free reviews.
- [Crowdin](https://composio.dev/toolkits/crowdin) - Crowdin is a localization management platform that streamlines translation workflows and collaboration. It helps teams centralize multilingual content, boost productivity, and automate translation processes.
- [Databox](https://composio.dev/toolkits/databox) - Databox is a business analytics platform that connects your data from any tool and device. It helps you track KPIs, build dashboards, and discover actionable insights.
- [Detrack](https://composio.dev/toolkits/detrack) - Detrack is a delivery management platform for real-time tracking and proof of delivery. It helps businesses automate notifications and keep customers updated every step of the way.
- [Dnsfilter](https://composio.dev/toolkits/dnsfilter) - Dnsfilter is a cloud-based DNS security and content filtering solution. It helps organizations block online threats and manage safe internet access with ease.
- [Faraday](https://composio.dev/toolkits/faraday) - Faraday lets you embed AI in workflows across your stack for smarter automation. It boosts your favorite tools with actionable intelligence and seamless integration.
- [Feathery](https://composio.dev/toolkits/feathery) - Feathery is an AI-powered platform for building dynamic data intake forms with advanced logic. It helps teams automate complex workflows and collect structured data with ease.
- [Fillout forms](https://composio.dev/toolkits/fillout_forms) - Fillout forms is an online platform for building and managing forms with a flexible API. It lets you create, distribute, and collect responses from forms with ease.
- [Formdesk](https://composio.dev/toolkits/formdesk) - Formdesk is an online form builder for creating and managing professional forms. It's perfect for collecting data, automating workflows, and integrating form submissions with your favorite services.
- [Formsite](https://composio.dev/toolkits/formsite) - Formsite lets you build online forms and surveys with drag-and-drop simplicity. Capture, manage, and integrate form responses securely for streamlined workflows.
- [Graphhopper](https://composio.dev/toolkits/graphhopper) - GraphHopper is an enterprise-grade Directions API for routing, optimization, and geocoding across multiple vehicle types. It enables fast, reliable route planning and logistics automation for businesses.
- [Hyperbrowser](https://composio.dev/toolkits/hyperbrowser) - Hyperbrowser is a next-generation platform for scalable browser automation. It empowers AI agents to interact with web apps, automate workflows, and handle browser sessions at scale.
- [La Growth Machine](https://composio.dev/toolkits/lagrowthmachine) - La Growth Machine automates multi-channel sales outreach and routine tasks for sales teams. Streamline your workflow and focus on closing more deals.
- [Leverly](https://composio.dev/toolkits/leverly) - Leverly is a workflow automation platform that connects and coordinates actions across your apps. It streamlines repetitive processes so your business runs smoother, faster, and with fewer manual steps.
- [Maintainx](https://composio.dev/toolkits/maintainx) - Maintainx is a cloud-based CMMS for centralizing maintenance data, communication, and workflows. It helps organizations streamline maintenance operations and improve team coordination.

## Frequently Asked Questions

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

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

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

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

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