The best MCP tool for Claude depends on the job: choose ToolRouter for hosted specialist tools, Zapier MCP for Zapier app actions, Composio for developer-managed SaaS integrations, and Arcade when each user must authorize actions under their own identity. Use a self-hosted MCP server instead when control of deployment and data flow matters more than managed setup.
| Pick | Best fit | Check before connecting |
|---|---|---|
| ToolRouter | Search, research, SEO, screenshots and other hosted specialist tools behind one Claude connector | Which tools are available in Claude's policy-filtered catalog and the price shown before a paid call |
| Zapier MCP | Actions across Zapier's app and workflow ecosystem | Which apps can be changed, and the Zapier tasks consumed per successful MCP call |
| Composio | SaaS toolkits, OAuth and custom integrations for agents | Tool-call, premium-tool and security add-on charges |
| Arcade | Per-user authorization for production agents | Auth-event and tool-call usage, plus identity-provider setup |
| Self-hosted server | Maximum deployment, credential and data-flow control | Maintenance, authentication, logging and incident ownership |
Setup: connect ToolRouter to Claude. Cowork: Claude Cowork. Terminal: Claude Code.
What are the best MCP tools for Claude?
- ToolRouter — best when Claude needs a managed specialist catalog without deploying a server for every capability.
- Zapier MCP — best when the main job is acting in apps already connected to Zapier.
- Composio — best when developers need broad SaaS toolkits, managed OAuth and custom agent integrations.
- Arcade — best when actions must be authorized and attributed to each end user.
- Self-hosted MCP servers — best when your team must own the runtime, credentials and data path.
These products overlap. Compare the exact tools, permissions, data handling, failure behavior and pricing required for your workflow rather than choosing on catalog size alone.
Claude MCP pricing compared
Prices checked 30 August 2026 on the vendors' official pages. Prices and included usage can change, so verify them before purchase.
| Provider | Current public starting point | Billing detail to watch |
|---|---|---|
| ToolRouter | Free tools; paid skills from $0.005/use; optional Lite $9/mo, Plus $19/mo; Team from $29/seat/mo | Failed paid calls do not charge; provider or BYOK costs can vary by tool |
| Zapier MCP | Available on Zapier plans | Each successful MCP tool call uses two Zapier tasks |
| Composio | Free; Pro $29/mo | Premium tools and optional security or execution features can add usage charges |
| Arcade | Free; Team $25/mo plus usage | Team lists $0.10/auth event and $0.01/tool call |
Sources: ToolRouter pricing, Zapier MCP, Composio pricing, and Arcade pricing.
Why use ToolRouter with Claude?
ToolRouter gives Claude one managed connection for specialist tasks such as current search, research, SEO checks, screenshots and live data lookups. The Claude connector uses ToolRouter's Anthropic-specific endpoint, which excludes standalone AI image, video and audio generation to comply with Anthropic's connector policy. Check the live catalog after connecting instead of assuming every ToolRouter tool is exposed in every client.
This is different from an app-action platform. If Claude primarily needs to update a CRM, send app data or run Zaps, Zapier MCP or Composio may be the better first connection. If every action must run as a specific employee, compare Arcade's per-user authorization model.
ToolRouter vs self-hosted MCP servers
| Factor | ToolRouter | Self-hosted MCP servers |
|---|---|---|
| Connection | One managed endpoint for the catalog available to that client | One or more endpoints you deploy and configure |
| Credentials | ToolRouter-managed access or BYOK where supported | You manage server and provider credentials |
| Operations | ToolRouter operates the gateway and catalog | You own hosting, updates, logs and uptime |
| Cost | Free or usage-based tools, plus optional plans | Infrastructure, maintenance and provider costs |
| Control | Subject to ToolRouter, client and provider policies | Greater control over deployment and data flow |
Use least-privilege credentials either way. Review tools that can write, delete, spend credits or contact people before allowing them to run without confirmation.
How does ToolRouter work across Claude and other assistants?
The account and gateway can be shared, but setup and catalog policy differ by client:
- Claude chat, desktop, mobile and Cowork — use the filtered remote connector in Connect Claude.
- Claude Code — use the local MCP package in Connect Claude Code.
- ChatGPT — create a custom MCP app using Connect ChatGPT.
- Grok at grok.com — add the verified chat connector using Connect Grok.
- Grok Bot — this is a separate downloadable product with account-dependent custom MCP availability; see Connect Grok Bot.
- Gemini CLI — the documented path is the command-line client, not consumer Gemini chat; see Connect Gemini CLI.
- Microsoft Copilot — the documented path is Copilot Studio, not every consumer Copilot surface; see Connect Copilot Studio.
The most useful MCP tool categories for Claude
Web search and deep research
Search tools are useful when Claude needs current sources rather than model memory. Look for dated results, direct source links, geographic or language controls and clear limits. Deep research tools add multi-source synthesis, but you should still inspect the underlying citations before relying on a claim.
ToolRouter exposes web search and deep research where the current client catalog permits them.
SEO and website inspection
SEO tools can check metadata, headings, crawl signals and search performance. A useful output should separate observed page facts from recommendations. For live rankings or Search Console data, verify the date, property and source rather than treating a generated suggestion as measurement.
Browse ToolRouter's SEO tools and confirm the exact skill available in Claude before running an audit.
Screenshots and web extraction
Screenshots help with rendered-page QA, while extraction tools turn pages into structured data. Check support for JavaScript-rendered pages, crawl limits, schemas, retries and website access rules. A scraping tool does not remove your responsibility to respect permissions and terms.
Live data and specialist APIs
Weather, market, company, geographic and other specialist APIs can give Claude current structured data. For consequential decisions, require source names and observation timestamps, and treat generated commentary separately from the returned facts.
For concrete workflows, see how to analyze stocks with AI assistants and how to get satellite images by date and location.
Audio transcription and file processing
Transcription tools turn uploaded audio into text, timestamps and sometimes speaker labels. Check supported file types, duration limits, privacy terms and whether speaker diarization is actually returned. See how to transcribe audio with AI assistants for client-specific setup and verification.
Media generation
Image, video and audio generation are useful MCP categories in clients that permit those tools. ToolRouter's Anthropic-specific Claude connector excludes standalone AI image, video and audio generation to comply with Anthropic's connector policy. Do not assume a media tool visible in ToolRouter's broader catalog is available inside Claude; check the live Claude catalog first.
How to evaluate an MCP server before connecting it
Use this checklist for any provider:
- Task fit: can it complete the exact job, not just return a plausible description?
- Client support: is the setup verified for the Claude surface you use?
- Permissions: which tools can read, write, delete, spend money or contact people?
- Result evidence: does the response include sources, timestamps, identifiers or downloadable outputs?
- Failure behavior: are failed and partial calls clearly reported?
- Cost: what is charged per tool call, provider call, task, auth event or seat?
- Data handling: where are prompts, credentials and tool outputs processed or retained?
- Operations: who owns authentication, updates, logs, uptime and incident response?
For sensitive workflows, start with read-only tools and least-privilege credentials. Anthropic advises users to connect only to trusted servers, review requested permissions and inspect approval requests before choosing Allow always; see its custom connector security guidance.
ToolRouter Claude MCP FAQ
Is ToolRouter the only MCP tool Claude needs?
No. ToolRouter is a specialist catalog. Add Zapier MCP or Composio for app actions, Arcade for per-user authorization, or a self-hosted server for a proprietary system.
Does ToolRouter work in Claude chat, Cowork and Claude Code?
Yes, through different setup paths. Claude chat, desktop, mobile and Cowork use the remote connector; Claude Code uses the terminal setup. Follow Connect Claude and Connect Claude Code.
Does Claude Free support a custom MCP connector?
Anthropic says Free users can add one custom connector. Team and Enterprise Owners must first add a connector for their organization, after which members connect individually. See Anthropic's current custom connector guide.
Can ToolRouter generate images or video inside Claude?
Not through ToolRouter's Anthropic-specific connector. That catalog excludes standalone AI image, video and audio generation. Use a client and connection path that permits those tools, then confirm the live catalog before paying for a call.
Can one ToolRouter bill cover a team using several assistants?
Yes. Team plans provide shared billing and usage visibility, while each assistant still has its own connection method and catalog policy. See ToolRouter for teams.
Compare more: ToolRouter vs Zapier MCP · ToolRouter vs Composio · ToolRouter vs Arcade · All comparisons.