MCP Server - Artie

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 a bearer-token header — the server accepts OAuth only.

https://mcp.artie.com/mcp

Cursor
Claude Code
Codex

Add the server to .cursor/mcp.json:

{
  "mcpServers": {
    "artie": {
      "url": "https://mcp.artie.com/mcp"
    }
  }
}

Add the remote server:

claude mcp add-json artie '{"type":"http","url":"https://mcp.artie.com/mcp"}'

Add this server to ~/.codex/config.toml:

[mcp_servers.artie]
enabled = true
url = "https://mcp.artie.com/mcp"

On first tool use, Artie may ask you to sign in, link an environment, and approve the requested scopes. Your client controls the confirmation experience; keep confirmation enabled for actions that change or delete resources.

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 selected saved connector details and perform approved connector maintenance actions
Deploy or remove source readers
Manage existing SSH tunnels and PrivateLink connections
Manage column hashing salts, encryption keys, and ingestion API keys
Search the Artie data catalog

The server does not expose every Dashboard or API action. pipeline_list returns lightweight state; use the tool reference to identify the right follow-up action. Some connector and source-reader operations handle restricted credentials. Review the exact tool’s data-handling guidance before calling it. See the MCP tools reference for every exposed tool, its access requirements, and its retry and safety guidance.

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 only authentication path. Artie API keys are not accepted. 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.

​Connect your client

​What you can do

​Authentication and access

​Privacy and terms

Connect your client

What you can do

Authentication and access

Privacy and terms