IonBin
All pages
Search
Agent-ready

How each tool connects to your AI agent

Start with the connection method, then check the actions and access it supports. IonBin records four routes using vendor documentation. A documented capability is not proof that a complete workflow has been tested. Unverified claims say "to verify".

Covers 166 listed tools. Tools whose verdict is still in review are left out of every count on this page.

MCP

Native connector / MCP

The vendor documents an official MCP server or native connector. Supported actions, clients, account requirements and authentication vary; check the linked source for each tool.

122 documented · 38 to verify
API/CLI

API / CLI

A public API or command-line tool. Agents reach it through an automation hub (n8n, Make, Zapier) or a little code.

150 documented · 15 to verify
Browser

Browser / manual

Browser access is recorded, but this listing has no confirmed MCP or API route. A person can use the interface; automated browser control needs its own compatibility check. Other routes may still exist.

12 manual listings
File import

File upload / import

Documents a file-upload or import route. Supported formats, file counts and size limits vary. This does not establish bulk processing, export support or automatic agent access.

127 documented · 36 to verify
How we assign levels

"Native connector / MCP" records an official vendor server or connector; community servers do not qualify for that label. "API / CLI" records a public API or official command-line interface. "File upload / import" records an input route; it does not establish bulk processing or export support. Supported operations, authentication, plans and compatible clients must be checked for the specific task.

An MCP client uses a server; supporting one role does not establish the other. Local servers commonly use stdio, while remote servers use Streamable HTTP. A client must support the server's transport, authentication and required capabilities. See the MCP architecture documentation.

"Browser / manual" means browser access is recorded but this listing has no confirmed MCP or API route. A person can use the interface. It does not mean other routes are impossible, and it does not establish that an agent can automate the browser.

The latest recorded connection-check date among listed tools is Oct 21, 2026; each tool carries its own date and sources. These dates identify source-review records, not proof of a successful live integration. Inferred pairings need a separate compatibility test. See the evidence definitions. 89 individual levels are still marked to verify.

MCP

Native connector / MCP

Filter the directory →

To verify

API/CLI

API / CLI

Filter the directory →

To verify

Browser

Browser / manual

Filter the directory →
File import

File upload / import

Filter the directory →

To verify

Agent platforms

Where the agent runs

PlatformUses MCP serversDocumented scope
BotpressTo verifyA client-specific source and its supported actions still need review.
Browser UseTo verifyA client-specific source and its supported actions still need review.
ChatGPTYes, documentedThe desktop app, CLI and IDE share MCP configuration for the same Codex host. ChatGPT web uses remote MCP tools through plugins; it does not read local config.toml.
ClaudeYes, documentedCustom connectors via remote MCP; Claude Code adds local or remote MCP servers
CursorYes, documentedmcp.json and marketplace; CLI and cloud agents supported
Gab AITo verifyMCP client support not found in the docs reviewed
Gemini (Google)Yes, documentedCustom MCP apps: personal Google Account, age 18+, US, English and Keep Activity on. Set up in the web app, then use on web or mobile.
Google AntigravityYes, documentedMCP servers from the MCP Store or a config file
GrokYes, documentedCustom MCP connectors are documented for users of the Grok app; the server must be reachable from the app over the public internet. Business/Enterprise admins provision connectors.
Grok BotYes, documentedPlugins directory; e.g. Railway plugin connects via its hosted MCP server (custom MCP servers to verify)
LindyTo verifyA client-specific source and its supported actions still need review.
LM StudioYes, documentedActs as a host for local and remote MCP servers.
Mistral VibeYes, documentedMCP connectors extend access to tools.
OpenAI CodexYes, documentedThe desktop app, CLI and IDE share MCP configuration for the same Codex host. ChatGPT web uses remote MCP tools through plugins; it does not read local config.toml.
Relevance AITo verifyA client-specific source and its supported actions still need review.
Automation hubs

Connect through an automation hub

A hub may connect through a supported integration or a configured API request. Check authentication, available actions, plan limits and the target API's rules. Exposing a workflow as an MCP tool also requires support and configuration in the chosen hub.

ElevenLabs is a trademark of its owner. IonBin is an independent publisher and is not affiliated with, sponsored by, or endorsed by ElevenLabs. Product names are used for identification and review purposes only.