Workflow Automation · TinyFish + Claude

TinyFish MCP with Claude: Automate Web Research and Repeatable Browser Workflows

The short answer

Claude works with TinyFish through the Model Context Protocol (MCP), an open standard that lets Claude use the tool securely. Once connected with an API key, Claude can start browser sessions, run live web searches, extract page content and manage automation runs using plain-language instructions, with permissions your organisation sets.

What is TinyFish?

TinyFish is a web automation platform. It runs browser sessions, performs live searches across the web and extracts content from pages. Typical users include research teams, operations staff, analysts and developers who need the same web tasks done again and again, such as checking prices, collecting public information or gathering data from sites that have no export option. It lets organisations turn manual browsing into repeatable, scheduled workflows.

How Claude connects to TinyFish through MCP

The Model Context Protocol (MCP) is an open standard that works like a universal adapter between Claude and other software. It lets Claude use a tool securely, reading information and taking actions, with the access rights the organisation chooses. Instead of copying and pasting between windows, Claude talks to the tool directly through a defined connection.

Once TinyFish is connected, Claude can typically ask for a live search, open a browser session, pull the content of a page and report back what it found. It can also check on or manage automation runs. Requests are made in ordinary language, so a researcher can ask for a summary of competitor pricing pages without writing code.

Access is controlled by the API key you provide, which can be limited to the permissions your team needs. Consequential actions can require a person's approval before they run, and activity can be logged for review. This keeps people in charge of what Claude does with the tool.

What you can automate

  • Competitor price monitoring

    A pricing analyst asks Claude to visit a set list of competitor product pages each morning. TinyFish opens the pages in browser sessions and extracts the listed prices. Claude compares them with last week's figures and highlights changes. The analyst reviews the summary rather than checking dozens of sites by hand.

  • Market and news research

    A strategy team needs a briefing on a new regulation or market. Claude uses TinyFish live search to find recent articles and official publications, extracts the relevant text, and drafts a short source-linked summary. Staff verify the key sources before the briefing is shared.

  • Supplier and vendor checks

    A procurement officer needs to confirm that suppliers still list the right certifications or contact details on their public websites. Claude runs repeatable browser checks across the supplier list, flags missing or changed information and lists exceptions for the procurement team to follow up.

  • Lead list enrichment

    A sales operations manager has a list of companies without complete details. Claude uses TinyFish to visit public company pages and extract the publicly listed information, such as industry and headquarters location. The results are cleaned and sent for review before being added to the CRM.

  • Routine compliance evidence

    A compliance team must capture how certain public web pages look and what they say at set dates. Claude runs scheduled browser sessions, extracts the content and stores a dated record, so staff have consistent evidence without manual screenshots.

An end-to-end workflow: Weekly competitor pricing report to Microsoft 365

TriggerEvery Monday at 07:00, or when a marketing manager asks Claude for an update.

  1. Claude reads the list of competitor product URLs stored by the marketing team.

  2. TinyFish opens a browser session for each page and extracts the current prices and offer details.

  3. Claude compares the results with the prior week and identifies price changes above an agreed threshold.

  4. Claude drafts a summary table and a short commentary in plain English.

  5. The marketing manager reviews and approves the draft before it is released.

  6. The approved report is saved to a shared Microsoft 365 folder and a notification is sent to the team in Microsoft Teams.

OutcomePricing changes are spotted within hours instead of weeks, and the marketing team spends its time on decisions rather than data collection.

How we set it up

  1. Free automation audit

    We review your current web research and checking tasks and identify which ones are repetitive enough to automate with TinyFish and Claude.

  2. Secure connection

    We set up the TinyFish connection to Claude using your API key, with access limited to the permissions each workflow needs. The key is stored securely and never shared in chat.

  3. Workflow design

    We design the end-to-end process across TinyFish and your other systems, such as Microsoft 365, your CRM or ticketing tool, and decide where people must approve actions.

  4. Testing with real cases

    We test the workflow against past examples from your business, check the extracted results for accuracy and adjust instructions until the output meets your standards.

  5. Launch, monitoring and training

    We launch with audit logs and monitoring in place, then train your team to run, review and maintain the workflow.

Who benefits

Research and insight managers
Gather and summarise public web information in hours rather than days, with sources recorded.
Operations leaders
Replace repetitive browsing tasks with scheduled, consistent runs that staff can review.
IT and security heads
Connect a web automation tool using a single API key, with access limits and audit logs.
Sales and marketing teams
Keep competitor, pricing and lead data current without manual website checks.

Security and control

  • Use an API key with the narrowest permissions needed for each workflow, and rotate it on a set schedule.
  • Require human approval before Claude publishes, sends or saves results that affect customers, suppliers or finances.
  • Respect website terms of service and robots rules, and automate only pages your organisation is permitted to access.
  • Keep audit logs of every browser session and automation run so results can be traced and reviewed.
  • Test extraction accuracy on known examples before relying on any workflow for decisions.

For teams in the US, UK, India and the Middle East

Organisations in the United States and the United Kingdom can run TinyFish workflows with Claude while meeting their data protection and contractual obligations. In India, workflows are designed to align with the Digital Personal Data Protection Act, 2023. For organisations in the UAE and Saudi Arabia, we consider local data protection laws when designing workflows. We choose the Claude hosting region to meet your specific legal and residency requirements.

Learn more about Claude and MCP

Frequently asked questions

What does the TinyFish MCP server do?

The TinyFish MCP server is the connector that lets Claude use TinyFish securely. Through it, Claude can start browser sessions, run live web searches, extract page content and manage automation runs. It translates plain-language requests into actions in TinyFish and returns the results to Claude, within the permissions you set.

Is it secure to connect TinyFish to Claude?

It can be, when set up carefully. Access is controlled by your API key, which should be limited to the permissions each workflow needs and rotated regularly. We add human approvals for important actions and keep audit logs of activity. We also check that automated browsing respects website terms and that your data handling meets applicable law.

What can Claude do with TinyFish once connected?

Typically, Claude can request live searches, open browser sessions on specified pages, extract content, compare results and report findings. It can also check the status of automation runs. Claude follows your instructions and the limits you configure, so the exact actions depend on the workflow we design together.

How long does setup take?

A simple single-task connection can be set up quickly once the design is agreed. A full workflow with testing, approvals, other system connections and team training usually takes several weeks. The free automation audit gives a clearer timeline for your specific needs.

What access or plan do we need?

Generally, you need an active TinyFish account and an API key with permissions suited to the work you want to automate. The exact plan and permission level depend on your usage and your TinyFish arrangements, so we confirm these during the free automation audit before any connection is made.

Book a free automation audit for TinyFish

Book a free automation audit and we will identify the web research and browser workflows in your business that are worth automating with TinyFish and Claude. You can also e-mail our team to start the conversation. You can also e-mail contact@mindarora.com.