Integration

SeaTable System Admin integration

System administration of a SeaTable server (self-hosted, or any server where the token's account is a system admin). The token acts as a system admin of the whole server: this connection can manage every user and team on it, not only the admin's own account, and export any base. List and search users, teams, groups, departments and bases; update user and team profiles, roles and limits and block logins; create groups and departments and add department members; restore trashed bases, export or repair a base; audit share links, forms, automations, notification rules, logins, file access, emails and virus detections; read usage statistics and server info; send system notifications and change the logo, favicon and login background. Returns personal data (names, contact emails, IP addresses). Left out on purpose: every delete route, user and team creation and user import (they set passwords), password resets, two-factor settings, every admin-rights change (system admin role, team admin, department admin), base password removal, plugin installs, site security settings and the registration and invitation log (its entries are undocumented and may carry invitation links). Authentication is a system admin's Account-Token (never expires) sent as a Bearer header; the connection also asks for the server URL.

Connect SeaTable System Admin How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SeaTable System Admin.Built from the 71 SeaTable System Admin tools below, on the connection you add once.

What you can do with SeaTable System Admin

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

User, 6 operations

get_userGet userGETAgents: ask firstReturns one user's details (personal data): name, contact email, phone, team, role, active and admin flags, two-factor state and creation time.
list_non_department_usersList non department usersGETAgents: ask firstLists the active users who belong to no department (personal data). Team users are not included.
list_usersList usersGETAgents: ask firstLists every user of the SeaTable server (personal data: user id, name, contact email, last login, role, storage and row usage), page by page.
search_userSearch userGETAgents: ask firstSearches all users by a part of their name, user id or contact email (personal data in the answer: names, contact emails, team, quota, last login).
search_user_by_org_idSearch user by org idGETAgents: ask firstSearches the users of one team by a part of their name or email (personal data: name, contact email, avatar).
update_userUpdate userPUTAgents: ask firstChanges a user's profile and limits: name, contact email, role, quotas, row and automation limits; is_active false blocks the user from logging in. Leave a field out to keep it.

Base, 4 operations

export_baseExport baseGETAgents: ask firstExports a whole base as a .dtable file (with its assets unless ignore_asset is true) and returns the file. The file can be large.
list_all_basesList all basesGETAgents: ask firstLists every base of the server, page by page: id, UUID, name, owner, team, group, size, row count and dates.
list_user_basesList user basesGETAgents: ask firstLists the bases owned by a user: id, UUID, name, workspace, creator, modifier, dates and row count.
repair_baseRepair basePUTAgents: ask firstRuns SeaTable's repair script on a base: it looks for errors in the base's stored structure and fixes common problems. Changes the stored base.

Department, 3 operations

add_departmentAdd departmentPOSTAgents: ask firstCreates a department under a parent department (-1 creates the single top-level department of the system or team).
list_departmentsList departmentsGETAgents: ask firstLists the departments on one level of the tree: the top level without parent_id, or the sub-departments of parent_id.
update_departmentUpdate departmentPUTAgents: ask firstRenames a department; its group, if any, is renamed too.

Department member, 3 operations

add_department_membersAdd department membersPOSTAgents: ask firstAdds users to a department. Returns those added and those that failed with the reason.
add_user_to_departmentsAdd user to departmentsPOSTAgents: ask firstAdds one user to several system-level departments at once; departments the user is already in come back under failed.
list_department_membersList department membersGETAgents: ask firstLists the members of a department (personal data: name, contact email, avatar) and whether each is a department admin.

Group, 3 operations

create_groupCreate groupPOSTAgents: ask firstCreates a group with a name and an owner (a user id).
list_groupsList groupsGETAgents: ask firstLists every group of the server, page by page (id, name, owner, quota, size), optionally filtered by name.
transfer_groupTransfer groupPUTAgents: ask firstTransfers ownership of a group to another user, who then controls the group and its bases. Returns the group.

Team, 3 operations

get_teamGet teamGETAgents: ask firstReturns one team: name, creation time, URL prefix, role, creator (personal data), quotas, storage, row usage and member limit.
list_teamsList teamsGETAgents: ask firstLists the teams (organizations) of the server with creator, role, quotas, storage, row usage and member limit. role filters by team type.
update_teamUpdate teamPUTAgents: ask firstChanges a team's name, role and limits (rows, members, asset quota, automation runs). Leave a field out to keep it.

Abuse report, 2 operations

list_abuse_reportsList abuse reportsGETAgents: ask firstLists the abuse reports filed on shared bases: base, reporter, type, description, time and whether handled. Share link tokens are withheld.
update_abuse_reportUpdate abuse reportPUTAgents: ask firstMarks an abuse report as handled (true) or not handled (false). Returns the report.

Automation rule, 2 operations

list_automationsList automationsGETAgents: ask firstLists every automation rule of the server: base, how often it runs, its trigger, creator, last run, validity and run count. Rule actions are withheld.
list_invalid_automationsList invalid automationsGETAgents: ask firstLists the automation rules that became invalid (their base, table, row or column is gone): base, trigger, creator and last run. Rule actions are withheld.

Base share link, 2 operations

list_base_external_linksList base external linksGETAgents: ask firstLists the share links of one base and of its views: creator, permission, open count, expiry. Link addresses and tokens are withheld.
list_external_linksList external linksGETAgents: ask firstLists every base share link of the server, page by page: base, creator, permission, open count and creation time. Link addresses and tokens are withheld.

Dataset sync, 2 operations

list_common_dataset_syncsList common dataset syncsGETAgents: ask firstLists the common datasets synced periodically into other bases: dataset, source and destination bases, creator and creation time.
list_invalid_syncsList invalid syncsGETAgents: ask firstLists the common dataset syncs that became invalid (for example because the source or destination table was deleted).

Department group, 2 operations

create_department_groupCreate department groupPOSTAgents: ask firstCreates the group (with its own workspace) of a department so the department can own bases. A department has at most one group.
get_department_groupGet department groupGETAgents: ask firstReturns the group of a department (its id and name). Answers 404 when the department has no group.

Notification rule, 2 operations

list_invalid_notificationsList invalid notificationsGETAgents: ask firstLists the notification rules that became invalid: base, trigger, action, creator and last run.
list_notification_rulesList notification rulesGETAgents: ask firstLists every notification rule of the server: base, how often it runs, trigger, action (message and users to notify), creator and last run.

System notification, 2 operations

list_system_notificationsList system notificationsGETAgents: ask firstLists the system notifications sent to users (personal data: recipient name, contact email, team), with message and whether seen.
send_system_notificationSend system notificationPOSTAgents: ask firstSends a system notification to one user, shown in their SeaTable notifications.

Team user, 2 operations

list_team_usersList team usersGETAgents: ask firstLists a team's members (personal data: name, contact email, last login) with is_org_admin, quota and active state.
update_team_userUpdate team userPUTAgents: ask firstChanges a team member: active false blocks their login, true allows it again; also name, contact email and quota. Leave a field out to keep it. Team admin rights are not changed here.

Trashed base, 2 operations

list_trashed_basesList trashed basesGETAgents: ask firstLists the bases in the trash of every user and team, with when they were deleted and who owns them. Restore one with restore_trashed_base.
restore_trashed_baseRestore trashed basePUTAgents: ask firstRestores a base from the trash to where it was. Fails when a base with the same name already exists there.

Virus file, 2 operations

list_virus_filesList virus filesGETAgents: ask firstLists the files the virus scanner flagged: path, base, group or team, and whether each was deleted or ignored. Mark one with update_virus_file.
update_virus_fileUpdate virus filePUTAgents: ask firstMarks a flagged file as ignored (true, a false alarm kept) or not ignored (false). Returns the detection.

Active user, 1 operation

list_active_users_by_dayList active users by dayGETAgents: ask firstLists the users active on one day (personal data), page by page.

Active user statistics, 1 operation

get_active_user_statisticsGet active user statisticsGETAgents: ask firstReturns the number of active users per day between start and end.

Admin user, 1 operation

list_admin_usersList admin usersGETAgents: ask firstLists the system administrators of the server with their admin role, contact email, last login and usage (personal data).

Ai statistics, 1 operation

get_ai_statisticsGet ai statisticsGETAgents: ask firstReturns the AI usage cost of a month, grouped by owner or by team.

Audit log, 1 operation

list_audit_logsList audit logsGETAgents: ask firstLists the audit log of the server (personal data: who did what and when).

Automation statistics, 1 operation

get_automation_statisticsGet automation statisticsGETAgents: ask firstReturns how many times automation rules ran per team (or per user outside teams) in a month.

Base notification, 1 operation

list_base_notificationsList base notificationsGETAgents: ask firstLists a user's notifications inside one base (personal data: messages, rules, rows). Give the base UUID and the user's id or contact email.

Common dataset, 1 operation

list_common_datasetsList common datasetsGETAgents: ask firstLists the common datasets of the server: name, source base, creator and creation time.

Data collection form, 1 operation

list_data_collection_formsList data collection formsGETAgents: ask firstLists every data collection form of the server: table, base, owner and creation time. Form tokens are withheld.

Email log, 1 operation

list_email_logsList email logsGETAgents: ask firstLists the emails sent through third-party email accounts (personal data): time, sender name, mail server and success.

External app statistics, 1 operation

get_external_app_statisticsGet external app statisticsGETAgents: ask firstReturns the visits of external apps per team (or per user outside teams) in a month.

Favicon, 1 operation

update_faviconUpdate faviconPOSTAgents: ask firstReplaces the server's favicon with an uploaded image; with_notify true sets the variant shown when there are notifications. Returns its link.

File access log, 1 operation

list_file_access_logsList file access logsGETAgents: ask firstLists file accesses (personal data: user, contact email, IP address, device) with base, file and time.

Form, 1 operation

list_formsList formsGETAgents: ask firstLists every form of the server: name, base, owner, creation time and number of submissions. Form tokens are withheld.

Group member audit log, 1 operation

list_group_member_audit_logsList group member audit logsGETAgents: ask firstLists group membership changes (members added or removed) with the member, the group and who made the change (personal data).

Login background image, 1 operation

update_login_background_imageUpdate login background imagePOSTAgents: ask firstReplaces the background image of the server's login page. Returns its link.

Login log, 1 operation

list_login_logsList login logsGETAgents: ask firstLists the logins of all users (personal data: name, contact email, IP address), with time and success.

Logo, 1 operation

update_logoUpdate logoPOSTAgents: ask firstReplaces the logo every user of the server sees with an uploaded image (a .png with a transparent background is recommended). Returns its link.

Plugin, 1 operation

list_pluginsList pluginsGETAgents: ask firstLists the plugins installed on the server with name, version, display name, description, who added them and when.

Plugin install count, 1 operation

list_plugins_install_countList plugins install countGETAgents: ask firstLists how many times each plugin was installed into bases.

Script run statistics, 1 operation

get_script_run_statisticsGet script run statisticsGETAgents: ask firstReturns how many times and how long each user's scripts ran in a month, for one user or all.

Script task, 1 operation

list_script_tasksList script tasksGETAgents: ask firstLists the scheduled script tasks of the server: script, base, owner, schedule, last run and whether active.

Shared base, 1 operation

list_bases_shared_to_userList bases shared to userGETAgents: ask firstLists the bases other users shared with this user: base name, ids, owner, sharer and row count.

Storage object, 1 operation

list_user_storage_objectsList user storage objectsGETAgents: ask firstLists the files and folders a user stores, inside a parent folder: object id, name (a base UUID for a base folder), is_file, size and last update.

System info, 1 operation

get_system_infoGet system infoGETAgents: ask firstReturns server information: version, counts of users, active users, groups, teams and bases, license (edition, mode, expiry, user limit) and base server status.

Team base, 1 operation

list_team_basesList team basesGETAgents: ask firstLists the bases of a team (names and metadata only; the data inside stays private to the team).

Team group, 1 operation

list_team_groupsList team groupsGETAgents: ask firstLists the groups of a team with their creator and creation time.

Team name, 1 operation

get_team_namesGet team namesGETAgents: ask firstReturns the names of the teams whose ids you give.

View share link, 1 operation

list_view_external_linksList view external linksGETAgents: ask firstLists every view share link of the server: base, table, view, creator, permission, open count and expiry. Link addresses and tokens are withheld.

Use SeaTable System Admin from Claude Code, Cursor or Codex

Connect SeaTable System Admin in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SeaTable System Admin operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SeaTable System Admin

Create your workspace
Sign up free. Nothing to install.
Connect SeaTable System Admin once
Add your SeaTable System Admin connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.