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.
- Connects with an API key
- Free 14-day trial
- No credit card
Start a research run on Acme's pricing page and summarize it
Working in TinyFish with Elaichi
-
List all TinyFish browser context profiles
-
Get single TinyFish browser context profile by ID
-
List all TinyFish browser session usage records
How to connect TinyFish to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
TinyFish MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
TinyFish MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with TinyFish through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in TinyFish is logged.
-
Sales
Research a prospect before the call
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.
-
Marketing
Watch competitor pricing pages for changes
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.
-
Support
Check a vendor status page right now
Fetch the live page through TinyFish and drop the current status into the ticket without leaving the conversation.
-
Product
Pull page content into a spec
Fetch a documentation page or kick off a research run and bring the findings straight into the document you are writing.
-
Engineering
Keep browser profiles tidy
List, update or delete TinyFish browser profiles, complete or cancel a profile setup session, and remove a stale domain, all from Cursor.
-
Operations
See what the team has been running
List TinyFish browser session and fetch usage records to see how much the team is using and where it is going.
Try asking
- “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”
What connecting TinyFish gets you
6 screens from Elaichi, each doing one job for your TinyFish account.
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about any web page in plain words.
Start a TinyFish research run or check a monitor from one chat box.
Copy the endpoint
AI apps
One endpoint runs TinyFish from every client.
Claude, ChatGPT and Cursor share one governed endpoint, no SDK and no shared API key.
Tool catalog
43 TinyFish tools, no code to write.
Monitors, research runs, fetches, browser sessions and profiles, cataloged and ready to call.
Toolboxes
Each team gets its own TinyFish toolbox.
Sales keeps research runs, marketing keeps monitors, engineering keeps browser profiles.
Shared connections
Share a TinyFish connection, not its key.
One person connects TinyFish, teams work through it, nobody else sees the API key.
Audit log
Every TinyFish call is written down.
When, who, what happened and which monitor or research run, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
TinyFish digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch monitors
TinyFish
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
TinyFish
Queued
Workflows
A schedule runs TinyFish work end to end.
Monitors are fetched, grouped and drafted into a digest a person approves before it posts.
TinyFish health
Refreshed 4 minutes ago · every 15 minutes · from the monitors collection
Monitors
1,284 ↓ 12%
Research runs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Monitors created
Last 14 days
By team
Share of activity
Sales 34%
Marketing 27%
Support 21%
Product 18%
Collections and dashboards
TinyFish health, counted without a model.
Four metrics, 14 days of research runs created, and a breakdown by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
TinyFish tools for your AI agents
43 tools are ready to call through Elaichi's MCP endpoint the moment you connect TinyFish, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put TinyFish in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot