Tool reference

The Syntropic MCP server exposes 24 model-visible tools, grouped by purpose below. You don't call these directly — the agent picks them based on what you ask. Use this page to understand what's possible and to phrase requests that any MCP-capable agent can act on reliably.

Every tool is scoped to your Syntropic permissions: the agent cannot see workspaces, connections, or tables that your account isn't already entitled to.

Workspace discovery

Tool	What it does
list_workspaces	Lists every accessible Syntropic workspace with its organization and your effective workspace role.
list_workspace_members	Lists active and pending members of one workspace, including email and workspace role. The signed-in user must be authorized as a workspace administrator.
create_workspace	Creates a workspace in an organization you administer. If you belong to exactly one organization, the organization can be resolved automatically; otherwise provide its ID.
invite_workspace_users	Adds or invites a bounded batch of workspace users with per-user roles and ordered results (5 recipients by default, derived from the configured concurrency). Existing active members are left alone. Pending invitations are skipped by default and are resent only when you explicitly request it; an expired invitation is replaced with a fresh one.

Try: "Which Syntropic workspaces do I have access to?"

"Who are the active and pending members of Regional Operations, and what are their workspace roles?"

"Create a workspace called Regional Operations, then invite the listed users as viewers."

Connection discovery

Tool	What it does
list_connections	Lists the database connections (Snowflake, Databricks, MotherDuck, S3) configured in a workspace.
list_tables	Lists the Syntropic-managed tables for one connection or across all connections.
list_existing_database_tables	Lists tables in the upstream warehouse that haven't been imported into Syntropic yet.
get_existing_table_schema	Returns the schema of an un-imported warehouse table so Claude can preview it before connecting.
test_connection	Pings a connection to check reachability and surfaces any auth or network errors.
copy_connection	Securely copies an eligible Snowflake, Databricks, MotherDuck, or S3 connection into another workspace in the same organization. You can provide a new name; otherwise the source name is preserved. Syntropic creates fresh encrypted credentials and automatically tests the copy.

Try: "What Snowflake connections do I have and which tables are on each?"

"Copy the Shared Snowflake connection into the new workspace as Regional Operations Snowflake."

Workspace onboarding workflow

An agent can perform a general workspace onboarding flow without a customer-specific tool:

1. Call create_workspace and use the returned workspace ID.
2. Call invite_workspace_users. Keep the default on_pending="skip" unless you explicitly want outstanding invitations resent.
3. Call copy_connection with an eligible source connection and the new workspace ID. The copied connection remains available even if its automatic health check reports unhealthy or test_error.
4. To manage an existing warehouse table, call list_existing_database_tables and then connect_existing_table. To make a new table instead, call create_table or create_table_with_data.

The tools return structured IDs and per-item outcomes, so each result can be passed directly into the next call and partial invitation failures can be retried without repeating successful invitations.

With Organization Settings → Settings → Default connection access → All workspace connections enabled by an organization owner, steps 2 and 3 can run in either order: new members receive access to existing connections, and new or copied connections grant access to current workspace members, including pending invitees. The current default applies at each step. Changing it does not backfill existing permissions or restore revoked access. Under Grant access manually, an admin still assigns connection access in User Management.

Reading tables

Tool	What it does
read_table	Reads table rows with pagination, column selection, and row filters. Renders as the interactive table viewer with no duplicate Markdown on hosts that support MCP Apps; returns a Markdown preview and pagination/filter summaries elsewhere.
get_table_schema	Returns column definitions, data types, constraints, and quality rules.
get_table_history	Shows the audit log: who changed what and when.
get_change_diff	Returns the row-level diff for a specific entry in history (before/after values).

Try: "Show me the first 100 rows of pricing_overrides where region = 'EU'."

"Who last edited the tax_rates table, and what did they change?"

Webhooks

Tool	What it does
list_webhooks	Lists secret-free webhook metadata for one table, including each webhook's ID, method, active state, monitoring state, and queue mode. It does not expose URLs, headers, payloads, or parameters.
edit_webhook	Changes a webhook's name, description, active state, monitoring state, or queue mode. It cannot change or reveal the URL, method, headers, payload, or parameters.
copy_webhook	Copies an existing webhook to a table in the same organization. You must have effective workspace Admin access at both ends. Stored credentials remain server-side and are re-encrypted using the target table's connection key. Copies are inactive by default.

Try: "Copy the pipeline webhook from source_table in Operations to destination_table in Finance, and leave it inactive."

"Rename the webhook on pricing_overrides to Notify downstream, enable monitoring, and leave it inactive."

Writing tables

Tool	What it does
create_table	Creates a new empty table in the warehouse through Syntropic, with columns and quality rules you specify.
create_table_with_data	Same as create_table, but seeds the table with initial rows in one step.
update_rows	Inserts, updates, or deletes rows. Respects Syntropic's approval workflow — if the table requires approval, the change goes to pending instead of committing. (Note: some MCP clients like ChatGPT on Plus/Pro plans restrict write tools at the client level.)
update_table_schema	Adds, drops, or modifies columns on an existing table.
connect_existing_table	Imports a pre-existing warehouse table into Syntropic so it can be managed through the platform.
disconnect_table	Removes a table's Syntropic metadata (schema, change history, quality rules, saved views) without deleting the underlying warehouse data. Useful for re-importing a table to pick up upstream schema changes, or for undoing an accidental import.

Try: "Create a new table feature_flags in my Snowflake connection with columns name (text, unique, not null) and enabled (boolean, default false)."

"Delete the row in customer_blocklist where email = '[email protected]'."

"Disconnect legacy_orders from Syntropic, then reconnect it to pick up the new columns that were just added upstream."

Data quality

Tool	What it does
manage_quality_rules	Adds, replaces, or clears validation rules on a table's columns. Supported rule types: character length, numeric range, absolute date, and relative date — each with comparison operators like >=, <=, before, after.

Try: "Add a quality rule to the price column so values must be greater than 0."

"Require start_date to be after 2025-01-01."

Approvals

Syntropic supports approval workflows on writes. When a tool call touches a table that requires approval, the change isn't applied immediately — it goes to a pending queue that a reviewer must approve or reject from the Syntropic web app. The agent reports the pending status back in the conversation so you know the write hasn't landed yet.

You can ask the agent:

"Are there any pending approvals on my tables?"

...and it will surface them via get_table_history.

Scope and safety notes

• Permissions: All calls run as your Syntropic user. If you can't see something in the web app, the agent can't see it through MCP either.
• Webhook secrets: Create webhooks and change request configuration in the Syntropic web app. MCP can edit only secret-free settings. Copying transfers stored configuration entirely within the backend without revealing credentials.
• Prompt injection: If a table contains untrusted content (e.g., user-submitted text that tries to hijack the agent), treat agent output from that table as suggestions to review, not as instructions to auto-apply.