Arcade Tools Catalog

Arcade’s public tools catalog is useful in two ways: as a directory of agent actions and as a reference for designing a browsable integration marketplace. It is aimed at developers choosing tools for an AI agent and product teams deciding how to explain capabilities before a user connects an account.

The catalog has a search field and categories such as Communication, Developer Tools, Databases, and Sales & CRM. Each integration card names the service, summarizes what an agent can do, previews specific actions, and shows its category; some cards also carry BYOC or Pro labels. That is a practical discovery pattern: visitors can start from a service name or a task area, then judge whether the listed actions match their workflow without opening every result. The GitHub detail page goes deeper with an OAuth label and a named list of available actions, including creating issues, reading repository content, and managing pull requests. These pages are product listings, not a guarantee that every action is available to every account.

Arcade’s actual offering extends beyond the directory. Its tool documentation describes prebuilt MCP servers and custom tool development, while its authorization guide explains how a tool can request user consent for provider access and receive a token in its execution context. Arcade also documents MCP gateways that expose selected catalog tools to a client. To get started, search the catalog for a service, inspect its action list and auth label, then use Arcade’s docs and account setup to connect only the tools the agent needs. A catalog listing alone does not connect an agent or authorize access to someone’s data.

For product inspiration, study the transition from compact cards to action-level detail. The category and search controls help users narrow a large inventory; named actions make scope legible; auth labels set expectations before setup. Arcade’s precise integrations and availability can change, so verify a chosen tool’s current documentation and required permissions before designing a workflow around it.

Example use cases

Suggested application — integration picker: Prototype a searchable catalog where each card previews three agent actions and links to a full capability page.
Suggested application — permission review: Show an auth requirement beside each action, then test whether users understand what account access an agent will request.
Suggested application — workflow planning: Compare the catalog’s GitHub and Slack action lists to identify the smallest set of tools needed for an issue-triage assistant.

Sources

Source image: Arcade official sharing image.

Arcade Tools Catalog.