Connect an AI Assistant to Elglide

Elglide is a remote Model Context Protocol (MCP) server. Connect Claude, Claude Cowork, Claude Code or another MCP client and ask it about your connections, pipelines, task runs, audits and usage — or, if you allow it, have it make changes for you. It acts as you, with your current role, and can never do more than you can in the portal. MCP is an open standard, so other AI apps that support it may connect the same way; the ones named here are the ones we have tested.

Elglide in the AI you already use · 3:03

Server address

https://app.elglide.com/mcp

Elglide hosts the server; there is nothing to install.

Two ways to connect

Sign in: for AI apps you use yourself, like Claude, Claude Cowork and Claude Code. You paste the address and sign in with your Elglide account. There is no secret to copy.
Access token: for programmatic access, like scripts, scheduled jobs and automated agents, or any client that can't sign you in. You create the token in the portal and send it as a header. It is shown once, so keep it like a password.

Either way, the connection is read-only unless you allow changes, and it can never do more than your role. To switch it off, use Access Tokens (MCP) › Connected apps › Disconnect for an app you signed in from, or Revoke the token itself on the same page. Removing Elglide in the AI app itself does not end its access; use Disconnect or Revoke in Elglide as above.

Sign in: Claude and other apps

In the app, add a custom connector (or MCP server) and paste the address above.
The app sends you to Elglide. Sign in with your usual account.
Choose whether the app may also make changes. Leave it unticked for a read-only connection.
Click Allow. The app stays connected while you use it.

Claude Code

claude mcp add --transport http elglide https://app.elglide.com/mcp

Then run /mcp inside Claude Code and choose Authenticate to sign in.

Scripts and automation: access token

For scripts, jobs and clients that send a header, create a token under profile menu › Access Tokens (MCP) in the portal. The page shows ready-to-paste settings; the token is shown only once.

{
  "mcpServers": {
    "elglide": {
      "url": "https://app.elglide.com/mcp",
      "headers": { "Authorization": "Bearer elg_pat_…" }
    }
  }
}

What it can do

Area	Examples
Connections	List and inspect connections, test them, browse source tables and columns, REST endpoints and file sets
Pipelines & tasks	Create pipelines, run or cancel tasks, set schedules, row filters and schema evolution
Runs	Run history, progress and logs
Sync optimization	Watermarks; promote or demote a task's sync mode
Audits	Audit rules, results and history; run an audit now
Connectivity	SSH tunnels and hybrid agents, their status and logs
Account	Users and invitations, notifications, usage, credits, invoices, SOX reports

Permissions and safety

Read-only unless you allow changes. Every token and connected app is read-only unless you ticked “allow changes” when creating it.
Never more than your role. Changes also need a role that may make them, checked on every call. If your role changes or you are deactivated, the assistant's access follows within a minute.
Some things stay in the portal: granting the Admin role, adding or inviting Admins and Owners, signing off SOX periods, payments and certificates. Pointing a connection at a different server means re-entering its saved credentials.
Every change is logged with who made it.
Disconnect any time under Access Tokens in your profile menu. It takes effect within a minute.