# TinyFish MCP connector

The TinyFish connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent fetch web pages, run research, and manage page monitors and browser profiles in TinyFish, with each person signed in as themselves and every call logged.

Source: https://elaichi.ai/connectors/tinyfish/

## Facts

| | |
| --- | --- |
| Application | TinyFish |
| Category | Application Development |
| AI tools | 43 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once TinyFish is connected

- Start a research run on Acme's pricing page and summarize it
- Which monitors changed this week and what moved?
- Create a monitor for our top competitor's careers page

## Connect TinyFish in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick TinyFish.
2. Optionally set Share with, then press Connect.
3. Paste a TinyFish API key. One person generates a token in TinyFish and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which TinyFish tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## TinyFish MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## TinyFish MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## TinyFish MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## TinyFish MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## TinyFish MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect TinyFish to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a TinyFish tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with TinyFish through Elaichi

### Research a prospect before the call

Sales. Start a TinyFish research run on a prospect's website from Claude and get the findings back while you prepare. Ask a follow-up and the agent pulls the run's results again.

### Watch competitor pricing pages for changes

Marketing. Create a TinyFish monitor on a competitor's pricing page, run it when you need a fresh look, and ask what moved since last week.

### Check a vendor status page right now

Support. Fetch the live page through TinyFish and drop the current status into the ticket without leaving the conversation.

### Pull page content into a spec

Product. Fetch a documentation page or kick off a research run and bring the findings straight into the document you are writing.

### Keep browser profiles tidy

Engineering. List, update or delete TinyFish browser profiles, complete or cancel a profile setup session, and remove a stale domain, all from Cursor.

### See what the team has been running

Operations. List TinyFish browser session and fetch usage records to see how much the team is using and where it is going.

## Elaichi vs Zapier MCP vs Composio for TinyFish

All three can connect TinyFish to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over TinyFish tools | Allow or restrict single TinyFish tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per TinyFish call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect TinyFish to Claude?

Connect TinyFish in Elaichi by pasting your TinyFish API key, which is the whole sign-in step. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Short, concrete asks about a monitor or a research run work better than long sentences.

### Does TinyFish work with ChatGPT and Cursor as well as Claude?

Yes. Once TinyFish is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect TinyFish once and every client sees it.

### What can an AI agent actually do with my TinyFish data?

An agent can fetch a web page through TinyFish, start a research run and read back its findings, and create, run, update or delete page monitors. It can also manage TinyFish browser profiles and sessions and show usage records for sessions and fetches. You ask in plain words, and the agent does the TinyFish work for you.

### Does connecting TinyFish give the AI everything in my TinyFish account?

No. The TinyFish connection carries the access of the API key that was used to connect it, so an agent can never reach more in TinyFish than that key can. Elaichi can narrow that access further with restrictions on a role or one person, and it never widens it.

### Can my team share one TinyFish connection?

Yes. One person connects TinyFish with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who ran each TinyFish call.

### Can I stop an agent from deleting or changing things in TinyFish?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting TinyFish monitors or browser profiles for a role or for one person while leaving fetches and research runs open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a TinyFish connection when someone leaves?

Offboarding a person in Elaichi ends their access to TinyFish at once, in every client they used. A shared TinyFish connection keeps working for everyone else on the team. If you disconnect TinyFish in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the TinyFish MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. TinyFish is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for TinyFish?

Yes. Both let Claude, ChatGPT or Cursor use TinyFish. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every TinyFish call.

### How is Elaichi different from Composio for TinyFish?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to TinyFish: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 43 TinyFish tools

Every tool below is callable through https://api.elaichi.ai/mcp once TinyFish is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Delete a TinyFish browser context profile domain by ID** (Delete). Remove one saved domain (its cookies and storage) from a Browser Context Profile. Required: id, profile_id.
- **Create a TinyFish browser context profile setup session** (Create). Start a temporary setup browser for a Browser Context Profile. Returns session_id and cdp_url: connect a CDP client (Playwright, Puppeteer) to cdp_url, log in, then save with browser_context_profile_setup_sessions.complete before expires_at. Required: profile_id.
- **TinyFish browser context profile setup sessions cancel** (Cancel). Cancel a running profile setup session and discard its unsaved state. Required: profile_id, session_id.
- **TinyFish browser context profile setup sessions complete** (Complete). Save a running setup session into its Browser Context Profile: captures cookies, local storage and session storage per domain. Saving again returns the first save's result. Required: profile_id, session_id.
- **Create a TinyFish browser context profile state** (Create). Upload browser state into a Browser Context Profile: cookies, plus optional localStorage and sessionStorage per origin. Required: profile_id, cookies.
- **List all TinyFish browser context profiles** (List). List Browser Context Profiles: saved logged-in browser state (cookies, local and session storage per domain) that runs reuse via profile_id.
- **Create a TinyFish browser context profile** (Create). Create an empty Browser Context Profile. Fill it by logging in through browser_context_profile_setup_sessions.create or by uploading cookies with browser_context_profile_states.create. Required: name.
- **Get single TinyFish browser context profile by ID** (Get). Get a Browser Context Profile and its saved domains. Required: id.
- **Update a TinyFish browser context profile by ID** (Update). Rename a Browser Context Profile, make it the default, or change its proxy country. Required: id.
- **Delete a TinyFish browser context profile by ID** (Delete). Delete a Browser Context Profile and its saved state. Required: id.
- **List all TinyFish browser session usage records** (List). List remote browser session usage: duration, data transfer, mode and status per session.
- **Create a TinyFish browser session** (Create). Create a remote browser session. Returns session_id and cdp_url: drive the browser over CDP (Playwright, Puppeteer). Spends wallet credit while it runs; end it with browser_sessions.delete.
- **Delete a TinyFish browser session by ID** (Delete). Terminate a remote browser session at once. Idempotent: an ended session also returns success. Required: id.
- **List all TinyFish fetch usage records** (List). List Fetch API usage records: URL, format, status and metadata per fetch.
- **Create a TinyFish fetch** (Create). Fetch up to 10 URLs and get clean extracted content (markdown, html or json), rendering JavaScript pages when needed. Per-URL failures are listed in errors without failing the request. Free within a daily allowance. Required: urls.
- **Create a TinyFish monitor run** (Create). Run a Monitor now, outside its schedule. Returns the new run. Required: monitor_id.
- **Create a TinyFish monitor** (Create). Create a Monitor that runs on a cron schedule: type fetch watches a page (config url), type search watches a topic (config query). Captures a baseline run at once and can post each run's results to webhook_url. Required: schedule_cron, type, config.
- **List all TinyFish monitors** (List). List Monitors (scheduled page or topic watches) with their schedule, status and latest run.
- **Get single TinyFish monitor by ID** (Get). Get a Monitor with its schedule, status and runs. Required: id.
- **Update a TinyFish monitor by ID** (Update). Pause or resume a Monitor (send status alone), or edit it (schedule_cron, with optional name, webhook_url and purpose). Required: id.
- **Delete a TinyFish monitor by ID** (Delete). Delete a Monitor and its schedule. Required: id.
- **Create a TinyFish research run** (Create). Start a research run: TinyFish searches the web, evaluates sources and writes a cited report for query. Returns research_run_id at once; poll research_runs.get (usually several minutes). 2 free completed runs a day, then billed; up to 5 at once. Required: query.
- **List all TinyFish research runs** (List). List saved research runs, newest first, filterable by status, query text and created date range.
- **Get single TinyFish research run by ID** (Get). Get a research run: status, query, quick and deep results (the cited report), plan, evidence and per-iteration state. Poll this after research_runs.create. Required: id.
- **TinyFish research runs cancel** (Cancel). Cancel a running research run. Idempotent: a finished run returns cancelled false and its current status. Required: research_run_id.
- **List all TinyFish run step HTML snapshots** (List). Get the full-page HTML captured at one step of a run (raw text/html). Only for runs started with capture_config html set to true; the final "Task completed" step has none (404). Required: run_id, step_id.
- **List all TinyFish run step screenshots** (List). Download the JPEG screenshot captured at one step of a run (binary image/jpeg). Step IDs are in the steps of runs.get; the final "Task completed" step has no screenshot (404). Required: run_id, step_id.
- **TinyFish runs execute** (Execute). Run a web automation and wait for it: TinyFish opens url in a real browser, follows the goal and returns the finished run (COMPLETED or FAILED, result JSON). For short tasks only; use runs.create for long ones. Spends wallet credit. Required: url, goal.
- **Create a TinyFish run** (Create). Start a web automation asynchronously and get its run_id at once. TinyFish opens url in a real browser and works through the natural-language goal. Poll runs.get until status is COMPLETED, FAILED or CANCELLED (or set webhook_url); stop it with runs.cancel. Spends wallet credit. Required: url, goal.
- **TinyFish runs bulk create** (Create). Start up to 100 web automations in one request, each with its own url and goal. Returns their run_ids in order; poll them with runs.bulk_get. Spends wallet credit per run. Required: runs.
- **List all TinyFish runs** (List). List automation runs, newest first, filterable by status, goal text and created date range. Each run has run_id, status, goal, result and timing.
- **TinyFish runs bulk get** (Get). Get up to 100 runs by ID in one request. Found runs are in data; unknown or not-owned IDs are listed in not_found. Runs here omit steps and video_url; use runs.get for those. Required: run_ids.
- **TinyFish runs bulk cancel** (Cancel). Cancel up to 100 runs by ID. Returns a result per run (cancelled, or already finished) and the IDs not found. Idempotent. Required: run_ids.
- **Get single TinyFish run by ID** (Get). Get one automation run: status (PENDING, RUNNING, COMPLETED, FAILED, CANCELLED), goal, result JSON, error, steps, timing and the live streaming_url. Poll this after runs.create. Required: id.
- **TinyFish runs cancel** (Cancel). Cancel a pending or running automation started with runs.create. Runs from runs.execute can't be cancelled. Required: run_id.
- **List all TinyFish search results** (List). Search the web and get ranked results (title, snippet, url) for query, with optional location, language, domain filters, date ranges and news or research-paper modes. Free within a daily allowance. Required: query.
- **List all TinyFish search usage records** (List). List Search API usage records: query details, status and result counts.
- **Create a TinyFish vault connection** (Create). Connect a password manager (1Password service-account token, or Bitwarden client ID, secret and master password) so runs can log in to websites with its credentials. Syncs display-safe item metadata at once. Required: provider.
- **List all TinyFish vault connections** (List). List the password managers (vault providers) connected to TinyFish.
- **Delete a TinyFish vault connection by ID** (Delete). Disconnect a vault provider and remove its stored enabled items. Required: id.
- **Create a TinyFish vault item sync** (Create). Re-sync items from the connected vault providers. Returns the merged items and sync counters.
- **List all TinyFish vault items** (List). List the credential items available from connected vaults (display-safe metadata, no secrets). Pass their IDs as credential_item_ids when starting a run with use_vault.
- **List all TinyFish wallets** (List). Get the wallet: available balance, currency, auto-reload settings, per-product rates and any pending top-up. Accounts on legacy credit plans get 404 FEATURE_NOT_AVAILABLE.
