What can you do with the AWS Glue integration?

LiveContext exposes 39 operations on AWS Glue, covering crawler, database, job and table. Common uses include automate crawler management, automate table management and automate trigger management.

LiveContext

All integrations

AWS Glue integration

AWS Glue serverless ETL service API. Manage data catalogs, crawlers, jobs, triggers, and workflows for data integration. Discover, prepare, and combine data for analytics, ML, and applications.

39 toolsCustom authAPI docs

Connect AWS Glue How integrations work

Common AWS Glue use cases

automate crawler management
automate table management
automate trigger management
automate database management
automate job management
automate job run management
automate partition management
get job programmatically
get table programmatically
get crawler programmatically

What you can do with AWS Glue

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.

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

Crawler, 7 operations

POSTcreate_crawler
Creates a new crawler with specified targets, role, configuration, and optional schedule.
POSTdelete_crawler
Removes a specified crawler from the Data Catalog, unless the crawler state is RUNNING.
POSTget_crawler
Retrieves metadata for a specified crawler.
POSTget_crawlers
Retrieves metadata for all crawlers defined in the customer account.
POSTstart_crawler
Starts a crawl using the specified crawler, regardless of what is scheduled. If the crawler is already running, returns a CrawlerRunningException.
POSTstop_crawler
If the specified crawler is running, stops the crawl.
POSTupdate_crawler
Updates a crawler. Stop the crawler first if it is currently running.

Database, 5 operations

POSTcreate_database
Creates a new database in the Data Catalog.
POSTdelete_database
Removes a specified database from a Data Catalog.
POSTget_database
Retrieves the definition of a specified database from the Data Catalog.
POSTget_databases
Retrieves all databases defined in a given Data Catalog.
POSTupdate_database
Updates an existing database definition in a Data Catalog.

Job, 5 operations

POSTcreate_job
Creates a new job definition.
POSTdelete_job
Deletes a specified job definition. If the job definition is not found, no exception is thrown.
POSTget_job
Retrieves an existing job definition.
POSTget_jobs
Retrieves all current job definitions.
POSTupdate_job
Updates an existing job definition. The previous definition is completely overwritten.

Table, 5 operations

POSTcreate_table
Creates a new table definition in the Data Catalog.
POSTdelete_table
Removes a table definition from the Data Catalog.
POSTget_table
Retrieves the Table definition in a Data Catalog for a specified table.
POSTget_tables
Retrieves the definitions of some or all of the tables in a given Database.
POSTupdate_table
Updates a metadata table in the Data Catalog.

Trigger, 5 operations

POSTcreate_trigger
Creates a new trigger.
POSTdelete_trigger
Deletes a specified trigger. If the trigger is not found, no exception is thrown.
POSTget_trigger
Retrieves the definition of a trigger.
POSTget_triggers
Gets all the triggers associated with a job.
POSTstart_trigger
Starts an existing trigger. See Triggers for information about how different types of trigger are started.

Job run, 4 operations

POSTget_job_run
Retrieves the metadata for a given job run.
POSTget_job_runs
Retrieves metadata for all runs of a given job definition.
POSTstart_job_run
Starts a job run using a job definition.
POSTstop_job_run
Stops a specified triggered crawl run; the specified JobRun must be in the RUNNING state.

Partition, 3 operations

POSTcreate_partition
Creates a new partition in the Data Catalog.
POSTdelete_partition
Deletes a specified partition from a specified table.
POSTget_partitions
Retrieves information about the partitions in a table.

Workflow, 2 operations

POSTcreate_workflow
Creates a new workflow.
POSTget_workflow
Retrieves resource metadata for a workflow.

Workflow run, 2 operations

POSTget_workflow_run
Retrieves the metadata for a given workflow run, including status, timestamps, and run statistics.
POSTstart_workflow_run
Starts a new run of the specified workflow.

Catalog import status, 1 operation

POSTget_catalog_import_status
Retrieves the status of a migration operation.

Use AWS Glue from Claude Code, Cursor or Codex

Connect AWS Glue in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its AWS Glue 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 AWS Glue

Create your workspace
Sign up free. Nothing to install.
Connect AWS Glue once
Add your AWS Glue 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.

AWS Glue integration FAQ

What can you do with the AWS Glue integration?: LiveContext exposes 39 operations on AWS Glue, covering crawler, database, job and table. Common uses include automate crawler management, automate table management and automate trigger management.