> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jedify.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Modes

> Jedify MCP runs in three modes — Asker, Editor, and Builder. Same connection, different tools.

Jedify's MCP server exposes three modes. The connection and authentication are identical — the mode only changes which tools your client sees, and [your role decides which modes you get](#which-modes-you-get).

* **Asker** — ask questions in plain language; get data back.
* **Editor** — have your agent make validated changes to your semantic layer, verify them, and publish only when you confirm.
* **Builder** — have your agent build data apps and dashboards using Jedify's semantic functions.

## Choose your mode

| | Asker mode | Editor mode | Builder mode |
| - | - | - | - |
| **Best for** | Ad-hoc questions and analysis | Evolving the semantic layer itself | Building dashboards and data apps |
| **How you use it** | You ask, in conversation | You describe a change; your agent drafts it, you verify it, you confirm publish | You describe; your agent builds |
| **Speed** | A few seconds — generated per question | Edits are validated instantly; publishing waits for your go-ahead | Instant — prebuilt, no AI at runtime |
| **Tools your agent gets** | Questioning and analysis | The above, plus editing, versioning, and test sets | The above, plus function management and SDK |

## Asker mode

Ask a question in plain language. Jedify interprets it against your semantic layer, runs the query, and returns the data. Best for ad-hoc exploration, investigations, and reporting.

> [card] [Asker tools](https://docs.jedify.com/mcp/asker/tools-reference.md)
>
> Every tool available in Asker mode.

> [card] [Examples](https://docs.jedify.com/mcp/asker/use-cases.md)
>
> Example prompts and what your agent does.

## Editor mode

Describe a change to your semantic layer — a new metric, a relationship, a dimension — and your agent turns it into a validated pending change. You can ask questions against the pending change, run a test set on it, and review what differs before you tell your agent to publish. Nothing goes live until you confirm — and on accounts without [Context Graph Versioning](https://docs.jedify.com/semantic-fusion/versioning/overview.md), a Data Expert also approves the edit in Jedify first.

> [card] [Editor tools](https://docs.jedify.com/mcp/editor/tools-reference.md)
>
> The tools your agent uses, and how an edit flows from draft to publish.

> [card] [Context Graph Versioning](https://docs.jedify.com/semantic-fusion/versioning/overview.md)
>
> Review, compare, and restore versions of your model in the app.

## Builder mode

Describe the dashboard or app you want; your agent builds it using **semantic functions**. No coding required — see [Semantic functions](https://docs.jedify.com/mcp/builder/semantic-functions.md) for how it works.

> [card] [Semantic functions](https://docs.jedify.com/mcp/builder/semantic-functions.md)
>
> What they are and how they're created.

> [card] [Builder tools](https://docs.jedify.com/mcp/builder/tools-reference.md)
>
> The six Builder-mode tools.

> [card] [SDK reference](https://docs.jedify.com/mcp/builder/sdk-reference.md)
>
> The `@jedify/sdk` TypeScript SDK.

> [card] [Examples](https://docs.jedify.com/mcp/builder/examples.md)
>
> Build a dashboard end to end.

## Which modes you get

Your **role in Jedify** decides which modes your agent sees. There is nothing to configure: the connection is the same for everyone, and the server returns the tools your role allows when you sign in.

| Your role in Jedify | Modes your agent gets |
| - | - |
| **Tenant Admin** | Asker + Editor + Builder |
| **Data expert** | Asker + Editor + Builder |
| **User** | Asker |

Roles are managed in Jedify under **Settings → Users**. If your agent is missing Editor or Builder tools, ask an administrator to check your role.

### Restricting to a single mode

You can narrow what an agent sees by adding `?mode=asker`, `?mode=editor`, or `?mode=builder` to the server URL — useful when you want an agent scoped to one job. It can only narrow your role's modes, never extend them: `?mode=editor` on a **User** account still returns Asker tools.

| | Where the mode goes |
| - | - |
| **Claude connector** | Not settable — you get your role's modes |
| **Local client** (`@jedify/mcp-auth`) | `REMOTE_MCP_URL` in the `env` block: `https://be.jedify.com/mcp/message?mode=editor` — see [Restricting the proxy to one mode](https://docs.jedify.com/mcp/connect.md#restricting-the-proxy-to-one-mode) |
| **Hosted agent or other MCP client** | The server URL: `https://be.jedify.com/mcp?mode=editor` |

An API key created in the app carries Asker mode on its own, so a hosted agent or a published app using that key sees Asker tools unless the URL selects another mode. See [Connect](https://docs.jedify.com/mcp/connect.md) for the setup in each client.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.