Connect an agent

Add the Enjab Mind MCP to your agent, exact steps for Claude Code, Claude apps, Cursor, VS Code, Codex, Gemini CLI, and more.

Enjab Mind is a remote Streamable-HTTP MCP server. Point any MCP client at it with your API key as a Bearer header and it gets the tools.

URL: https://mind.enjab.ae/api/mcp
Transport: HTTP (Streamable HTTP)
Auth header: Authorization: Bearer enjabmind_YOUR_KEY

First, mint a key

Sign in at mind.enjab.ae/dash/keys and create an API key (read-only is enough for most agents). Copy it once, then drop it into the steps below. See Authentication.

Every client below supports remote HTTP MCP and a custom auth header natively. The field names differ per client (url vs serverUrl vs httpUrl vs uri; http vs streamableHttp vs streamable_http), so use the exact snippet for your tool. Replace enjabmind_YOUR_KEY with your key throughout.

Command-line agents

One command (-s user makes it available in every project):

claude mcp add --transport http --scope user enjab-mind https://mind.enjab.ae/api/mcp \
  --header "Authorization: Bearer enjabmind_YOUR_KEY"

Or commit it to a project by creating .mcp.json at the repo root:

.mcp.json

{
  "mcpServers": {
    "enjab-mind": {
      "type": "http",
      "url": "https://mind.enjab.ae/api/mcp",
      "headers": { "Authorization": "Bearer enjabmind_YOUR_KEY" }
    }
  }
}

Reference: Claude Code MCP docs.

Keep the key in an env var and add it with the CLI:

export ENJAB_MIND_TOKEN="enjabmind_YOUR_KEY"
codex mcp add enjab-mind \
  --url https://mind.enjab.ae/api/mcp \
  --bearer-token-env-var ENJAB_MIND_TOKEN

Or edit ~/.codex/config.toml:

~/.codex/config.toml

[mcp_servers.enjab-mind]
url = "https://mind.enjab.ae/api/mcp"
bearer_token_env_var = "ENJAB_MIND_TOKEN"
# or hardcode: http_headers = { Authorization = "Bearer enjabmind_YOUR_KEY" }

Reference: Codex config reference.

gemini mcp add --scope user --transport http \
  --header "Authorization: Bearer enjabmind_YOUR_KEY" \
  enjab-mind https://mind.enjab.ae/api/mcp

Or edit ~/.gemini/settings.json (note the httpUrl field):

~/.gemini/settings.json

{
  "mcpServers": {
    "enjab-mind": {
      "httpUrl": "https://mind.enjab.ae/api/mcp",
      "headers": { "Authorization": "Bearer enjabmind_YOUR_KEY" }
    }
  }
}

Reference: Gemini CLI MCP docs.

Run goose configure → Add Extension → Remote Extension (Streamable HTTP), or edit ~/.config/goose/config.yaml:

~/.config/goose/config.yaml

extensions:
  enjab_mind:
    name: Enjab Mind
    type: streamable_http
    uri: https://mind.enjab.ae/api/mcp
    headers:
      Authorization: Bearer enjabmind_YOUR_KEY
    enabled: true

Reference: Goose extensions docs.

Claude apps

Enjab Mind uses an API key, not OAuth

Claude's Add custom connector dialog is built for OAuth. Its Advanced settings show OAuth Client ID / OAuth Client Secret, do not paste your Enjab Mind key there. Pasting a secret with no client ID produces the error "A client id must be provided with a client secret." Use one of the methods below instead.

Enjab Mind authenticates with a Bearer header, so connect it through the config file using the mcp-remote bridge (needs Node/npm). Edit:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "enjab-mind": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://mind.enjab.ae/api/mcp",
        "--header", "Authorization: Bearer enjabmind_YOUR_KEY"
      ]
    }
  }
}

Fully quit and reopen Claude Desktop after saving.

Newer (beta) Claude Desktop builds add a Request headers field in the connector dialog. If yours has it, you can instead: Settings → Connectors → Add custom connector, URL https://mind.enjab.ae/api/mcp, and under Request headers set Authorization = Bearer enjabmind_YOUR_KEY (leave the OAuth fields blank). If you don't see that field, use the config file above.

Reference: Custom connectors.

The web app can't run the mcp-remote bridge, and the connector dialog defaults to OAuth. Two cases:

If your account has the Request headers beta: Settings → Connectors → Add custom connector, URL https://mind.enjab.ae/api/mcp, and under Request headers set authorization = Bearer enjabmind_YOUR_KEY. Leave OAuth Client ID / Secret blank (allowlisted headers: authorization, x-api-key, x-auth-token).
If the dialog only shows OAuth Client ID / Secret: Enjab Mind (API-key auth) can't be added from Claude web yet. Connect from Claude Code, Claude Desktop (config above), or any editor instead.

Reference: Remote MCP connectors.

Editors & IDEs

Edit ~/.cursor/mcp.json (global) or <project>/.cursor/mcp.json:

~/.cursor/mcp.json

{
  "mcpServers": {
    "enjab-mind": {
      "url": "https://mind.enjab.ae/api/mcp",
      "headers": { "Authorization": "Bearer enjabmind_YOUR_KEY" }
    }
  }
}

Reference: Cursor MCP docs.

Command Palette → MCP: Add Server → HTTP, or create .vscode/mcp.json (note the servers key and type: "http"):

.vscode/mcp.json

{
  "servers": {
    "enjab-mind": {
      "type": "http",
      "url": "https://mind.enjab.ae/api/mcp",
      "headers": { "Authorization": "Bearer enjabmind_YOUR_KEY" }
    }
  }
}

Reference: VS Code MCP configuration.

Cascade panel → MCP icon, or edit ~/.codeium/windsurf/mcp_config.json (note serverUrl):

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "enjab-mind": {
      "serverUrl": "https://mind.enjab.ae/api/mcp",
      "headers": { "Authorization": "Bearer enjabmind_YOUR_KEY" }
    }
  }
}

Reference: Cascade MCP docs.

Cline panel → MCP Servers → Remote Servers, or edit cline_mcp_settings.json (note type: "streamableHttp"):

cline_mcp_settings.json

{
  "mcpServers": {
    "enjab-mind": {
      "type": "streamableHttp",
      "url": "https://mind.enjab.ae/api/mcp",
      "headers": { "Authorization": "Bearer enjabmind_YOUR_KEY" }
    }
  }
}

Reference: Cline MCP overview.

Settings → AI → MCP Servers → Add Remote Server, or edit ~/.config/zed/settings.json (note context_servers):

~/.config/zed/settings.json

{
  "context_servers": {
    "enjab-mind": {
      "url": "https://mind.enjab.ae/api/mcp",
      "headers": { "Authorization": "Bearer enjabmind_YOUR_KEY" }
    }
  }
}

Reference: Zed MCP docs.

Agent panel → … → MCP Servers → Manage → View raw config, or edit mcp_config.json (note serverUrl):

~/.gemini/config/mcp_config.json

{
  "mcpServers": {
    "enjab-mind": {
      "serverUrl": "https://mind.enjab.ae/api/mcp",
      "headers": { "Authorization": "Bearer enjabmind_YOUR_KEY" }
    }
  }
}

Reference: Antigravity MCP install guide.

For Junie, add to .junie/mcp/mcp.json (project) or ~/.junie/mcp/mcp.json (user):

.junie/mcp/mcp.json

{
  "mcpServers": {
    "enjab-mind": {
      "url": "https://mind.enjab.ae/api/mcp",
      "headers": { "Authorization": "Bearer enjabmind_YOUR_KEY" }
    }
  }
}

Reference: Junie MCP configuration.

Any other client (mcp-remote fallback)

If a client only speaks local stdio MCP, or can't send a custom header, bridge to Enjab Mind with the community mcp-remote proxy. Add this wherever that client takes a command-based server:

{
  "mcpServers": {
    "enjab-mind": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://mind.enjab.ae/api/mcp",
        "--header", "Authorization: Bearer enjabmind_YOUR_KEY"
      ]
    }
  }
}

Use it

Once connected, the agent has search, list_lists, and get_list (and the write tools on a read-write key). Tell it, in its system prompt, to search Enjab Mind when it needs a saved tool, link, or reference. See the full tool list.

Command-line agents

Claude apps

Editors & IDEs

Any other client (mcp-remote fallback)

Use it

On this page