Skip to main content
Glama

seafile_server

DestructiveIdempotent

Manage self-hosted Seafile accounts, devices, tokens, subscriptions, avatars, and server settings through the Seahub API, with confirmation-gated writes and dry-run previews.

Instructions

seafile_server covers the server toolset (46 route operations). Auth header Authorization Token. Self-hosted Seafile only. seafile.com hosts are refused. Writes, including side-effect GETs, need confirm true and SEAFILE_ALLOW_WRITES=true. Omit confirm for a dry-run preview of method, path, and redacted body. Delete, purge, expire, revert, trash clean, move, copy, and overwrite previews name the library id and path. Actions: account_info: GET /api2/account/info/. Read the account behind SEAFILE_TOKEN. The connector does not store a password. auth_ping: GET /api2/auth/ping/. Ping with the account token. Confirms the token is accepted. create_abuse_reports: POST /api/v2.1/abuse-reports/. POST /api/v2.1/abuse-reports/ (AbuseReportsView). Body and query are free-form. create_auth_token: POST /api2/auth-token/. Mint an account token. Credential-minting write. Output token is redacted. Prefer setting SEAFILE_TOKEN outside this connector. Warning: destructive, exposure, or credential change. delete_accounts: DELETE /api2/accounts/{email}/. DELETE /api2/accounts/{email}/ (Account). Path params: email. Body and query are free-form. Warning: destructive, exposure, or credential change. delete_auth_token_by_session: DELETE /api/v2.1/auth-token-by-session/. DELETE /api/v2.1/auth-token-by-session/ (AuthTokenBySession). Body and query are free-form. Warning: destructive, exposure, or credential change. delete_devices: DELETE /api2/devices/. DELETE /api2/devices/ (DevicesView). Body and query are free-form. Warning: destructive, exposure, or credential change. delete_two_factor_auth: DELETE /api2/two-factor-auth/{email}/. DELETE /api2/two-factor-auth/{email}/ (TwoFactorAuthView). Path params: email. Body and query are free-form. Warning: destructive, exposure, or credential change. delete_user: DELETE /api/v2.1/user/. DELETE /api/v2.1/user/ (User). Body and query are free-form. Warning: destructive, exposure, or credential change. get_accounts: GET /api2/accounts/{email}/. GET /api2/accounts/{email}/ (Account). Path params: email. Body and query are free-form. get_auth_token_by_session: GET /api/v2.1/auth-token-by-session/. GET /api/v2.1/auth-token-by-session/ (AuthTokenBySession). Body and query are free-form. Warning: destructive, exposure, or credential change. get_avatars_user_resized: GET /api2/avatars/user/{user}/resized/{size}/. GET /api2/avatars/user/{user}/resized/{size}/ (UserAvatarView). Path params: user, size. Body and query are free-form. get_client_sso_link: GET /api2/client-sso-link/. GET /api2/client-sso-link/ (ClientSSOLink). Body and query are free-form. Warning: destructive, exposure, or credential change. get_client_sso_link_token: GET /api2/client-sso-link/{token}/. GET /api2/client-sso-link/{token}/ (ClientSSOLink). Path params: token. Body and query are free-form. Warning: destructive, exposure, or credential change. get_query_io_status: GET /api/v2.1/query-io-status/. GET /api/v2.1/query-io-status/ (SeahubIOStatus). Body and query are free-form. get_subscription: GET /api/v2.1/subscription/. GET /api/v2.1/subscription/ (SubscriptionView). Body and query are free-form. get_user: GET /api/v2.1/user/. GET /api/v2.1/user/ (User). Body and query are free-form. get_user_avatar: GET /api/v2.1/user-avatar/. GET /api/v2.1/user-avatar/ (UserAvatarView). Body and query are free-form. get_webdav_secret: GET /api/v2.1/webdav-secret/. Read the WebDAV secret. Side-effect style credential read. The secret is redacted. Warning: destructive, exposure, or credential change. list_accounts: GET /api2/accounts/. GET /api2/accounts/ (Accounts). Body and query are free-form. list_devices: GET /api2/devices/. GET /api2/devices/ (DevicesView). Body and query are free-form. list_subscription_logs: GET /api/v2.1/subscription/logs/. GET /api/v2.1/subscription/logs/ (SubscriptionLogsView). Body and query are free-form. list_subscription_plans: GET /api/v2.1/subscription/plans/. GET /api/v2.1/subscription/plans/ (SubscriptionPlansView). Body and query are free-form. list_unseen_messages: GET /api2/unseen_messages/. GET /api2/unseen_messages/ (UnseenMessagesCountView). Body and query are free-form. ping: GET /api2/ping/. Ping the Seafile server. No library access. post_accounts: POST /api2/accounts/{email}/. POST /api2/accounts/{email}/ (Account). Path params: email. Body and query are free-form. post_auth_token_by_session: POST /api/v2.1/auth-token-by-session/. POST /api/v2.1/auth-token-by-session/ (AuthTokenBySession). Body and query are free-form. Warning: destructive, exposure, or credential change. post_avatars_user_resized: POST /api2/avatars/user/{user}/resized/{size}/. POST /api2/avatars/user/{user}/resized/{size}/ (UserAvatarView). Path params: user, size. Body and query are free-form. post_client_login: POST /api2/client-login/. POST /api2/client-login/ (ClientLoginTokenView). Body and query are free-form. post_client_sso_link: POST /api2/client-sso-link/. POST /api2/client-sso-link/ (ClientSSOLink). Body and query are free-form. Warning: destructive, exposure, or credential change. post_client_sso_link_token: POST /api2/client-sso-link/{token}/. POST /api2/client-sso-link/{token}/ (ClientSSOLink). Path params: token. Body and query are free-form. Warning: destructive, exposure, or credential change. post_device_wiped: POST /api2/device-wiped/. POST /api2/device-wiped/ (RemoteWipeReportView). Body and query are free-form. Warning: destructive, exposure, or credential change. post_logout_device: POST /api2/logout-device/. POST /api2/logout-device/ (LogoutDeviceView). Body and query are free-form. post_markdown_lint: POST /api/v2.1/markdown-lint/. POST /api/v2.1/markdown-lint/ (MarkdownLintView). Body and query are free-form. post_organization: POST /api2/organization/. POST /api2/organization/ (OrganizationView). Body and query are free-form. post_regdevice: POST /api2/regdevice/. POST /api2/regdevice/ (RegDevice). Body and query are free-form. post_user_avatar: POST /api/v2.1/user-avatar/. POST /api/v2.1/user-avatar/ (UserAvatarView). Body and query are free-form. post_user_convert_to_team: POST /api/v2.1/user/convert-to-team/. POST /api/v2.1/user/convert-to-team/ (UserConvertToTeamView). Body and query are free-form. post_user_list: POST /api/v2.1/user-list/. POST /api/v2.1/user-list/ (UserListView). Body and query are free-form. post_user_reset_password: POST /api/v2.1/user/reset-password/. POST /api/v2.1/user/reset-password/ (ResetPasswordView). Body and query are free-form. Warning: destructive, exposure, or credential change. server_info: GET /api2/server-info/. Read server version and feature flags. update_account_info: PUT /api2/account/info/. PUT /api2/account/info/ (AccountInfo). Body and query are free-form. update_accounts: PUT /api2/accounts/{email}/. PUT /api2/accounts/{email}/ (Account). Path params: email. Body and query are free-form. update_two_factor_auth: PUT /api2/two-factor-auth/{email}/. PUT /api2/two-factor-auth/{email}/ (TwoFactorAuthView). Path params: email. Body and query are free-form. update_user: PUT /api/v2.1/user/. PUT /api/v2.1/user/ (User). Body and query are free-form. update_webdav_secret: PUT /api/v2.1/webdav-secret/. Rotate the WebDAV secret. Credential-minting. The secret is redacted. Warning: destructive, exposure, or credential change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "seafile_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoFree-form JSON or form body. /api2 routes are sent as form fields. /api/v2.1 routes are sent as JSON. Secrets are redacted in previews.
queryNoQuery parameters, such as p for a library path or q for search.
actionYesSeafile operation to call.
paramsNoPath parameters, such as repo_id or group_id.
confirmNoSet to the boolean true to execute the write. Omit this field for a dry-run preview. false and the string true are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real value beyond them: the two-key write gate, the dry-run preview contents (method, path, redacted body), secret redaction, and per-action 'destructive, exposure, or credential change' flags that localize risk to specific operations such as create_auth_token and post_user_reset_password. It stops short of describing return payloads or rate limits, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded preamble is well organized, but the body is roughly forty near-identical entries like 'GET /api/v2.1/subscription/. GET /api/v2.1/subscription/ (SubscriptionView). Body and query are free-form.' — each repeating the route twice and adding a view name no agent can act on. Bulk without information density makes the genuinely useful lines (server_info, ping, get_webdav_secret) hard to find.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 47-operation dispatcher with no output schema, the definition covers the essentials an agent needs to call it safely: auth mechanism, self-hosted restriction, write gating, dry-run, and redaction. It is incomplete in that most actions get no statement of what they return, what the body must contain, or how listing endpoints paginate, leaving the agent to guess API semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents body, query, params, action, and confirm, and the description repeats rather than extends that (e.g. 'Path params: email', 'Body and query are free-form'). Some added meaning exists — knowing which path params each action needs (email, user, size, token) — but since the params object is free-form with no per-action mapping, the description should have carried more of that mapping and mostly restates routes instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening states a clear verb/resource framing: 'seafile_server covers the server toolset (46 route operations)' with self-hosted-only scope, and each action names a route and view. The agent can tell this is the server/account/auth administration surface rather than file or library work, though the description never explicitly contrasts it with seafile_files_and_dirs, seafile_libraries, or seafile_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives strong invocation constraints (Authorization Token header, self-hosted Seafile only, seafile.com refused, writes require confirm=true plus SEAFILE_ALLOW_WRITES=true, omit confirm for a dry-run preview). What it lacks is routing guidance: no sentence says when to pick this tool over the three siblings, so the agent must infer 'server admin work' from the operation list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.