Skip to content

LangChain MCP connector

The LangChain connector links your LangChain sessions, session views, insights and insight configs to Claude, ChatGPT, Cursor, Microsoft Copilot and other MCP clients through one Elaichi endpoint, so each person works in LangChain as themselves with every action logged.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Summarize this week's LangChain sessions by status.

Working in LangChain with Elaichi

  • List all LangChain info healths
  • Get single LangChain session dashboard by ID
  • Get single LangChain session by ID
Ask anything…
Governance / Audit log Last 24 hours
LangChain Get single LangChain session by ID Emily Carter · Claude · 9:41 AM Done
LangChain Get single LangChain session dashboard by ID Emily Carter · Claude · 9:41 AM Done
LangChain List all LangChain info healths Emily Carter · Claude · 9:41 AM Done
LangChain Update a LangChain session by ID Megan Brooks · ChatGPT · 9:38 AM Done
LangChain Create a LangChain session Ryan Hayes · Cursor · 9:35 AM Done

How to connect LangChain to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

LangChain MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

LangChain MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

LangChain MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

LangChain MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

LangChain MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect LangChain to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with LangChain through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in LangChain is logged.

  • Engineering

    Check on a session before standup

    Ask for the dashboard of a LangChain session by name and get a plain summary of how it is doing, without opening another tab.

  • Engineering

    Set up a new session for a launch

    Create a LangChain session for a new feature, then rename or update it later as the project changes shape.

  • Product

    Turn a question into a saved view

    Describe what you want to see and have a LangChain session view created for it, then rename a batch of views in one go when naming conventions change.

  • Data science

    Read the insights on a session

    Pull the session insights LangChain has generated, ask what stands out, and create or adjust an insights config to change what gets tracked next.

  • Operations

    Tidy up old sessions in bulk

    List every LangChain session, spot the ones nobody has touched, and delete them together once the team agrees.

  • Support

    Confirm LangChain is healthy during an incident

    Check LangChain's health status and the metadata on the affected session so you can tell customers what is going on with confidence.

Try asking

  • “Summarize this week's LangChain sessions by status.”
  • “Which session views changed most in the last 14 days?”
  • “List sessions missing metadata from last week's runs.”

See all 382 LangChain tools →

What connecting LangChain gets you

6 screens from Elaichi, each doing one job for your LangChain account.

Elaichi Agent

Ask Elaichi to work across your apps.

Summarize this week's LangChain sessions by status.

Which session views changed most in the last 14 days?

List sessions missing metadata from last week's runs.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about your sessions, get real answers.

Ask plain-language questions and get answers pulled from live LangChain session records.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint, every client, no shared keys.

Connect Claude, ChatGPT, Cursor and Microsoft Copilot to one governed LangChain endpoint, no SDK required.

ElaichiTools
Tool Action Description
List all LangChain info healths List Get health information about the current LangSmith deployment. Returns the HealthInfoGetResponse object containing deployment health attributes.
Get single LangChain session dashboard by ID Get Get a prebuilt dashboard for a tracing project (session) in LangSmith. Returns: title, description, index, id, session_id, charts, sub_sections, layout, created_at, updated_at. Required: session_id.
Get single LangChain session by ID Get Get a specific tracer session (project) in LangSmith by id. Returns: start_time, end_time, extra, name, description, default_dataset_id, reference_dataset_id, trace_tier, id, run_count, latency_p50, latency_p99, first_token_p50, first_token_p99, total_tokens, prompt_tokens, completion_tokens, total_cost, prompt_cost, completion_cost, tenant_id, last_run_start_time, last_run_start_time_live,…. Required: id.
Update a LangChain session by ID Update Update a tracer session (project) in LangSmith by id. Returns: start_time, end_time, extra, name, description, default_dataset_id, reference_dataset_id, trace_tier, id, tenant_id, last_run_start_time_live. Required: id.
Delete a LangChain session by ID Delete Delete a tracer session (project) in LangSmith by id. Returns an empty 204 response on success. Required: id.

Tool catalog

382 LangChain tools, ready without custom code.

Browse every LangChain tool, resource and method without writing any custom code.

ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

LangChain · sessions and debugging traces

LangChain starter 18 Mar 4, 2026

Data Science toolbox

LangChain · session metadata and views

— 9 Mar 2, 2026

Product toolbox

LangChain · usage sessions and dashboards

— 24 Feb 27, 2026

Support toolbox

LangChain · session lookups for tickets

LangChain starter 6 Feb 19, 2026

Analytics toolbox

LangChain · session views and reporting

— 31 Jan 30, 2026

Platform toolbox

LangChain · session health and bulk operations

— 12 Jan 22, 2026

Toolboxes

Every team gets its own LangChain toolbox.

See toolboxes scoped to each team, from sessions to session views.

ElaichiConnections
Connection Scope Status Access
LA

LangChain (Engineering Prod)

Connected by Emily Carter

Personal • Active 1 team · 6 members
LA

LangChain (Data Science)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
LA

LangChain (Product Analytics)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
LA

LangChain (Support Ops)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
LA

LangChain (Platform Core)

Connected by Ryan Hayes

Personal • Active Not shared
LA

LangChain (Research)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share LangChain access without ever sharing credentials.

See who connected each LangChain account and how many teams and members use it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

LangChain Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

LangChain Sessions Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

LangChain Sessions List Toolbox

Audit log

Every LangChain action, logged and attributable.

Track when, who, what happened, type and resource for every LangChain call.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

LangChain digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch sessions

    LangChain

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    LangChain

    Queued

Automations

Schedules trigger real LangChain work end to end.

A schedule fires, fetches LangChain sessions, drafts a digest, and waits for approval before posting.

LangChain health

Refreshed 4 minutes ago · every 15 minutes · from the sessions collection

Live

Sessions

1,284 ↓ 12%

Session views

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Sessions created

Last 14 days

By team

Share of activity

Engineering Prod 34%

Data Science 27%

Product Analytics 21%

Support Ops 18%

Collections and dashboards

See LangChain health without asking anyone.

Four metrics and a 14 day chart track LangChain records, refreshed on schedule automatically.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for LangChain

All three can connect LangChain to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for LangChain, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over LangChain tools Allow or restrict single LangChain tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per LangChain call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

LangChain tools for your AI agents

382 tools are ready to call through Elaichi's MCP endpoint the moment you connect LangChain, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 240 of 382 LangChain tools here. Connect LangChain and call search_tools or tools/list over the MCP endpoint for the complete set.

Questions, answered

How do I connect LangChain to Claude?

Connect LangChain in Elaichi first, which asks for your LangChain API key and nothing else, so there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account when prompted and LangChain is ready to use in Claude.

Does LangChain work with ChatGPT and Cursor as well as Claude?

Yes. Once LangChain is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect LangChain once and every client picks it up.

What can an AI agent actually do with my LangChain data?

An agent can list your LangChain sessions, open a session's dashboard and describe how it is performing, create or rename sessions and session views, and read or create session insights and insight configs. It can also check LangChain's health and pull session metadata when something looks off. LangChain has a large set of actions, so short concrete asks like "show me the dashboard for the checkout session" work better than long paragraphs.

Does connecting LangChain give the AI access to every session in my workspace?

No. Access follows the LangChain API key of the person who connected it, so an agent only sees the LangChain sessions, views and insights that key already reaches. Elaichi can narrow that further with per-action restrictions, and it can never widen it beyond what LangChain itself allows.

Can my team share one LangChain connection?

Yes. One person connects LangChain in Elaichi and shares the connection with a team, and nobody else ever handles the LangChain API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every session change, not the connection.

Can I stop an agent from deleting or changing things in LangChain?

Yes. Restrictions in Elaichi work per action, so you can allow reading LangChain sessions and insights while restricting deleting sessions, bulk deleting or editing insight configs. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.

What happens to a LangChain connection when someone leaves?

Offboarding a person in Elaichi ends their access to LangChain at once, across every client they used. A shared LangChain connection keeps working for everyone else on the team. If you want LangChain gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

Does the LangChain MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. LangChain is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for LangChain?

Yes. Both let Claude, ChatGPT or Cursor use LangChain. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every LangChain call.

How is Elaichi different from Composio for LangChain?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to LangChain: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put LangChain in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot