Skip to main content
Artie’s Model Context Protocol (MCP) server gives compatible AI clients access to approved Artie operations.
Before you begin, make sure you have an MCP-compatible client that supports remote Streamable HTTP servers and OAuth.

​
Connect your client

Use the remote server URL below. OAuth-capable clients discover Artie’s authorization server and prompt you to sign in. Do not add an Artie API key or bearer-token header for a new setup.
Add the server to .cursor/mcp.json:
On first tool use, Artie may ask you to sign in, link an environment, and approve the requested scopes.

​
What you can do

The server exposes a reviewed set of Artie operations. It can help you:
  • List, create, start, update, and remove pipelines; inspect schema changes; and manage backfill work
  • Inspect safe metadata for saved connectors and perform selected maintenance actions
  • Deploy or remove source readers that were configured through the Dashboard
  • Manage existing SSH tunnels and PrivateLink connections
  • Manage existing column hashing salts, encryption keys, and ingestion API keys
  • Search the Artie data catalog
The server does not expose every Dashboard or API action. In particular, it cannot create, read, or update connector or source-reader configurations because those operations can handle credentials. Configure those resources through the authenticated Dashboard setup flow, then use the approved MCP operations for supported maintenance and pipeline work.
Some tools change or delete resources. Clients can be configured to auto-approve tool calls, so do not enable automatic approval for destructive tools. Review the exact action and affected resource before authorizing a call. Deleting a resource or changing an encryption or ingestion API key can interrupt dependent workloads.

​
Authentication and access

OAuth is the supported authentication path. If a client cannot connect or has an expired token, remove its saved Artie connection and reconnect so it can complete OAuth again. OAuth prompts and recovery steps vary by client. For a headless or remote client, complete any browser approval and environment-linking flow from a browser session that can access the Artie Dashboard.

​
Privacy and terms

MCP requests are part of your use of Artie Services and are subject to Artie’s Privacy Policy and Terms of Service. For privacy questions, contact privacy@artie.com.