← All implementations

Plaid · Supporting pattern

Internal MCP server

Plaid's internal Model Context Protocol server is supporting infrastructure rather than an agent. The central server connects engineers' AI tools to internal systems such as Jira, application logs, and data schemas that third-party MCP servers cannot reach.

1

Supporting infrastructure

This entry describes supporting infrastructure that other work builds on. The catalog classifies it as a supporting pattern. The record reports no execution workflow.

Approach type
Supporting pattern
Work
Coding
Human involvement
Unknown
Invocation
Interactive
Deployment stage
Scaled
Evidence strength
Detailed primary
Entry reviewed

Where people stay involved

The catalog records no execution workflow for this entry, so the scopes below describe access to the system rather than work it completes on its own.

  • engineer request → internal tool accessUnknown · Level unknown

Unclassified for engineer request → internal tool access; human attention boundary: unknown.

1

Observation date
2025

Implementation details

Harness

Central internal MCP server that fronts vendor AI clients

1

Tool access

More than 20 tools and several internal services (Jira, logs, schemas)

1

Credentials

Behind Plaid's identity-aware proxy and centralized authorization

1

Reported results and limitations

The catalog records what the sources report, with the scope and the denominator of every figure. A qualification below limits the figure it sits under.

Reported metrics

Headline claim

Dozens of agents rely on the internal MCP server; Claude Code and Cursor are used by over 80% of engineers

1

Reported by
Plaid
Scope
Claude Code and Cursor adoption among Plaid engineers; separate from internal MCP server adoption
Denominator
Plaid engineers for the AI-client usage share
Observation date
2025
Key observation

Claude Code and Cursor are used by over 80% of Plaid engineers; the source does not report internal MCP server adoption share

1

Reported by
Plaid
Scope
Claude Code and Cursor adoption among Plaid engineers; separate from internal MCP server adoption
Denominator
Plaid engineers for the AI-client usage share
Key observation

Thousands of tool calls and dozens of agents built on it

1

The source does not report the denominator of this figure.

Reported by
Plaid
Scope
Tool calls and agents relying on the internal MCP server across engineering, product, and support

Sources and research details

Citations link to the original publisher. Each source also keeps a preserved copy in the repository, so a changed or removed page stays checkable.

  1. The Plaid internal MCP serverhttps://engineering.plaid.com/the-plaid-internal-mcp-server-8eff08bb6bdbEngineering blog · First party · Last source verification: 2026-08-31
    Preserved copy ↗
Research details for every claim on this page
  1. Summary
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  2. Headline claim
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    Plaid reported the figures in its own engineering blog without independent verification.
    Reported by
    Plaid
    Scope
    Claude Code and Cursor adoption among Plaid engineers; separate from internal MCP server adoption
    Denominator
    Plaid engineers for the AI-client usage share
    Method
    Not reported
    Observation date
    2025
  3. Harness
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  4. Tool access
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  5. Credentials
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  6. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    Plaid reported the figures in its own engineering blog.
    Reported by
    Plaid
    Scope
    Claude Code and Cursor adoption among Plaid engineers; separate from internal MCP server adoption
    Denominator
    Plaid engineers for the AI-client usage share
    Method
    Not reported
    Observation date
    Not reported
  7. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    Plaid reported the figures in its own engineering blog.
    Reported by
    Plaid
    Scope
    Tool calls and agents relying on the internal MCP server across engineering, product, and support
    Denominator
    Not reported
    Method
    Not reported
    Observation date
    Not reported
  8. Operating model assessment
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    Unverified
    Confidence reason
    The MCP server is a tool-access layer, not a workflow with a single human-attention boundary.
    Observation date
    2025

The catalog records no related implementation for this entry yet.

Back to the directory →