Jedify Production
Query a governed semantic layer over your Snowflake, BigQuery or Databricks warehouse in plain language, and run read-only SQL against it. Anthropic lists 16 tools; Jedify documents 25 across three modes selected by a URL parameter. OAuth or API key, no application scopes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Jedify Production via MCP
https://be.jedify.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Jedify Production Tools & Capabilities (16)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The tool count depends on a URL parameter, not on the connector. Anthropic lists 16 Asker-mode tools; Jedify documents 25 across three modes, selected by
?mode=or a proxy flag. A tool census of the listed endpoint does not describe an installation that connected with a different string. - No application scopes exist. The RFC 9728 descriptor at
https://be.jedify.com/.well-known/oauth-protected-resource/mcpdeclaresscopes_supportedas an - Anthropic's directory records the auth posture wrongly. The entry sets
is_authless: trueandauth_posture: "no_auth". The listed endpoint returned HTTP 401 with aWWW-Authenticate: Bearerchallenge to an anonymous request on 2026-08-23. Jedify requires a login. - Three listed tools have no vendor documentation.
ask_an_agent,list_agentsandcreate_share_linkappear in Anthropic's listing and in none of Jedify's three tool references. We cannot describe whatask_an_agentreaches, and it is dispatcher-shaped by name. - We could not read tool schemas or safety annotations. The listed endpoint returned 401, so we never saw a
tools/listresponse and cannot reportreadOnlyHintordestructiveHintfor any tool. The read/write split above is our classification of names against Jedify's descriptions. /mcp/messageinitializes without authentication. A single anonymousinitializereturned HTTP 200 with the server's full instruction block on 2026-08-23, while the listed/mcppath returned 401. Only the handshake is open — we did not attempt any tool call, and tool access remains credentialed on Jedify's documented account.- No tool can observe cost. No tool in any of the 25 names carries a
credit,balance,usage,quotaorbillingverb. Warehouse query cost is real — Jedify's own Athena page notes per-TB-scanned billing — and nothing in the surface reports it. - Published apps flatten permissions. Jedify warns that a published dashboard uses one API key for every viewer, so all viewers see data at that key's level rather than their own.
- Row-level security needs SSO. Jedify's Snowflake session-variable route for per-user row filtering "requires SSO." Without it, an admin must map each user to a Snowflake role by hand.
- Jedify publishes no numeric rate limit. Its REST reference documents a 429 response but states no threshold, and documents no idempotency key on any question or function-creation call.
- Jedify disclaims output accuracy in writing. Its disclaimer states AI-generated outputs "may occasionally contain errors, omissions, or misinterpretations," that validating them is the user's responsibility, and that Jedify "does not guarantee the correctness, completeness, or suitability of any result."
- Whether a share link can be revoked is unresolved. We found no Jedify documentation on expiring or withdrawing a share link, and we did not create one.
Frequently asked questions
Sixteen in Anthropic's listing, but 25 in Jedify's documentation. Jedify's MCP server runs three modes — Asker, Editor and Builder — and its docs state the mode changes which tools your client sees. The directory lists Asker only. Editor adds six semantic-layer editing tools and Builder adds six function-management tools, and a URL parameter selects the mode.
Not in the default Asker mode, and only as a proposal in Editor mode. Jedify documents that Editor mode never changes your semantic layer directly — sl_commit_edits stages a changeset as review-pending sessions and a human approves before anything applies. Asker mode's only write is create_share_link. No mode writes to your warehouse.
Yes, read-only SELECT statements. The run_sql_query tool is in Anthropic's listing and Jedify's Asker reference describes it as a read-only SQL SELECT against the data source. The server's own instructions state that only SELECT is allowed, that INSERT, UPDATE, DELETE, DROP, ALTER and CREATE are barred, and that queries must be single-line.
None that narrow anything. Jedify's RFC 9728 resource descriptor declares scopes_supported as an empty array, and its authorization server advertises only email, profile and phone — all OpenID identity claims. Checked live on 2026-08-23. So the consent screen offers no way to grant asking a question without also granting read-only SQL.
Yes, despite Anthropic's directory recording it as authless. The directory entry sets is_authless to true and auth_posture to no_auth, but an anonymous request to the listed endpoint returned HTTP 401 with a Bearer challenge on 2026-08-23. Jedify documents browser sign-in for desktop clients and an API key for hosted agents.
Whatever your warehouse holds, filtered by your permissions. Jedify connects to Snowflake, BigQuery, Databricks, Redshift and AWS Athena, and its authentication page states access is scoped to the signed-in user's or key's permissions. For Snowflake, Jedify forwards the end-user identity so native row access policies filter rows per user.
Because it uses one API key for all viewers. Jedify warns that a published app uses one API key for everyone who opens it, so every viewer sees data at that key's permission level rather than their own. Jedify's guidance for sensitive data such as HR or finance is to pick a key whose access matches what all viewers should see.
Because you are in Asker mode, which is the default. Jedify's troubleshooting page states that Builder mode requires the --builder flag in the proxy args, and that an API key carries its own mode. When using a key, Jedify's documented fix is to set the server URL to https://be.jedify.com/mcp/message?mode=builder, which takes precedence over the key's mode.
Sources
- Jedify MCP overview (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify MCP modes, including the
?mode=parameter (retrieved 2026-08-23) · retrieved 2026-08-23 - Jedify Asker tools reference (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify Asker examples, source of the example prompts quoted above (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify Editor tools reference and changeset operations (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify Builder tools reference (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify semantic functions (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify MCP connect and authentication — · (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify MCP troubleshooting, source of the FAQ questions (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify Snowflake row-level security (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify AWS Athena connector, per-TB-scanned cost note (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify Deep Research Agent, share-link description (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify disclaimer on AI-generated outputs (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify role-based access control (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify REST API endpoints reference (retrieved 2026-08-23) · retrieved 2026-08-23
- Jedify documentation index,
llms.txtandllms-full.txt— · (retrieved 2026-08-23).docs.jedify.com/robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes, expressly permitting this synthesis. · retrieved 2026-08-23 - npm proxy package
@jedify/mcp-auth1.1.1 (retrieved 2026-08-23) · retrieved 2026-08-23 - Live auth posture check: anonymous POST to
https://be.jedify.com/mcpreturned 401 with a Bearer challenge; RFC 9728 metadata athttps://be.jedify.com/.well-known/oauth-protected-resource/mcp; authorization server metadata athttps://be.jedify.com/.well-known/oauth-authorization-server(2026-08-23) · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- Jedify support — <mailto:support@jedify.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Analytics
- Developer
- Jedify Production
- Tools
- 16
- Domain
- be.jedify.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.