--- title: "Extend Muse AI With Custom MCPs: TinyFish, Composio & Fish Audio" description: "Muse lets you plug in custom MCP connectors with a single message. Here's how I added TinyFish for free search and fetch, Composio for 1,600+ tools, and Fish Audio for media — plus the skills trick that makes them stick." date: 2026-10-16 categories: ["ai"] tags: ["muse","tinyfish","composio"] --- import Button from "@components/widgets/Button.astro"; import Notice from "@components/widgets/Notice.astro"; import ListCheck from "@components/widgets/ListCheck.astro"; import Accordion from "@components/widgets/Accordion.astro"; Muse comes with a decent set of built-in tools and connectors, but the defaults only go so far. Its web search burns tokens on heavyweight browser sessions, and half the services I actually use — Search Console, my YouTube stats, keyword tools — aren't on Meta's list at all. The fix is that Muse accepts custom MCP connectors, and adding one takes a single message. You literally ask the agent to connect a service; it figures out the integration, builds a connector card with a secure form for the API key, verifies the calls, and saves a reusable skill so it knows when to use the tool later. This post walks through the three connectors I added — TinyFish for free search and fetch, Composio for 1,600+ SaaS tools, and Fish Audio for media generation — plus the skills pattern that makes the whole setup reliable. - A Muse account — my [Muse invite guide](/muse-ai-meta-agent/) covers signup and a 1-billion-token invite code - A free TinyFish API key from [agent.tinyfish.ai](https://go.bitdoze.com/tinyfish) — no credit card - Optional: a [Composio](https://composio.dev) account if you want the 1,600-tool catalog — free tier covers ~100,000 requests/month ## How custom connections work in Muse Before the specifics, the general flow — because it's the same for every connector and it's the part that makes Muse unusual. You ask in chat: ```text How can we add TinyFish for search and fetch in you? They have an MCP and CLI with API key. ``` Muse reads the provider's docs or repo itself, picks the integration that fits, and renders a **connector card** in the conversation. You hit Connect, a secure form opens, and the API key goes straight into encrypted storage — never through the chat transcript. Then it proves the wiring with live calls before declaring it done. Once connected, every integration shows up under **Settings → Connections → Connected**, and Muse typically creates a **custom skill** on its own — a saved routine telling it when to reach for that tool. Three connectors in, I have TinyFish MCP and Composio MCP sitting there like first-class integrations, plus the skills to drive them. If Muse offers a connector card, always enter keys through it — that path writes to encrypted storage directly. If a key ever ends up in a message, tell Muse to move it to the vault and not print it again. ## TinyFish: better search and fetch The one I set up first, because Muse's built-in browsing is the expensive way to read the web. The browser is a real Chromium and it's great for interactive work — logins, forms, checkout flows — but every page it opens comes back loaded with markup the agent has to chew through. [TinyFish](/tinyfish-ai-agents-web-search/) returns clean JSON and markdown instead, and Search + Fetch are free at 30 requests and 150 URLs per minute. My [coding-agent setup guide](/tinyfish-free-search-coding-agents/) covers the same pairing for CLI agents. Muse evaluated the three options (the MCP server, the `@tiny-fish/cli` package, plain REST) and on my first run picked REST. On the second I asked for the **MCP** route explicitly — that's the one to choose, because the TinyFish MCP exposes all of their tools rather than just the two free endpoints, and it lands under Settings → Connections like a native integration. Verification was immediate: a search for "TinyFish web agent" came back as ranked JSON with titles, URLs, and snippets, and fetching `tinyfish.ai` returned the full page as clean markdown in about half a second. In daily use it handles "search today's news with TinyFish" or "fetch this article and summarize it" without a browser session — the last fetch I ran summarized a full article through the MCP in one call. Fetch batches up to 10 URLs at once, and the metered Agent/Browser automation endpoints stay off unless you ask for them. Two extras worth knowing once it's wired: - **Monitor** — scheduled page/topic watches with diffs, webhook, and email delivery. Pair it with Muse Goals and the agent decides whether a change matters while TinyFish does the cheap watching ($0.005/run on top of the free allowance). - **Research API** — a beta endpoint that synthesizes a cited report across multiple sources. Handy as a second opinion next to Muse's own deep research; details in my [TinyFish review](/tinyfish-ai-agents-web-search/). ## Composio: one MCP for 1,600+ tools TinyFish fixes web reading. [Composio](/composio-mcp-guide/) fixes everything else — it's an MCP aggregator exposing roughly 1,600 tools (Gmail, YouTube, Reddit, Google Search Console, Plausible, Ubersuggest, and on down the SaaS catalog) through a single connection, with about 100,000 requests/month on the free tier. Setup follows the same pattern. In Composio's dashboard you connect the apps you want — mine currently has Gmail, YouTube, Reddit, Fish Audio, Google Search Console, Plausible Analytics, and Ubersuggest for keyword research — then copy the MCP endpoint and API key from the Sessions section, and ask Muse to configure it. Same connector card, same secure key form. The payoff showed up fast. I asked for a report pulling my Search Console data for this site plus my YouTube channel stats with keyword lookups, and it produced a proper document — subscriber count, which recent videos are pulling the most views, search performance — without me opening a single dashboard. That's the point of the aggregator: one connector, and a whole workday's worth of "log into five tools and copy numbers" collapses into a request. If you want the deeper dive on what Composio's MCP can do beyond this, my [Composio MCP guide](/composio-mcp-guide/) walks through the platform on its own. ## Fish Audio: media generation (with caveats) Third connector, and the one where honesty matters. [Fish Audio](/fish-audio-review/) gives Muse access to image, audio, and video generation plus voice cloning — useful for YouTube thumbnails and narration. I went in through Composio, so it rides the same MCP. It does not work out of the box reliably. My first thumbnail request through the GPT Image 2.5 Sunburst model failed outright; switching the same prompt to Nano Banana produced a genuinely usable thumbnail against my spec. Generations show up in the chat and land in Muse's Library — occasionally needing a manual download when the artifact doesn't attach cleanly. So: worth connecting, but expect to babysit model choice until the flaky ones sort themselves out. If media generation is the goal, my [Fish Audio review](/fish-audio-review/) and the [image/video generation guide](/fish-audio-image-video-generation/) cover what the platform handles standalone. ## The skills trick that makes it all stick Here's the piece I'd tell anyone to copy. An MCP gives Muse *access* to tools; a **skill** teaches it *how to use them well*. Muse auto-created one for TinyFish — the search-first-then-fetch escalation, so it stops reaching for the browser when a clean API call will do. For everything else, I write the skill myself. For the thumbnail work, I dropped the same skill spec I use in my other agents into Muse's memory — which model to call, what the output format should be, when to retry with a different model. You can do it the lazy way too: just tell Muse "create a custom skill for this MCP so you know what to do," review what it writes, and edit. The skill files live in Muse's editable memory, so they're yours to fix. The pattern that works: one MCP for access, one skill for judgment. Wire the connector, then immediately ask Muse to draft the skill, then tune it. Five extra minutes per tool, and the difference between an agent that *can* call an API and one that knows *when*. ## Practical prompts to try - "Add TinyFish search and fetch — use their MCP and walk me through connecting." - "Search today's news on `` with TinyFish, then fetch the top two results." - "Fetch this article with TinyFish and summarize it for me." - "Connect my Composio MCP and check which tools are available." - "Pull a report from Search Console and my YouTube stats through Composio." - "Create a YouTube thumbnail for ` ## What works and what doesn't **What works:** The connector flow itself is the headline — one message, secure key form, verified calls, saved skill. TinyFish Fetch is the clear daily win (clean markdown, free, cheap on tokens). Composio turns cross-tool reporting into a single request. And MCPs you add land under Settings → Connections like they shipped with the product. **What doesn't:** Third-party tool reliability varies — Fish Audio failed on one model and worked on another, so expect some babysitting. TinyFish Search can lag a few minutes behind breaking news. The Research API is beta. And none of this replaces Muse's browser for anything interactive: logins, clicks, and form fills still need the real Chromium. ## FAQ Just ask it. Tell Muse the tool name and that it has an MCP or API, and it will research the integration, build a connector card, and collect your API key through a secure Connect form. Connected tools appear under Settings → Connections → Connected. The tools I used are free at this scale — TinyFish Search and Fetch cost nothing (30/min and 150 URLs/min), Composio's free tier covers ~100,000 requests/month, and Fish Audio rides your existing plan. Muse only spends the small number of tokens needed to issue each call and read the result. Keys entered through the connector's secure form go into encrypted storage and ride along only on requests to that provider's hosts — they don't pass through the chat transcript and Muse can't echo them back. Rotating a key is easy if you ever doubt it. The MCP. It exposes all of TinyFish's tools through one connection and shows up as a managed integration under Settings → Connections. Plain REST works too — Muse wired that up on my first attempt — but it's limited to the two free endpoints and you maintain it yourself. Yes. Connectors and keys live on your Muse VM, not on a device. Anything you ask from mobile, WhatsApp, or the web app executes on the same VM, so a connector you set up once works from every surface. ## Bottom line Muse's built-in tools are the floor, not the ceiling. One message per service — TinyFish for cheap clean web access, Composio for a 1,600-tool catalog, Fish Audio for media — and the agent grows connectors, encrypted credentials, and skills to match. The trick that makes it durable is asking Muse to write a skill per connector so it knows when each tool earns its place. Twenty minutes of setup, and the "personal agent" pitch stops being hypothetical.