tinyfish — Claude Code plugin: what it does and setup
Gives Claude Code web search, page extraction, browser automation, and monitoring. The first call uses OAuth unless you provide an API key.
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tinyfish@claude-communityWhat tinyfish does
tinyfish connects Claude Code to TinyFish’s hosted MCP server through .mcp.json. The /tinyfish:search skill searches the web with date or topic filters, while /tinyfish:fetch returns clean Markdown from up to 10 URLs in parallel, including JavaScript-heavy pages.
Use /tinyfish:agent to send a browser agent to a site, fill forms, reuse logged-in browser profiles, or return structured data. /tinyfish:monitor checks a page or search topic on a recurring basis and posts results to a webhook. Search and fetch are free; automation and monitoring charge the TinyFish wallet. A completed monitor check costs $0.005.
The first request opens an OAuth sign-in, or you can set TINYFISH_API_KEY. The web skills do not read local files. /tinyfish:doctor runs npx @tiny-fish/cli doctor and tests the service connection, while /tinyfish:feedback prepares a GitHub issue through gh and waits for approval. /tinyfish:agent and /tinyfish:monitor require wallet credit because those operations are billed.
What it helps with
- search the web with recency filters
- extract Markdown from JavaScript-heavy pages
- fill a form and collect structured data
- send recurring page checks to a webhook
Example prompts for the agent
- Run
/tinyfish:searchto find recent research on this topic and filter the results by date. - Use
/tinyfish:fetchon these URLs and return clean Markdown for each page. - Ask
/tinyfish:agentto open the site, complete the form, and return structured results.
How to install tinyfish
Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install tinyfish@claude-communityStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about tinyfish
How do I install tinyfish in Claude Code?
Add the marketplace with /plugin marketplace add anthropics/claude-plugins-community, then install the plugin with /plugin install tinyfish@claude-community.
What does tinyfish do?
It adds web search, page extraction, browser automation, and recurring monitoring to Claude Code through the TinyFish MCP server.
What authentication does tinyfish require?
The first use can start an OAuth sign-in. You can instead set TINYFISH_API_KEY; browser automation and monitoring use paid TinyFish wallet operations.
Source text
claude · MIT
# TinyFish The complete web toolkit for your agent — search, fetch, browser automation, headless browser control, and website monitoring. ## Skills `search`, `fetch`, `agent`, and `monitor` are built on TinyFish's hosted MCP server (bundled via `.mcp.json`). No install, no CLI needed — first use triggers an OAuth sign-in to your TinyFish account, or set an API key (see Authentication). Search and fetch are free; automation and monitor checks are billed to your TinyFish wallet, and new users get $8 in sign-up credits. They work in any environment, including sandboxed surfaces without terminal access. - **`/tinyfish:search`** — free, token-efficient web search with flexible recency/date filtering and news/research-paper scoping - **`/tinyfish:fetch`** — free, clean content extraction from up to 10 URLs in parallel, including JS-heavy pages - **`/tinyfish:agent`** — browser automation billed to your wallet: natural-language goals, saved logged-in browser profiles, and raw CDP browser sessions - **`/tinyfish:monitor`** — recurring checks on a page or a search topic, with results sent to a webhook: $0.005 per completed check, failed checks are free The remaining two are setup tools rather than web tools, and both use your terminal: - **`/tinyfish:doctor`** — diagnose and repair your TinyFish setup. Runs the TinyFish CLI (`npx @tiny-fish/cli doctor`) for the config checks, then calls a TinyFish tool to prove this agent can actually reach the service. Without a terminal it still runs that second half. - **`/tinyfish:feedback`** — file a bug report or a doctor diagnostic as a GitHub issue on the public `tinyfish-io/tinyfish-cookbook` repo, via `gh`. Nothing is sent until you approve the exact text. ## Authentication Two ways in, no configuration to choose between: - **API key** — grab a key at https://agent.tinyfish.ai/api-keys and `export TINYFISH_API_KEY="sk-tinyfish-…"`; the plugin sends it as `X-API-Key`. No browser sign-in. - **OAuth** — with no key set, or a key the server rejects, the connection falls back to the OAuth sign-in prompt. ## Desktop setup note In Claude Desktop, installing this plugin enables its skills but the bundled `tinyfish` MCP connector still needs one manual step: open the plugin's **Connectors** tab and click **Install** on `tinyfish` before the skills can actually call it. ## Privacy TinyFish's privacy policy: https://www.tinyfish.ai/privacy-policy ## Local file access `search`, `fetch`, `agent`, and `monitor` read no local files — every operation goes through the TinyFish MCP server. The two setup skills do touch your machine: - **`/tinyfish:doctor`** runs the TinyFish CLI, which reads your agent config directories (`~/.claude`, `~/.codex`, `~/.cursor`, `~/.grok`, `~/.hermes`, `~/.openclaw`, `~/.config/opencode`) and the CLI credential store (`~/.tinyfish/config.json`) to find where TinyFish is registered. Diagnosis reads those files and makes authenticated calls to TinyFish to test what it found; the repair step rewrites the registrations, and only commands the CLI itself proposes. `doctor` reports its own run to TinyFish — set `TINYFISH_NO_TELEMETRY` to suppress that and the `tinyfish connect` a repair re-runs. - **`/tinyfish:feedback`** shells out to `gh issue create` against a public repo, after showing you the exact issue text and waiting for your approval.
© tinyfish-io · MIT · tinyfish-io/tinyfish-web-agent-integrations
