Connect

There are three ways to connect. All of them use the same modes and authentication:

The Jedify connector in Claude — nothing to install or configure.
A local client with a JSON config (Claude Desktop, Cursor, Claude Code) — for clients without a Jedify connector, or to authenticate with an API key instead of signing in.
A hosted agent or app builder — the server URL and an API key.

You never configure a mode. Whichever way you connect, the tools your agent gets are decided by your role in Jedify: Tenant Admins and Data experts get Asker, Editor, and Builder; Users get Asker. See Which modes you get.

If your organization’s Jedify is hosted in the EU, use be-eu.jedify.com wherever this page says be.jedify.com.

Claude connector

Jedify is a connector in Claude — nothing to install or configure. Connect it and sign in.

Open the Jedify connector

Go to claude.ai/directory/jedify, or open Settings → Connectors in Claude and search for Jedify.

Connect and sign in

Click Connect. Your organization’s Jedify login opens; sign in and return to Claude. Sessions refresh automatically — see Authentication.

The Jedify connector in the Claude connector directory, showing its tools and the Connected by default status

On Claude Team and Enterprise, a workspace admin enables the connector once for the whole organization — it then appears for every user, connected by default. Once connected, it is available wherever you use Claude: the web app, Claude Desktop, and Claude Code (run /mcp to see it).

Already running @jedify/mcp-auth? You can remove that entry from your client’s MCP configuration and use the connector instead — the connector serves the same tools your role allows.

Local clients (JSON config)

Use a local client configuration in a client that has no Jedify connector, or when you want to authenticate with an API key instead of signing in. It runs the @jedify/mcp-auth proxy in Claude Desktop, Cursor, or Claude Code (requires Node.js 18+):

{
  "mcpServers": {
    "jedify": {
      "command": "npx",
      "args": ["-y", "@jedify/mcp-auth"]
    }
  }
}

That single block is all you need. There is no mode setting: after you sign in, the server returns the tools your role allows — Editor and Builder tools appear automatically for Tenant Admins and Data experts.

Configured REMOTE_MCP_URL with ?mode=editor or ?mode=builder before? You can drop it — your role now decides. Keep it only to deliberately restrict that client to one mode, as below.

Restricting the proxy to one mode

The proxy talks to the URL in REMOTE_MCP_URL, and a ?mode= on it narrows the client to a single package — handy for an agent you want scoped to one job, or to keep a shared machine on Asker tools:

{
  "mcpServers": {
    "jedify-editor": {
      "command": "npx",
      "args": ["-y", "@jedify/mcp-auth"],
      "env": {
        "REMOTE_MCP_URL": "https://be.jedify.com/mcp/message?mode=editor"
      }
    }
  }
}

Use ?mode=asker, ?mode=editor, or ?mode=builder. Note the path: the proxy talks to /mcp/message, not /mcp. You can keep several such blocks side by side under different server names.

?mode= can only narrow what your role allows, never extend it — ?mode=editor on a User account still gets Asker tools. REMOTE_MCP_URL is also the one reliable way to set a mode for the proxy: its --editor / --builder flags and MCP_MODE variable are ignored whenever an API key is in use, and older cached proxy versions ignore them entirely.

Config file location

Claude Desktop
Cursor
Claude Code

Settings → Developer → Edit Config, or edit directly:

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

Command palette (Cmd/Ctrl+Shift+P) → MCP Settings → Open MCP Settings, or edit directly:

macOS / Linux — ~/.cursor/mcp.json
Windows — %APPDATA%\Cursor\mcp.json

Edit ~/.claude.json in your home directory and add the server under mcpServers (the same block shown above).

Restart your client. The first time you use a Jedify tool, you’ll sign in in the browser.

Authenticate with an API key

To skip the browser login — on a headless machine, a shared environment, or a CI setup — add JEDIFY_API_KEY to the env block. When it’s present, the proxy authenticates every request with the key instead of prompting you to sign in:

{
  "mcpServers": {
    "jedify": {
      "command": "npx",
      "args": ["-y", "@jedify/mcp-auth"],
      "env": {
        "JEDIFY_API_KEY": "your-api-key"
      }
    }
  }
}

Create the key in Jedify under Settings → API Keys. It is bound to you and carries your identity and permissions, so no email or sign-in is needed. If JEDIFY_API_KEY is unset, the proxy falls back to the browser login. Requires @jedify/mcp-auth v1.1.0 or later.

A key created in the app carries Asker mode on its own, regardless of your role. To use Editor or Builder tools with a key, add REMOTE_MCP_URL alongside it as shown in Restricting the proxy to one mode — the URL parameter takes precedence over the key’s own mode, so the same block works with or without a key.

To see what your agent got, ask it “Which Jedify tools do you have?” — Editor tools include make_edit and get_graph; Builder tools include create_semantic_function and list_semantic_functions.

Hosted agents and other MCP clients

For platforms that connect to an MCP server with a URL and a token — ChatGPT, no-code app builders, or any MCP client outside Claude — provide the server URL and an API key in the platform’s MCP settings:


Server URL	`https://be.jedify.com/mcp`. An API key runs in Asker mode, so add `?mode=editor` or `?mode=builder` if the agent needs those tools
API key	Create one in Jedify under Settings → API Keys — see Authentication

REST API

MCP

Data Connectors

Slack App

Looker Extension

Claude connector

Local clients (JSON config)

Restricting the proxy to one mode

Config file location

Authenticate with an API key

Hosted agents and other MCP clients

Next steps

Modes

Authentication

Asker examples

Builder mode

​Claude connector

​Local clients (JSON config)

​Restricting the proxy to one mode

​Config file location

​Authenticate with an API key

​Hosted agents and other MCP clients

​Next steps

Modes

Authentication

Asker examples

Builder mode

Claude connector

Local clients (JSON config)

Restricting the proxy to one mode

Config file location

Authenticate with an API key

Hosted agents and other MCP clients

Next steps