Connect Plaid to Raycast
Give Raycast governed access to Plaid’s 5 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Plaid to Raycast in four steps
Admins approve the server once. Everyone in Raycast then gets it through the same governed connection.
- 1
Add Plaid to Runlayer
Plaid isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Raycast to Runlayer
Users add the Runlayer Plugin to Raycast by following Runlayer’s setup guide. Raycast reaches Plaid’s 5 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Raycast setup guide - 3
Sign in to Plaid
Sign in the way Plaid requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Plaid from Raycast
Plaid’s approved tools appear in Raycast. Every call is checked against policy and recorded.
Tools
5 Plaid tools in Raycast
Runlayer policy decides which of these Raycast users can call.
Debug item
Diagnose a Plaid item by retrieving its state information.
Get link analytics
Retrieves Plaid Link analytics data for analyzing user conversion and error rates.
Get tools introduction
Returns a list of all available tools with a brief introduction for each.
Get usages
Retrieves usage metrics for Plaid products and services.
List teams
Retrieve teams associated with the user and present them as a selectable list.
Control
What Runlayer can see and stop in Raycast
Some controls apply to every client at the gateway. Others depend on what Raycast exposes to Runlayer.
Gateway policy (available)
Every Plaid call from Raycast passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Raycast as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Raycast yet, so control happens at the gateway.
Frequently asked questions
Connect more