Skip to main content
Glama
plaid-devx-mcp

plaid-devx-mcp

Related Servers

Alternatives to plaid-devx-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables connecting to the Plaid Sandbox API to retrieve bank accounts, transactions, and balances through MCP tools.
      305 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP servers for the Plaid API, providing tools to access Plaid financial data and documentation. Includes an authenticated API server for account, transaction, and investment operations, and an unauthenticated docs server for searching Plaid documentation.
      -
    • F
      license
      A
      quality
      B
      maintenance
      Enables AI agents to safely interact with GitHub, query Postgres read-only, check deployment status, and search/read files within an allowlisted sandbox—all with dry-run writes and SQL/path safety gates.
      8
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to read realistic, coherent data—repos, pull requests, issues, commits, users—through API-compatible, read-only replicas of 21 developer platforms including GitHub, Jira, Linear, Slack, Sentry and Salesforce, all preloaded with one simulated company so integrations can be built and tested with no accounts, credentials, rate-limit worry, or cleanup.
      10
      197 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Local, stateful twins of the Jobber, Housecall Pro, and QuickBooks Online APIs. Its MCP tools let a coding agent reset, rewind, advance time, inject faults, and load scenarios while it builds and tests integrations, with no real accounts.
      14
      99 npm
      2
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: core data endpoints (accounts, balance, transactions, auth, identity), item lifecycle (create, get, list, remove), sandbox testing controls (fire webhook, reset login), API spec exploration (search, describe, request example, stats), docs access, and a drift check. Even similar tools like accounts_get vs balance_get are clearly differentiated by purpose and description.

    Naming Consistency5/5

    All tools consistently use the 'plaid_' prefix followed by a noun phrase and an action verb (e.g., plaid_accounts_get, plaid_transactions_sync, plaid_sandbox_item_create). The naming pattern is uniform and predictable, making it easy to infer tool purpose from the name alone.

    Tool Count5/5

    With 20 tools, the server covers a broad set of Plaid development features without feeling bloated. Each tool has a clear role in the developer workflow—from item creation to sandbox controls, API exploration, and documentation—so the count is well-scoped and appropriate for the server's purpose.

    Completeness5/5

    The tool surface covers the full lifecycle: item creation (via sandbox or Link), data retrieval for accounts, balances, transactions, auth, and identity, item management (get, list, remove), sandbox testing (webhook firing, login reset), API spec introspection, docs access, and release-readiness drift checking. No obvious gaps are apparent for commonly used Plaid endpoints.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues