MCP ConfigsMay 7, 2026·5 min read

Le Chat Connectors — Slack, Notion, Drive Tools for Claude

Le Chat ships pre-validated connectors for Slack, Notion, Drive, Linear, Figma. Wire them into Claude Code or Cursor as MCP servers via le-chat-mcp.

Agent ready

This asset can be read and installed directly by agents

TokRepo exposes a universal CLI command, install contract, metadata JSON, adapter-aware plan, and raw content links so agents can judge fit, risk, and next actions.

Stage only · 5/100Stage only
Agent surface
Any MCP/CLI agent
Kind
Mcp Config
Install
Stage only
Trust
Trust: New
Entrypoint
Asset
Universal CLI install command
npx tokrepo install 6df0de55-d600-4bf0-a6cd-72b551f551be
Intro

Mistral's Le Chat ships a connector ecosystem — pre-validated tool definitions for Slack, Notion, Google Drive, Linear, Figma, GitHub. Each connector is a typed contract: scopes, capabilities, error modes. The same connector schema can be exposed as an MCP server, letting Claude Code / Cursor / Codex CLI call Le Chat connectors directly. Best for: agents that need read+write access to enterprise SaaS without writing per-tool MCP code. Works with: Le Chat (native), Claude Code / Cursor / any MCP host (via le-chat-mcp). Setup time: 5 minutes (Mistral account + connector OAuth).


What's in the connector library

Connector Reads Writes
Slack channels, messages, users post message, react
Notion pages, databases create/update pages, query DB
Google Drive files, folders, content upload, comment
Linear issues, projects, cycles create/update issues
Figma files, frames, components comment, version
GitHub repos, PRs, issues comment, label

Use connectors inside Le Chat

# In Le Chat web UI, click Connectors → enable Slack/Notion/etc → OAuth in
# Then a normal prompt:
"Find every Linear issue tagged 'urgent' assigned to me, summarize, and post to #engineering on Slack"

Le Chat plans the calls, requests approval, and executes.

Use Le Chat connectors from Claude Code

Add to your MCP config:

{
  "mcpServers": {
    "lechat-connectors": {
      "command": "npx",
      "args": ["-y", "le-chat-mcp"],
      "env": {
        "LECHAT_API_KEY": "your-key",
        "LECHAT_CONNECTORS": "slack,notion,linear,gdrive"
      }
    }
  }
}

Now Claude Code can call:

  • lechat_slack_search
  • lechat_notion_query_database
  • lechat_linear_create_issue
  • lechat_gdrive_upload
  • ...all with Le Chat's pre-validated schemas.

Build a custom connector

# my-connector.yaml — register with Mistral via API
connector:
  id: my-internal-crm
  name: Acme CRM
  oauth:
    client_id: ${ACME_CLIENT_ID}
    authorize_url: https://acme.example.com/oauth/authorize
    scope: ["read:contacts", "write:notes"]
  capabilities:
    - id: search_contacts
      input_schema:
        type: object
        properties:
          query: { type: string }
      output_schema:
        type: object
        properties:
          contacts: { type: array, items: { ... } }

Once registered, the connector becomes available to your Le Chat workspace and any MCP host using le-chat-mcp.


FAQ

Q: Is Le Chat free? A: Yes — Le Chat has a generous free tier including connectors. Pro plan unlocks higher message quotas and frontier models. Pricing on mistral.ai/pricing.

Q: Why use Le Chat connectors instead of writing my own MCP servers? A: Le Chat connectors handle OAuth, scope validation, and error mapping in one place. Writing your own MCP for Slack means re-implementing rate limits, retries, and pagination. The trade-off: Le Chat connectors require a Mistral account and route calls through their cloud.

Q: Can I self-host the connectors? A: Custom connectors you build are owned by you and can route to any backend. The first-party Le Chat connectors (Slack, Notion, etc) are operated by Mistral. For full self-host, look at MCP-native servers like @modelcontextprotocol/server-slack.


Quick Use

  1. Sign in at chat.mistral.ai (free tier)
  2. Click Connectors, enable + OAuth Slack / Notion / Linear / Drive
  3. To use from Claude Code: install le-chat-mcp via the JSON config below

Intro

Mistral's Le Chat ships a connector ecosystem — pre-validated tool definitions for Slack, Notion, Google Drive, Linear, Figma, GitHub. Each connector is a typed contract: scopes, capabilities, error modes. The same connector schema can be exposed as an MCP server, letting Claude Code / Cursor / Codex CLI call Le Chat connectors directly. Best for: agents that need read+write access to enterprise SaaS without writing per-tool MCP code. Works with: Le Chat (native), Claude Code / Cursor / any MCP host (via le-chat-mcp). Setup time: 5 minutes (Mistral account + connector OAuth).


What's in the connector library

Connector Reads Writes
Slack channels, messages, users post message, react
Notion pages, databases create/update pages, query DB
Google Drive files, folders, content upload, comment
Linear issues, projects, cycles create/update issues
Figma files, frames, components comment, version
GitHub repos, PRs, issues comment, label

Use connectors inside Le Chat

# In Le Chat web UI, click Connectors → enable Slack/Notion/etc → OAuth in
# Then a normal prompt:
"Find every Linear issue tagged 'urgent' assigned to me, summarize, and post to #engineering on Slack"

Le Chat plans the calls, requests approval, and executes.

Use Le Chat connectors from Claude Code

Add to your MCP config:

{
  "mcpServers": {
    "lechat-connectors": {
      "command": "npx",
      "args": ["-y", "le-chat-mcp"],
      "env": {
        "LECHAT_API_KEY": "your-key",
        "LECHAT_CONNECTORS": "slack,notion,linear,gdrive"
      }
    }
  }
}

Now Claude Code can call:

  • lechat_slack_search
  • lechat_notion_query_database
  • lechat_linear_create_issue
  • lechat_gdrive_upload
  • ...all with Le Chat's pre-validated schemas.

Build a custom connector

# my-connector.yaml — register with Mistral via API
connector:
  id: my-internal-crm
  name: Acme CRM
  oauth:
    client_id: ${ACME_CLIENT_ID}
    authorize_url: https://acme.example.com/oauth/authorize
    scope: ["read:contacts", "write:notes"]
  capabilities:
    - id: search_contacts
      input_schema:
        type: object
        properties:
          query: { type: string }
      output_schema:
        type: object
        properties:
          contacts: { type: array, items: { ... } }

Once registered, the connector becomes available to your Le Chat workspace and any MCP host using le-chat-mcp.


FAQ

Q: Is Le Chat free? A: Yes — Le Chat has a generous free tier including connectors. Pro plan unlocks higher message quotas and frontier models. Pricing on mistral.ai/pricing.

Q: Why use Le Chat connectors instead of writing my own MCP servers? A: Le Chat connectors handle OAuth, scope validation, and error mapping in one place. Writing your own MCP for Slack means re-implementing rate limits, retries, and pagination. The trade-off: Le Chat connectors require a Mistral account and route calls through their cloud.

Q: Can I self-host the connectors? A: Custom connectors you build are owned by you and can route to any backend. The first-party Le Chat connectors (Slack, Notion, etc) are operated by Mistral. For full self-host, look at MCP-native servers like @modelcontextprotocol/server-slack.


Source & Thanks

Built by Mistral AI. Commercial product with free tier.

chat.mistral.ai — Le Chat home + connector gallery

🙏

Source & Thanks

Built by Mistral AI. Commercial product with free tier.

chat.mistral.ai — Le Chat home + connector gallery

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets