This article explains how to connect Claude Code CLI to Ezekia using the Model Context Protocol (MCP) for agent-based or automated workflows. Once connected, Claude Code can securely search, create, and update data in Ezekia using natural language.

Note: This setup is intended for developers and teams building AI agents or automation workflows. It requires use of the Claude Code CLI and an Ezekia API token. For a simpler, user-friendly setup using OAuth, please see the Claude (Connectors) MCP guide.


Important: Claude Code vs Ezekia’s Built-in AI

Ezekia supports separate AI integrations:

Ezekia Built-in AI / Sidekick

  • Uses the OpenAI API
  • Requires an OpenAI API key and credits
  • Configured inside Ezekia
  • Powers features such as Sidekick and summarisation

Claude Code via MCP

  • Uses Claude Code as an external AI tool
  • Does not use OpenAI API keys or credits
  • Uses an Ezekia API token for authentication
  • Is configured via the Claude Code CLI (not within Ezekia)

Connecting Claude Code via MCP is completely independent of enabling Sidekick or other AI features.


Who This Guide Is For

This setup is intended for:

  • Developers or technical users using Claude Code (CLI)
  • Users with access to Ezekia settings and API tokens
  • Users comfortable working with terminal/command line tools

Unlike ChatGPT, this setup is not designed for general end users and does not provide a UI-based connector experience.


Important: Claude Code Requirements

Claude Code MCP connections require access to the Claude Code CLI, which is not available on standard free Claude (claude.ai) accounts.

To use Claude Code with Ezekia MCP, you will need:

  • Access to Claude Code (CLI)
  • A Claude account with developer/API access enabled
  • Ability to run terminal commands (e.g. claude mcp add)

The standard Claude web app (claude.ai) does not support MCP connections or external tool integrations.

This means:

  • You cannot connect Ezekia MCP directly from the Claude web interface
  • MCP connections must be configured via the Claude Code CLI

For most non-technical users, ChatGPT MCP may be a more accessible option as it supports UI-based setup and OAuth authentication.


How Authentication Works

Claude Code connects to MCP servers using HTTP-based connections.

For Ezekia MCP:

  • Authentication is handled using your Ezekia API token
  • The token is passed securely as a request header
  • The token defines exactly what the AI can see and do in Ezekia

This differs from ChatGPT, which uses an OAuth login flow. In Claude Code, authentication is typically configured manually via the CLI.


Prerequisites

To connect Claude Code to Ezekia, you will need:

  • Claude Code installed and working (CLI access)
  • An Ezekia account with admin access to generate API tokens
  • Access to your system terminal (Mac, Linux, or Windows/WSL)


Step 1: Generate an API Token in Ezekia

  1. Go to Settings → API Tokens in Ezekia
  2. Click Generate new token
  3. Complete the fields:
    • Name: e.g. Ezekia MCP
    • Expiration: as required
    • Permission group: choose appropriate access (recommended: minimum required)
    • Client name: Ezekia MCP
  4. Click Generate token
  5. Copy and store the API key securely (it will only be shown once)

The permissions assigned here control exactly what Claude can access and do in Ezekia.


Step 2: Add the Ezekia MCP Server in Claude Code

Claude Code connects to MCP servers using CLI commands.

Add the Ezekia MCP Server

Run the following command in your terminal:

claude mcp add --transport http ezekia https://mcp.ezekia.com \
   --header "Authorization: Bearer YOUR_API_TOKEN"

  • Replace YOUR_API_TOKEN with your Ezekia API key
  • HTTP transport is the recommended method for remote MCP servers

Optional: Set Scope

You can control where the connection is available:

  • Default (local project only)
  • User-wide (all projects)
  • Shared (team via .mcp.json)

Example:

claude mcp add --transport http --scope user ezekia https://mcp.ezekia.com \
   --header "Authorization: Bearer YOUR_API_TOKEN"


Step 3: Verify the Connection

Run:

claude mcp list

You should see the Ezekia MCP server listed.

To check details:

claude mcp get ezekia

Inside Claude Code, you can also run:

/mcp

This shows server status and allows authentication if needed.


Using Ezekia in Claude Code

Once connected, you can interact with Ezekia using natural language.

Examples:

  • “Search for senior product managers in Berlin”
  • “Create a new assignment for this company”
  • “Add a follow-up task for next week”
  • “Update the project status to completed”
  • “Add a note summarising today’s call”

Claude translates your requests into secure actions performed directly in Ezekia.


Managing Your MCP Connection

You can manage your connection using:

claude mcp list
claude mcp get ezekia
 claude mcp remove ezekia


Security & Permissions

  • Access is controlled entirely by your API token
  • Actions respect your assigned permission group
  • No credentials are exposed beyond the configured token

We recommend:

  • One API token per user for auditability
  • Granting the minimum permissions required


Note on Support

Claude Code MCP connections are currently untested and not officially supported by Ezekia.

While the MCP endpoint may be compatible, we have not validated full functionality, authentication behaviour, or ongoing stability within Claude Code. If you choose to use Claude Code with Ezekia MCP, this should be considered an experimental setup.

We recommend using ChatGPT with the Ezekia MCP connector.


Getting Help

Ezekia Support can help with:

  • MCP availability and setup
  • API token generation and permissions
  • Verifying connectivity to Ezekia

We’re unable to provide support for:

  • Claude Code installation or CLI usage
  • Prompt design or automation workflows
  • General Claude configuration

For Ezekia-specific questions, contact support@ezekia.com.