Skip to main content
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.
  • 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

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.

Asker tools

Every tool available in Asker mode.

Examples

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 Model Versioning, a Data Expert also approves the edit in Jedify first.

Editor tools

The tools your agent uses, and how an edit flows from draft to publish.

Model Versioning

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 for how it works.

Semantic functions

What they are and how they’re created.

Builder tools

The six Builder-mode tools.

SDK reference

The @jedify/sdk TypeScript SDK.

Examples

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. 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. 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 for the setup in each client.