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 Artie API key generated from the Settings page in the Artie dashboard
An MCP-compatible client that supports remote Streamable HTTP servers

Connect your client

Use the remote server URL below and send your Artie API key in the Authorization header. Treat the key as a secret. Do not commit a configuration file that contains it.

https://mcp.artie.com/mcp

Cursor
Claude Code
Codex

Add the server to .cursor/mcp.json:

{
  "mcpServers": {
    "artie": {
      "url": "https://mcp.artie.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ARTIE_API_KEY"
      }
    }
  }
}

Add the remote server:

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

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

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

[mcp_servers.artie.http_headers]
Authorization = "Bearer YOUR_ARTIE_API_KEY"

Replace YOUR_ARTIE_API_KEY with the API key you generated from the Artie dashboard.

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. Artie may add or remove supported MCP operations over time.

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

The MCP endpoint requires an Artie API key. If your client cannot connect or reports an invalid token, verify that the key is current, then replace the saved key in your client configuration and reconnect. Generate a replacement key from the Artie dashboard if needed.

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