Skip to main content
Jedify’s MCP works with desktop AI apps — Claude Desktop and Cursor — and with hosted AI agents and app builders (for example ChatGPT or no-code app builders). Pick the path that matches how you work.
  • Desktop apps (Claude Desktop, Cursor) run a small local proxy (@jedify/mcp-auth).
  • Hosted agents / app builders connect to the Jedify MCP server over the network.
Either way, the mode (Asker or Builder) and authentication work the same.

​
Desktop apps: Claude Desktop & Cursor

​
Prerequisites

  • An active Jedify account.
  • Node.js 18 or higher (the proxy runs with npx).
  • Claude Desktop or Cursor, installed and up to date.

​
Step 1: Add the Jedify configuration

Add this to your client’s MCP configuration: 
{
  "mcpServers": {
    "jedify": {
      "command": "npx",
      "args": ["-y", "@jedify/mcp-auth"]
    }
  }
}
This connects in Asker mode (the default). For Builder mode, add --builder to args — see Modes.

​
Step 2: Find your client’s config file

Open it from Settings → Developer → Edit Config, or edit directly:macOS — ~/Library/Application Support/Claude/claude_desktop_config.jsonWindows — %APPDATA%\Claude\claude_desktop_config.jsonIf the file doesn’t exist, create it with {} and add the configuration from Step 1.

​
Step 3: Restart, authenticate, verify

  1. Fully quit and reopen your client so it loads the configuration.
  2. The first time you use a Jedify tool you’ll sign in — see Authentication.
  3. Confirm it works by asking: “What data entities are available in our Jedify platform?”

​
Hosted agents & app builders

Hosted AI agents and app builders connect to the Jedify MCP server directly over the network — there’s no local proxy to install and no JSON config files to edit. The screens differ by platform, but to connect your agent you always provide two things: the server URL and your API key. (The app your agent later builds needs its own credentials to run — see Authentication.)
1

Open your platform's MCP settings

Find where your platform lets you add an MCP server or external tool — often labeled MCP servers, Tools, or Integrations.
2

Enter the Jedify MCP server URL

Paste your Jedify MCP server URL. To use Builder mode, add ?mode=builder to the end of the URL; leave it off for Asker:
Asker mode (default):
https://<your-jedify-mcp-url>

Builder mode — note ?mode=builder at the end:
https://<your-jedify-mcp-url>?mode=builder
(If your URL already contains a ?, join the parameter with & instead: …&mode=builder.) Your API key is at app.jedify.com/settings/api-keys; if you can’t find your MCP server URL, ask your Jedify contact.
3

Add your API key

Paste your API key into the platform’s credential field — usually labeled API key, token, or authorization.
4

Verify two things

In Builder mode? Ask “Which Jedify builder tools do you have?” — you should see tools like create_semantic_function and list_semantic_functions. If you only get question-answering tools, the ?mode=builder didn’t take effect.Reaching your data? Ask “Using Jedify, what data is available about our company?” — a real, account-specific answer confirms it’s connected to your account.

​
Next steps

Modes

Asker vs Builder, and how to switch.

Authentication

Browser-based login or an API key.

Asker examples

What to ask, and what your agent does.

Builder mode

Build dashboards by steering your agent.