Connect Plaid to Gumloop
Give Gumloop governed access to Plaid’s 5 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Plaid to Gumloop in four steps
Admins approve the server once. Everyone in Gumloop 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 Gumloop to Runlayer
Users add the Runlayer Plugin to Gumloop by following Runlayer’s setup guide. Gumloop reaches Plaid’s 5 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Gumloop 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 Gumloop
Plaid’s approved tools appear in Gumloop. Every call is checked against policy and recorded.
Tools
5 Plaid tools in Gumloop
Runlayer policy decides which of these Gumloop 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 Gumloop
Some controls apply to every client at the gateway. Others depend on what Gumloop exposes to Runlayer.
Gateway policy (available)
Every Plaid call from Gumloop passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Gumloop as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Gumloop yet, so control happens at the gateway.
Frequently asked questions
Connect more