Integration

Nile integration

Nile is serverless Postgres built for multi-tenant B2B apps. This control-plane API manages workspaces, databases, their dedicated compute instances and credentials, workspace developers and invites, and reads usage, billing, subscription and database health metrics (errors, query performance, uptime). Running SQL and the per-database Nile Auth API are not part of it; creating or rotating a database credential (the answer carries a password), creating or resizing dedicated compute, unauthenticated provisioning, claims, token exchange and billing-customer setup are not exposed. Authentication is a Nile API key, created in the Security tab of the Nile console, sent as a Bearer token.

Connect Nile How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Nile.Built from the 32 Nile tools below, on the connection you add once.

What you can do with Nile

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.

Database, 5 operations

create_databaseCreate databasePOSTCreates a database in the given region and starts provisioning it; poll get_database until status is READY. The name must be under 64 characters, unique in the workspace, letters, digits and underscores, starting with a letter or underscore.
delete_databaseDelete databaseDELETEMarks a database deleted and queues its data for deletion; it leaves the dashboard at once. It stays connectable while queued, and compute costs still apply until then.
get_databaseGet databaseGETReturns one database: id, name, status (READY once provisioned), region, creation and deletion dates, apiHost and dbHost (the Postgres connection host).
list_databasesList databasesGETLists the databases in a workspace with id, name, status (PENDING, REQUESTED, BUILT, POOLED, READY), region, creation date, apiHost and dbHost.
rename_databaseRename databasePUTRenames a database. The new name follows the creation rules: under 64 characters, unique in the workspace, letters, digits and underscores, starting with a letter or underscore.

Compute, 4 operations

delete_compute_instanceDelete compute instanceDELETERemoves a dedicated compute instance from a database and queues it for deletion; it leaves the dashboard at once. When deletion is finalized, all data on the instance is deleted.
get_compute_instanceGet compute instanceGETReturns one dedicated compute instance of a database, as a one-element list: instanceId, instanceName, status, region and instance type (size, memory, hourly cost).
list_compute_instancesList compute instancesGETLists the dedicated compute instances of a database: instanceId, instanceName, status, region, current and desired instance type (size, memory, hourly cost).
list_workspace_compute_metricsList workspace compute metricsGETReturns dedicated compute usage for a workspace over a time window: totalVCPUHours, usage per database and chart points.

Invite, 3 operations

create_developer_inviteCreate developer invitePOSTSends an invitation email to a developer with a link to join the workspace. A 202 answer means the invite is pending email delivery.
delete_developer_inviteDelete developer inviteDELETEDeletes a previously issued developer invite, so its link no longer works.
list_developer_invitesList developer invitesGETLists the developer invites of a workspace with invitee email, sender and verificationState (EMAIL_PENDING, EMAIL_SENT, VERIFIED or EXPIRED).

Workspace, 3 operations

create_workspaceCreate workspacePOSTCreates a workspace. Its slug, the identifier other tools take, is generated from the name, must be globally unique, and keeps only ASCII characters (spaces and non-ASCII become hyphens).
get_workspaceGet workspaceGETReturns one workspace: id, name, slug and creation date.
list_workspacesList workspacesGETLists the workspaces the authenticated developer may use, with id, name, slug and creation date. Pass slug as workspaceSlug to the other tools.

Credential, 2 operations

delete_credentialDelete credentialDELETEDeletes a database credential; anything connecting with it stops working. This cannot be undone.
list_credentialsList credentialsGETLists the credentials of a database (id, tenant, creation date) without their passwords, which Nile shows only once, at creation.

Developer, 2 operations

list_workspace_developersList workspace developersGETLists the developers with access to a workspace: id, email, kind (HUMAN or API) and their workspaces.
remove_developerRemove developerDELETERemoves a developer from a workspace; they lose access to it.

History, 2 operations

get_workspace_billing_historyGet workspace billing historyGETReturns a workspace's cumulative costs for one month, one point per UTC day boundary (plus now for the current month); totals equal the last point.
get_workspace_subscription_historyGet workspace subscription historyGETLists every subscription record of a workspace, most recent first: level, validFrom, validTo and subscriptionId.

Compute type, 1 operation

list_compute_typesList compute typesGETLists the dedicated compute types available in a workspace: id, computeSize, memory and hourlyCost.

Error, 1 operation

list_database_error_insightsList database error insightsGETReturns bucketed SQL and connection error counts for a database (by databaseId, not name), each point with timestamp, source and errorCount.

Me, 1 operation

identify_developerIdentify developerGETReturns the developer (or API key) behind the token: id, email, kind (HUMAN or API), the workspaces it may use (with their slug) and the database ids it may access. Start here to find a workspaceSlug.

Query performance, 1 operation

list_database_query_performance_insightsList database query performance insightsGETReturns query metrics for a database (by databaseId): proxy queries per second, observed queries per second, P99 latency in ms and CPU milliseconds per time bucket.

Readiness, 1 operation

get_workspace_billing_readinessGet workspace billing readinessGETChecks, without creating anything, whether a workspace's billing is set up: status is ready, missing_customer, missing_payment_method, lookup_failed or manual_review_required.

Region, 1 operation

list_regionsList regionsGETLists the region identifiers a workspace can create databases in, such as AWS_US_WEST_2 (us-west-2, Oregon). The answer is a plain list of strings.

Resend, 1 operation

resend_developer_inviteResend developer invitePOSTEmails an existing invitation again with the same code, without replacing or revoking it. If delivery fails the prior invitation is unchanged.

Subscription, 1 operation

get_workspace_current_subscriptionGet workspace current subscriptionGETReturns the current subscription record of a workspace: level, validFrom, validTo and subscriptionId.

Total, 1 operation

get_workspace_billing_totalsGet workspace billing totalsGETReturns a workspace's cost totals for one month by component, from rated usage lines, with the pricing applied (model, currency, rates, monthly allowances).

Uptime, 1 operation

list_database_uptime_insightsList database uptime insightsGETReturns time-weighted uptime of a database (by databaseId), derived from PostgreSQL ready probes: a summary percentage plus one point per time bucket.

Usage, 1 operation

get_workspace_usage_insightsGet workspace usage insightsGETReturns month-to-date CPU and provisioned compute usage (UTC) and current storage with daily snapshots, each metric with its own availability status. Covers non-sharded (Flavor 1) workspaces only.

Use Nile from Claude Code, Cursor or Codex

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

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