# How to connect Plaid to Grok Bot

```json
{
  "title": "How to connect Plaid to Grok Bot",
  "toolkit": "Plaid MCP",
  "toolkit_slug": "plaid_mcp",
  "framework": "Grok Bot",
  "framework_slug": "grok-bot",
  "url": "https://composio.dev/toolkits/plaid_mcp/framework/grok-bot",
  "markdown_url": "https://composio.dev/toolkits/plaid_mcp/framework/grok-bot.md",
  "updated_at": "2026-11-09T06:01:32.081Z"
}
```

## Introduction

Grok is xAI's assistant, and its bot builder lets you create a personal agent that holds context, runs skills, and connects to the apps you already use through plugins.
This guide explains how to connect Plaid to a Grok bot using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a plugin, authenticate once, then ask your bot to work with Plaid in plain language.

## Also integrate Plaid MCP with

- [ChatGPT](https://composio.dev/toolkits/plaid_mcp/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/plaid_mcp/framework/claude-cowork)
- [Hermes](https://composio.dev/toolkits/plaid_mcp/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/plaid_mcp/framework/atomic-agent)

## TL;DR

Composio exposes 1,500+ apps to your Grok bot through a single connection, so you get:
- Connect to 1,500+ apps with on-demand tool loading, so you do not fill your context window with unnecessary tool definitions.
- Use programmatic tool calling through a remote workbench, letting the model write its own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
- Handle large tool responses outside the model context to keep conversations lean.

## Connect Plaid MCP to Grok Bot

### Connecting Plaid to Grok Bot
Once Grok Bot is set up, you connect Plaid entirely from its interface, and the whole flow takes under a minute.
### Set up Grok Bot
Get access. Grok Bot is included with Cursor Ultra, Cursor Premium Teams, and SuperGrok Heavy. Get the desktop app for macOS or Windows from [x.ai/bot](https://x.ai/bot) and sign in. An iPhone companion app is also available, and your bots sync across devices.
Create a bot. Pick a suggested role or define your own, then give it a short name, one primary job, and a short description of how it should work. Focused bots work best, because a clear role gives the bot more useful context over time.
### Connect Plaid
### 1. Add the Composio plugin
Click the button. The Composio listing on x.ai opens and launches Grok Bot for you. If the app does not open on its own, click Add to Grok Bot.
[Add to Grok Bot](https://x.ai/bot/plugin/32661537)
Grok Bot opens the Composio plugin, showing its connector and skills. Click Add.
### 2. Authenticate
Go to the Installed section and click the Composio entry. You'll see its connector and skills listed.
Click Authenticate. You'll be taken to the Composio consent screen. Review the access it requests and click Authorize. Composio handles the OAuth handshake for you, so you never touch API keys or tokens.
### 3. Connect your Plaid account
Back in the chat, ask your bot to connect to Plaid or give it any Plaid task.
For example, ask it to:
- "List items with highest error rates"
- "Show Link conversion rates last week"
- "Get API volume trends for last month"
It will prompt you to authenticate and authorize access.
That's it. Composio's tools are now available in your Grok bot, and your Plaid account is ready to use.

## What is Grok Bot?

Grok is xAI's assistant, available as a chat interface and a bot builder for creating personal agents that run skills and connect to external apps.
With Composio Connect, your Grok bot can securely access apps like Plaid through MCP without you sharing account credentials directly with the agent.

## What is the Plaid MCP server, and what's possible with it?

The Plaid MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Plaid account. It provides structured and secure access to Item diagnostics, Link analytics, usage metrics, and team information, so your agent can diagnose Items, analyze Link conversion and error rates, review product usage, and list your teams on your behalf.
- Item diagnostics: Have your agent retrieve an Item's current state information to help investigate connection issues.
- Link conversion analysis: Let the agent review Plaid Link analytics to assess user conversion performance.
- Link error analysis: Direct your agent to retrieve Link error-rate data and identify where users may be having trouble.
- Product usage review: Instruct your agent to retrieve usage metrics for Plaid products and services.
- Team discovery: Have your agent list the Plaid teams associated with your account so you can choose the relevant one.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `PLAID_MCP_PLAID_DEBUG_ITEM` | Plaid debug item | Diagnose a Plaid item by retrieving its state information. This tool provides comprehensive information about why an item may not be working properly. Use this tool when you need to diagnose why an item is not functioning as expected In the response, you will see the following information: 1. Item State: - "Never extracted": no extraction has been attempted for this item yet - "Successful": The most recent extraction was successful - "Retrying": The most recent extraction encountered a temporary issue and is being retried - "Needs user attention": The item requires user input and client access is not permitted - "Needs user attention (with access)": The item requires user input but client access is permitted 2. Item Consent State: - Boolean indicating whether the item has active user consent - If an item is not consented, it cannot perform extractions or updates 3. Item Deleted At: - If set to a non-zero value, indicates when the item was deleted - Deleted items cannot retrieve data, and cannot be patched as it is requested by the end users - If the item is not deleted yet, the response will be "not available" 4. Known Issues: - Includes description and status of any known issues affecting the item - May provide insights into ongoing problems with the connection When diagnosing an item, follow this sequence: - First, check if the item is deleted. If yes, the item cannot work properly. - Second, if the item is not deleted but lacks active consent, it cannot function properly. - Third, if the item is not deleted: * Check item state. If it indicates the item needs user attention, the item requires manual intervention. * Note any known issues as supplementary information, though these are usually not the primary cause of problems. - If all diagnostics look normal but the user still reports issues, advise them to contact Plaid support. - If an item is deleted, it is not working properly. It is not patchable, you should suggest the user to create a new item. - If an item is missing active consent, it is not working properly. You should suggest the user to use Update Mode to reauthorize the item. - If an item state indicates it needs user attention, the user should use Update Mode to reauthorize the item. - If running into error "the item does not belong to the team", it means the item is not associated with the team. You must inform the user that the item does not belong to their selected team. You may ask if they would like to try other teams associated with their account, but do not automatically attempt other teams. - If an item cannot be found, it's possible the item is not in the Production environment. When explaining the error, inform the user that this is a possible reason for the error. |
| `PLAID_MCP_PLAID_GET_LINK_ANALYTICS` | Plaid get link analytics | Retrieves Plaid Link analytics data for analyzing user conversion and error rates. Use this tool when you need to: - Analyze Link conversion funnel metrics - Track user progression through the Link flow - Monitor error rates over time - Evaluate Link performance and user experience Some common use cases: - Monitoring Link conversion rates and identifying drop-offs - Analyzing conversion trends over specific time periods - Tracking error patterns and frequency (both by type and total via CountEntities) - Generating comprehensive Link performance reports - Comparing performance across different stages of the Link flow The response includes three main components: 1. Funnel Data (funnel): Tracks user progression through key Link stages with counts: - countAtLinkOpen: Number of users who opened Link - countAtSelectInstitution: Number who selected an institution - countAtHandoff: Number who completed the handoff process 2. Conversion Over Time (conversionOverTime): Time series data showing conversion trends with: - start: Timestamp marking the start of the series - series: Array of named data series, where each contains: * name: Identifier for the conversion metric * data: Array of counts, can contain null values 3. Errors Over Time (errorsOverTime): Time series tracking error occurrences with: - start: Timestamp marking the start of the series - series: Array of named data series, where each contains: * name: Error type identifier (includes "CountEntities" series for total errors across all types) * data: Array of error counts - If user does not provide a date range, please ask them to provide one. You could ask if they want to see the data for the last 30 days and you could use the current date as the end date. Note that the earliest date available for Link analytics data is September 1, 2023 (9/1/2023). |
| `PLAID_MCP_PLAID_GET_TOOLS_INTRODUCTION` | Plaid get tools introduction | Returns a list of all available tools with a brief introduction for each. Use this tool when users ask questions like "What is this Plaid MCP Server?" or "What tools are available?". Your response should follow this format: This is an official Plaid MCP Server made by Plaid. It provides the following functionalities: * - * - ... |
| `PLAID_MCP_PLAID_GET_USAGES` | Plaid get usages | Retrieves usage metrics for Plaid products and services. Use this tool when you need to: - Get usage data for specific metrics over a time period - Track product usage and consumption - Monitor API request volumes - Generate usage reports for billing purposes The data shows how many times each Plaid product was used within the specified date range for certain metrics, with results aggregated by day. Common metrics include number of API calls, authentication requests, and other product-specific usage counts. The key is the product name, and the value is the list of metric types corresponding to that product. - Auth: ["auth-request", "auth-unverified-request"] - Balance: "balance-request" - Identity: ["identity-request", "identity-match-request"] - Transactions: ["transactions", "transactions-add", "transactions-remove", "transactions-active", "transactions-refresh"] - Investments: ["investments-h-add", "investments-h", "investments-h-remove", "investments-h-active", "investments-t-add", "investments-t", "investments-t-remove", "investments-t-active"] - Investments Move: "investments-auth-request" - Liabilities: ["liabilities-add", "liabilities-remove", "liabilities-active", "liabilities"] - Assets: ["assets-add", "assets-pdf-request", "assets-refresh", "assets-refresh-monthly", "assets-audit-request", "assets-history-request"] - Payments: "payment_initiation-initd" - Enrich: "enriched-transaction" - Signal: "momo-frs-eval-request" - Income: ["income-bank-request", "income-bank-refresh", "income-payroll-request", "income-payroll-refresh", "income-document-request", "income-document-parsing", "income-doc-bank-statemnt", "income-document-fraud"] - Statements: "statements-single-doc" - Identity Verification: ["idv-base", "idv-lightning-group-1", "idv-lightning-group-2", "idv-lightning-group-3", "idv-document", "idv-selfie-check"] - Consumer Report: ["cra-bank-income-request", "cra-base-report-create", "cra-base-report-refresh", "cra-network-insights-req", "income-insights-refresh", "partner-prism-attrib", "partner-prism-scores"] - Monitor: ["monitor-wl-rescan-add", "monitor-wl-rescan-remove", "monitor-wl-base"] - Hosted Link Delivery: ["hosted-link-delivery-eml", "hosted-link-delivery-sms"] - Transfer: ["momo-transfer-ach", "momo-transfer-ach-sd", "momo-wire-request", "momo-rtp-request", "momo-transfer-g-ach", "momo-transfer-g-ach-sd", "momo-transfer-authorized", "momo-transfer-manual-req", "momo-transfer-return-unauthorized", "momo-transfer-return-noc", "momo-transfer-return-other"] - If a user asks for a product similar to one on this list and you're 99% confident it's the same product, query for the product on this list and inform them which product you're querying for. Otherwise, do not query an unrelated product. - "momo-frs-eval-request" is the metric type used in the API for Signal. When communicating with users, refer to it as "signal-request" instead. User: "I want to see the usage data for Transactions" Reasoning: The metric types for Transactions are ["transactions", "transactions-add", "transactions-remove", "transactions-active", "transactions-refresh"]. Input parameters: { "metric_types": ["transactions", "transactions-add", "transactions-remove", "transactions-active", "transactions-refresh"], // other fields ... } User: "What metrics are available for Identity Verification?" Response: We support the following metrics for Identity Verification: idv-base, idv-lightning-group-1, idv-lightning-group-2, idv-lightning-group-3, idv-document, idv-selfie-check. - If metric_types aren't provided, use "auth-request" as the default - If no date range is provided, ask the user for one (suggest last 30 days with current date as end date) - The maximum look-back period is limited to 1 year from the current date |
| `PLAID_MCP_PLAID_LIST_TEAMS` | Plaid list teams | Retrieve teams associated with the user and present them as a selectable list. After the user selects a team, capture the team_id of the selected team for use in subsequent tool requests. 1. You MUST return a numbered list of teams with their names clearly displayed in a human readable format in the conversation dialog - Format each team as: "{number}. {company name} (ID: {team_id})" - Example: "1. XXX Corporation (ID: fakeid00000000000000000)" 2. Ask the user explicitly to select a team by providing either: - The number from the list (e.g., "Please select team 3") - The exact team name (e.g., "I want to use XXX Corporation") - The team ID directly (e.g., "Use team fakeid00000000000000000") 3. After user selection, confirm their choice with a clear acknowledgment: - "You've selected: {company name} (ID: {team_id})" 4. Store and use this team_id for ALL subsequent tool requests that require a team_id parameter 5. Handle edge cases appropriately: - If only one team exists, auto-select it and confirm the selection - If no teams exist, clearly communicate this limitation to the user - If the response is empty, the user is not a member of any teams. Inform the user that they should visit dashboard.plaid.com to join or create a team. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

Once connected, your Grok bot can access the Plaid MCP server through Composio to run the actions you authorize, using plain language in the chat.

## Complete Code

None listed.

## Conclusion

### Way Forward
Now that Plaid is connected, extend your setup by connecting the other apps you already use every day, so your Grok bot can run true cross-app workflows end to end.
- Connect Calendar to turn threads into scheduled meetings automatically.
- Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
- Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
- Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single connection, your bot can coordinate multiple tools safely and reliably in one conversation.

## How to build Plaid MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/plaid_mcp/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/plaid_mcp/framework/claude-cowork)
- [Hermes](https://composio.dev/toolkits/plaid_mcp/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/plaid_mcp/framework/atomic-agent)

## Related Toolkits

- [Firecrawl](https://composio.dev/toolkits/firecrawl) - Firecrawl automates large-scale web crawling and data extraction. It helps organizations efficiently gather, index, and analyze content from online sources.
- [Tavily](https://composio.dev/toolkits/tavily) - Tavily offers powerful search and data retrieval from documents, databases, and the web. It helps teams locate and filter information instantly, saving hours on research.
- [Exa](https://composio.dev/toolkits/exa) - Exa is a data extraction and search platform for gathering and analyzing information from websites, APIs, or databases. It helps teams quickly surface insights and automate data-driven workflows.
- [Serpapi](https://composio.dev/toolkits/serpapi) - SerpApi is a real-time API for structured search engine results. It lets you automate SERP data collection, parsing, and analysis for SEO and research.
- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [Peopledatalabs](https://composio.dev/toolkits/peopledatalabs) - Peopledatalabs delivers B2B data enrichment and identity resolution APIs. Supercharge your apps with accurate, up-to-date business and contact data.
- [Snowflake](https://composio.dev/toolkits/snowflake) - Snowflake is a cloud data warehouse built for elastic scaling, secure data sharing, and fast SQL analytics across major clouds.
- [Posthog](https://composio.dev/toolkits/posthog) - PostHog is an open-source analytics platform for tracking user interactions and product metrics. It helps teams refine features, analyze funnels, and reduce churn with actionable insights.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [AccuWeather](https://composio.dev/toolkits/accu_weather) - AccuWeather is a global weather service providing current conditions, forecasts, MinuteCast precipitation, alerts, and lightning data. Use it for fast, localized forecasts and real-time weather alerts.
- [Adafruit IO](https://composio.dev/toolkits/adafruit_io) - Adafruit IO is Adafruit's cloud platform for connected device and IoT project data. It helps you store, visualize, and act on sensor feeds without running your own backend.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ahrefs MCP](https://composio.dev/toolkits/ahrefs_mcp) - Ahrefs MCP is Ahrefs' hosted MCP server for SEO data and insights. Use it to access backlinks, organic metrics, keyword research, and competitor analysis.
- [Akta](https://composio.dev/toolkits/akta) - Akta is a company intelligence platform providing enrichment, news, and alternative business signals. It helps teams build targeted company lists and enrich data-driven workflows.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Amplitude](https://composio.dev/toolkits/amplitude) - Amplitude is a digital analytics platform for product and behavioral data insights. It helps teams analyze user journeys and make data-driven decisions quickly.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Plaid MCP?

With a standalone Plaid MCP server, the agents and LLMs can only access a fixed set of Plaid tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Plaid and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Grok Bot?

Yes, you can. Grok Bot fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Plaid tools.

### Can I manage the permissions and scopes for Plaid while using Tool Router?

Yes, absolutely. You can configure which Plaid scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Plaid data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)