# TinyFish MCP Server > **TinyFish MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to TinyFish. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/tinyfish > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About TinyFish MCP for running AI-driven browser automation tasks, deep web research, persistent browser login profiles, remote CDP browser sessions, and agentic wallet payments. --- ## Details - Server ID: `tinyfish` - Version: 1.0.0 - Tools: 37 - Authentication: API key, held by MewCP - Calls served: 58 - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — TinyFish has to be in the toolset first. In order: 1. Add TinyFish to your toolset at https://mewcp.com/mcp/tinyfish 2. Connect your TinyFish account (API key); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (37) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `run_browser_automation_sse` _(write)_ — Runs a browser automation task and streams its Server-Sent Events to completion synchronously, blocking until a terminal `COMPLETE` event arrives, then returns… - `start_automation_async` _(write)_ — Creates and enqueues a browser automation run, returning its `run_id` immediately without waiting for the run to finish. Poll a separate status tool with the… - `run_browser_automation_sync` _(write)_ — Executes a browser automation task synchronously, blocking until it finishes, and returns the final status, result, and error in one response. Runs created… - `list_runs` _(read)_ — Lists automation runs with optional filtering by status, goal text, and creation date range. Returns paginated run summaries plus a total count, sorted… - `get_run` _(read)_ — Retrieves full details for a single automation run by ID, including its status, goal, extracted result, step-by-step trace, and any error information. Use… - `cancel_run` _(write)_ — Cancels an in-progress automation run by ID. Only runs started via the async or SSE automation endpoints can be cancelled — a run started via the synchronous… - `get_runs_by_ids` _(read)_ — Retrieves multiple automation runs by ID in a single request, returning each found run's status, goal, result, and error alongside a list of any IDs that were… - `cancel_runs_by_ids` _(destructive)_ — DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Cancels multiple in-progress automation runs by ID in a single bulk call (1-100 IDs). Only… - `get_step_screenshot` _(read)_ — Retrieves the JPEG screenshot captured at a specific automation run step, authenticated with the API key. Returns the image as base64-encoded bytes with its… - `get_step_html_snapshot` _(read)_ — Retrieves the full-page HTML snapshot captured at a specific automation run step, authenticated with the API key. Only available when the run was started with… - `search_web` _(read)_ — Searches the web and returns ranked results with titles, snippets, and URLs, plus the total result count and current page. Location and language each… - `list_search_usage` _(read)_ — Lists search usage records for the authenticated user, returning paginated query details, status codes, and result counts. `limit` defaults to 100 and is… - `fetch_extract_content` _(read)_ — Fetches 1-10 URLs in parallel (rendering JavaScript-heavy pages when needed) and returns clean extracted content as markdown (default), HTML, or a structured… - `list_fetch_usage` _(read)_ — Lists fetch usage records for the authenticated user — URL, format, status, and metadata for each past fetch operation — with page-based pagination… - `get_wallet` _(read)_ — Retrieves the caller's wallet: current balance, auto-reload configuration, per-product contract rates, and any in-flight top-up. `auto_reload: null` means the… - `request_wallet_topup` _(write)_ — Starts a wallet top-up for a USD `amount` and returns a payment challenge — this call alone never moves money, and is as safe as a read despite its CREATE… - `confirm_wallet_topup` _(write)_ — Settles a wallet top-up previously started with `request_wallet_topup`, using a `payment_authorization` credential obtained from the caller's own external… - `create_browser_context_profile` _(write)_ — Creates a new Browser Context Profile — a reusable, isolated browser identity (cookies, local storage, fingerprint) that automation runs can attach to. Returns… - `delete_browser_context_profile` _(destructive)_ — DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Permanently deletes the Browser Context Profile identified by `profileId`, including all its… - `update_browser_context_profile` _(write)_ — Updates a Browser Context Profile's name, default status, or proxy country, returning the full updated profile. Only the fields you provide are changed —… - `create_profile_setup_session` _(write)_ — Starts a temporary setup browser for a Browser Context Profile, returning a `cdp_url` to drive it with Playwright, Puppeteer, or any CDP client. Log in during… - `cancel_profile_setup_session` _(write)_ — Cancels a running Browser Context Profile setup session and discards any unsaved setup state. Requires the `session_id` returned by… - `save_profile_setup_session` _(write)_ — Captures cookies, local storage, and session storage from a running setup session into the Browser Context Profile. Requires the `session_id` returned by… - `upload_browser_context_profile_state` _(write)_ — Uploads cookies, local storage, and session storage directly into a Browser Context Profile, without running a live setup browser session. Writes/merges the… - `delete_profile_domain` _(destructive)_ — DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Permanently removes one domain's saved state (e.g. cookies for that site) from a Browser… - `connect_vault_provider` _(write)_ — Connects a supported password manager (1Password or Bitwarden) and immediately syncs its display-safe credential metadata. Returned items carry only metadata… - `disconnect_vault_provider` _(destructive)_ — DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Permanently disconnects the vault provider connection identified by `connectionId` and… - `sync_vault_items` _(destructive)_ — DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Re-syncs items across every connected vault provider in one bulk call, returning the full… - `run_research_sse` _(write)_ — Runs a research task — searching, evaluating sources, and synthesizing a cited report — and streams its progress to completion synchronously, blocking until… - `start_research_async` _(write)_ — Enqueues a research task and returns its `research_run_id` immediately after durable dispatch, without waiting for completion. Poll `get_research_run` or… - `attach_research_progress` _(read)_ — Reconnects to a research run's live progress stream and blocks until the terminal `done` event, returning the same shape as `run_research_sse`: research run… - `list_research_runs` _(read)_ — Lists saved research runs with optional filtering by status, query text, and creation date range. Returns paginated run summaries plus a total count, sorted… - `get_research_run` _(read)_ — Retrieves one saved research run by ID: its status, quick and deep results, research plan, gathered evidence, and iteration count. `error` here is the run's… - `cancel_research_run` _(write)_ — Cancels a running research run by ID. This call is idempotent: calling it again on an already-terminal run still returns 200 with `cancelled: false` and the… - `list_browser_session_usage` _(read)_ — Lists Tetra browser session usage for the authenticated user — duration, data transfer, mode, and status for each session — with page-based pagination and… - `create_browser_session` _(write)_ — Creates a remote browser session and returns CDP connection details — connect via Playwright's `connect_over_cdp` or any CDP client at the returned `cdp_url`.… - `terminate_browser_session` _(destructive)_ — DESTRUCTIVE — REQUIRES EXPLICIT USER CONFIRMATION BEFORE CALLING. Immediately terminates a remote browser session, releasing its resources instead of waiting… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file, then quit Claude Desktop completely and reopen it 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)