SIDE BY SIDE, read 10 Nov 2026
Hex MCP server and Omni MCP Server, field by field: 18 and 26 tools named
| Field | Hex MCP server | Omni MCP Server |
|---|---|---|
| Data tool | Hex | Omni |
| Publisher | Hex | Omni Analytics |
| Kind | Official | Official |
| Repository or docs | learn.hex.tech/docs/api-integrations/mcp-server | docs.omni.co/ai/mcp |
| Version or commit | Hosted service (no versioned release) | Hosted service (no versioned release) |
| Last release | none found on 10 Nov 2026 | none found on 10 Nov 2026 |
| Transport | Remote (hosted) | Remote (hosted) |
| Auth | OAuth authorization to the user's Hex workspace (server URL app.hex.tech/mcp, or the customer's single-tenant, EU or HIPAA domain); requires Explorer role or higher. | OAuth 2.1 with PKCE (creates an MCP OAuth PAT for the user), or an API key (personal token or Organization API key; Organization keys can act as a user with X-MCP-User-ID). |
| Access | Read and write | Configurable |
| Tools listed | 18 named in the evidence | 26 named in the evidence |
| Tool definitions read at | learn.hex.tech/docs/api-integrations/mcp-server | docs.omni.co/ai/mcp/tools.md |
| Context weight | 252 tokens for 18 tool definitions (18 with a description), measured from the docs page read | 466 tokens for 27 tool definitions (27 with a description), measured from the docs page read |
| Status | Exists on 10 Nov 2026 as a Hex-hosted MCP server; tool list read from the Hex docs page (knowledge tools for Explorers, project editing tools for Editors). | Exists on 10 Nov 2026 as Omni's hosted MCP server (OAuth callback via callbacks.omniapp.co); admins toggle tool capabilities in AI Hub > MCP. The docs page lists 25 tools. |
| Read | 10 Nov 2026 | 10 Nov 2026 |
In one sentence each
- Hex MCP server: Hex's hosted server runs Threads (agent analyses over the user's data connections) and notebook editing under workspace roles and project permissions.
- Omni MCP Server: Omni's hosted server runs as a specific Omni user and exposes models, topics, saved queries and apps, so answers follow the semantic model and the user's permissions.
The read facts, topic by topic
| Topic | Hex MCP server | Omni MCP Server |
|---|---|---|
| Publisher and releases | Hex documents its own MCP server and an official Hex plugin in the Cursor Marketplace. No versioned release is published; the hosted URL is app.hex.tech/mcp. | Omni documents its own MCP server for querying Omni data and searching Omni docs from external AI tools. No versioned release is published for the hosted server; it is enabled by an organization setting (AI Hub > MCP, enabled by default). |
| Clients, auth and scoping | Threads created through the MCP server behave like Threads in the Hex app and select among the data connections the user can access. The MCP server enforces workspace roles and project permissions; editing a cell needs Can Edit or Full Access on that project, even for Admins. Knowledge tools need the Explorer role or above and project editing tools need Editor or above. | MCP tools run with the permissions of a specific Omni user, so results include only what that user can access. With OAuth, all MCP queries use the user's Omni permissions and access controls. An Organization API key can run tools as another user via the X-MCP-User-ID header, and X-MCP-Model-ID can pin a model. |
| Access and safety | The MCP server does not query Sensitive data connections by default and cannot read cell outputs from projects that use them, unless an admin allows it. MCP access is not governed by the workspace API access setting; deactivating the user is how to revoke all of a user's access. The tools include create, update and delete for cells, so the server is read-write for Editors. | The tool list includes app write tools (putApp, patchApp, publishDraft) so the server is not read-only; edits land on a shared draft until publishDraft runs. Organization Admins can individually enable or disable tool capabilities on the MCP settings page. A user-scoped key lists a tool only if the member holds the permission it needs. QueryUsageAnalytics uses read-only queries on usage data and is limited to Organization Admins. |
| What it reaches | The server works with Claude Desktop, Claude Code, Cursor, ChatGPT, Codex and Glean as well as standard MCP clients. Single-tenant, EU multi-tenant and HIPAA multi-tenant workspaces use their own host instead of app.hex.tech. | The same MCP server can serve embed users, scoped to each user's permissions. Setup pages exist for ChatGPT, Claude Code, Claude Desktop, Codex, Cursor, Microsoft Copilot and VS Code. |
| Lineage and impact | Project editing tools list cells and read cell outputs and chart images, giving agents the SQL, Python and Markdown cells of a notebook. Search_projects finds projects in the workspace, and get_project reads a project's metadata. None found: A lineage tool on the Hex MCP server page (cell-level reads exist, but no column or upstream-table lineage tool is listed). | PickModel returns the models available to the calling user and pickTopic returns the topics in the chosen model and selects the most relevant one. SearchContent finds existing dashboards and apps by name, folder or tile name, and listDocumentQueries lists the saved queries in a document. None found: A lineage tool among the Omni MCP tools (no column or upstream-table lineage tool documented). |
| Definitions, ownership and rules | Admins can mark data connections Sensitive and the docs point to descriptions and exclusions as the way to shape what the Hex Agent sees. | Queries run against Omni's modeled topics, and the Omni docs publish guidance on configuring AI context at model, topic and view level. ListSkills finds a saved Omni skill by name, identifier or description and reads its instructions without running it. |
| Freshness and upkeep | Run_cell and run_notebook execute cells or the draft notebook and get_run polls status, so results are produced at call time. None found: Scheduled metadata collection on the Hex MCP page. | None found: Scheduled or event-driven metadata collection in the Omni MCP docs; tools run queries and read content at call time. GetData and runQuery execute queries on request, and checkStatus and cancelJob manage running jobs. |
| Profile | The llms.txt notes workspace data is private and MCP access requires the user to authorize an OAuth connection. Claude connector widgets created by the Hex connector expire after 24 hours, and file uploads to a conversation are not supported. | The OAuth connection URL routes requests to the user's Omni organization through callbacks.omniapp.co/callback/mcp. |
Tool names, as published
Hex MCP server
search_projects create_thread get_thread continue_thread get_me create_project get_project list_cells get_cell create_cell update_cell delete_cell run_cell run_notebook get_run get_cell_output get_cell_image list_data_connections
Omni MCP Server
pickModel pickTopic getData runQuery listLlms askOmni checkStatus cancelJob listBranches listSkills submitFeedback searchContent listDocumentQueries runSavedQuery startDashboardDownload checkDashboardDownload fetchDashboardDownload getApp getAppDraft putApp patchApp publishDraft showApp import-claude-dashboard-from-url get-dashboard-import-job-status queryUsageAnalytics
Read next
Sources
- learn.hex.tech/docs/api-integrations/mcp-server, read 10 Nov 2026
- learn.hex.tech/llms.txt, read 10 Nov 2026
- docs.omni.co/ai/mcp/tools.md, read 10 Nov 2026
- docs.omni.co/ai/mcp/authentication.md, read 10 Nov 2026
- docs.omni.co/llms.txt, read 10 Nov 2026
- docs.omni.co/sitemap.xml, read 10 Nov 2026
Last reviewed 10 Nov 2026.