Skip to content

Cloud Storage

Seafile MCP connector

The Seafile connector lets Claude, ChatGPT, Cursor, and any MCP client browse your Seafile libraries, find and file documents, and create share links, with each person's own Seafile access applied to every request.

Connect on Elaichi How to connect

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Seafile to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Seafile once

  1. Open Connections, choose Add connection, and pick Seafile.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Seafile API key. One person generates a token in Seafile and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

seafile
Seafile
Amazon Web Services
Cloudinary
DocuSign
Egnyte
Google Drive
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Seafile 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.

Seafile 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 today. The plugin directory lives at chatgpt.com/plugins.

Seafile 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.

Connect Seafile 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.

Connect Seafile on Elaichi See pricing

Use cases

What teams do with Seafile through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Operations

    Find the right file across every library

    Ask for the latest version of a vendor contract or a floor plan and the agent searches your Seafile libraries and folders, then tells you where it lives.

  • Sales

    Send a proposal with a share link

    After a call, ask the agent to create a Seafile share link for the proposal and hand it back ready to paste into the follow-up email.

  • Legal

    Set up a matter folder before kickoff

    Describe the new matter and the agent creates the folder structure in the right Seafile library and drops in the standard templates.

  • HR

    File onboarding documents in the right place

    Give the agent a new hire's name and it creates their folder, saves the signed offer and policy acknowledgments, and confirms what landed where.

  • Marketing

    Tag assets so the team can find them

    Ask the agent to update metadata on a batch of campaign images and build a view that groups them by campaign, channel, and status.

  • IT

    Review which files are shared outside

    Ask which download and upload links are open across your Seafile libraries and which library tokens are still active, then clean up the ones nobody needs.

Try asking

  • “List share links created in the Marketing library this week.”
  • “Which Seafile repos have upload links still active?”
  • “Summarize files added to the Engineering library yesterday.”

See all 30 Seafile tools below

Compare

Elaichi vs Zapier MCP vs Composio for Seafile

All three can connect Seafile 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 Seafile, 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 Seafile tools Allow or restrict single Seafile 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 Seafile 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 $15 per user per month. 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.

AI tools

Seafile tools for your AI agents

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

See it in Elaichi

What connecting Seafile gets you

6 screens from the product, each doing one job for your Seafile account.

The agent

Ask about Seafile libraries in plain language.

Questions about files, share links and repos answered from live Seafile records.

  • repos
  • files
  • share links
  • metadata records

Ask Elaichi to work across your apps.

List share links created in the Marketing library this week.

Which Seafile repos have upload links still active?

Summarize files added to the Engineering library yesterday.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Seafile.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

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

Tool catalog

30 Seafile tools ready on connect.

Repos, files, share links, upload links and metadata records, with no custom code.

  • Create a Seafile auth token
  • List all Seafile repo API tokens
  • Create a Seafile repo API token
  • Seafile repo API tokens bulk update
ElaichiTools
Tool Action Description
Create a Seafile auth token Create Create a Seafile account token by authenticating with your username and password. Returns: token, openapi, info, tags, servers, components, paths, x-readme, _id. Required: username, password. Two-factor authentication requires the X-SEAFILE-OTP header.
List all Seafile repo API tokens List List all repo API tokens for a Seafile library. Returns: repo_id, app_name, generated_by, permission, api_token. Required: repo_id.
Create a Seafile repo API token Create Generate a new repo API token for a Seafile library. Returns: repo_id, app_name, generated_by, permission, api_token, openapi, info, servers, x-readme, components, paths, _id. Required: repo_id, app_name.
Seafile repo API tokens bulk update Update Update a repo API token's permission in a Seafile library. Returns: repo_id, app_name, generated_by, permission, api_token, openapi, info, servers, x-readme, components, paths, _id. Required: repo_id, app_name, permission.
Seafile repo API tokens bulk delete Delete Delete a repo API token from a Seafile library. Returns: success, openapi, info, servers, x-readme, components, paths, _id. Required: repo_id, app_name.

Toolboxes

Every team gets its own Seafile toolbox.

Curate one toolbox per team and scope which Seafile tools it holds.

  • Engineering
  • Marketing
  • Legal
  • Finance
ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

Seafile · code libraries and build artefacts

 Seafile starter 18 Mar 4, 2026

Marketing toolbox

Seafile · brand assets and share links

 — 9 Mar 2, 2026

Legal toolbox

Seafile · contract files and access records

 — 24 Feb 27, 2026

Finance toolbox

Seafile · invoice folders and archives

 Seafile starter 6 Feb 19, 2026

Support toolbox

Seafile · customer upload links

 — 31 Jan 30, 2026

IT Operations toolbox

Seafile · repos and API tokens

 — 12 Jan 22, 2026

Shared connections

Share a Seafile account, never a credential.

See who connected each Seafile account and which teams and members use it.

  • Marketing
  • Engineering
  • Legal EMEA
  • Finance
ElaichiConnections
Connection Scope Status Access
SE

Seafile (Marketing)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
SE

Seafile (Engineering)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
SE

Seafile (Legal EMEA)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
SE

Seafile (Finance)

Connected by Tyler Reed

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

Seafile (Support)

Connected by Ryan Hayes

 Personal • Active Not shared
SE

Seafile (IT Operations)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Every Seafile call is answerable later.

When, who, what happened, type and resource for each file and share link.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

emily.carter@northwind.io

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

jake.morgan@northwind.io

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

megan.brooks@northwind.io

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

tyler.reed@northwind.io

 Seafile Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 Seafile Repos Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 Seafile Repos List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule drafts your Seafile digest.

Six steps fetch and group Seafile files, an agent drafts, a person approves.

Seafile digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch repos

    Seafile

    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 Michael Brennan

    Approve

  6. Post the digest

    Seafile

    Queued

Collections and dashboards

Seafile health counted, not asked for.

Four metrics, 14 days of files created and a team breakdown, refreshed on schedule.

Seafile health

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

Live

Repos

1,284 ↓ 12%

Files

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Repos created

Last 14 days

By team

Share of activity

Marketing 34%

Engineering 27%

Legal EMEA 21%

Finance 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Seafile to Claude?

Two steps. In Elaichi, choose Seafile and paste in an API key from your Seafile account, since Seafile connects with an API key and there is no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Seafile is available in Claude.

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

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

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

With Seafile connected, an agent can list your libraries and folders, search for files by name, and tell you where a document lives. It can create folders and files, update or remove files in bulk, create share links, and review open download and upload links. It can also read and update the metadata on files and build metadata views that group files the way your team thinks about them.

Does connecting Seafile give the AI access to every library?

No. Every request to Seafile runs as the person who signed in, so the agent sees only the libraries, folders, and files that person can already open in Seafile. Elaichi can narrow that further by hiding actions for a team or a person, but it can never widen access beyond what Seafile itself allows.

Can my team share one Seafile connection?

Yes. One person connects Seafile in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every action on Seafile in the audit log is tied to the person who took it.

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

Yes. Restrictions in Elaichi apply per action, so you can allow searching and creating share links in Seafile while blocking file deletion, folder deletion, or bulk updates. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

What happens to a Seafile connection when someone leaves?

When a person is offboarded in Elaichi, their access to Seafile through every client ends at once. A Seafile connection they shared with a team keeps working for everyone else. If you want to remove Seafile entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

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

Yes. Seafile 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, 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 Seafile?

Yes. Both let Claude, ChatGPT or Cursor use Seafile. 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 Seafile call.

How is Elaichi different from Composio for Seafile?

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 Seafile: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Seafile in front of your team

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

Connect Seafile Talk to us
Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.