Developer · Remote MCP server

OmegaAI

Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.queryomega/omega
Version
2.0.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-05-10
Updated
2026-05-10
Publisher
com.queryomega
Namespace
Namespace verified by the MCP Registry via the domain queryomega.com · how
Repository
github.com/The-Lambda-Group/query-omega-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.cloud.queryomega.com/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

How to connect OmegaAI

OmegaAI is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.cloud.queryomega.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
OilpriceAPI MCP-SERVERSource-timestamped energy data and reviewed OilPriceAPI product facts for MCP clients.Local · stdionpm: oilpriceapi-mcp
okffsMCP server connecting Claude Code to GitHub for an issue to branch to PR to close workflow.Local · stdionpm: @neturely/okffs
OleanderThe all-in-one data stack for agents. Upload files, run SQL, evolve tables, and render charts.Remote · HTTPLive check: sign-in requiredoleander.dev
Ollama HandoffOffload cheap work from your AI agent to a local Ollama model, at zero cloud cost.Local · stdioPyPI: ollama-handoff
OmenMulti-language code analysis for complexity, debt, hotspots, ownership, and defect prediction.Local · stdioOCI image (Docker): ghcr.io/panbanda/omen:3.0.0
OmnaraDeploy durable AI agents with Omnara, an open-source managed-agent platform.Remote · HTTPLive check: sign-in requiredapp.omnara.com
Omni Computer UseWindows MCP server replicating Anthropic's computer-use tool surface, for any MCP client.Local · stdioPyPI: omni-computer-use-mcp
Omni MCP ServerAll-in-one MCP server: GitHub, Git, Slack, web fetch, memory, and filesystem. Agent Mode opt-in.Local · stdionpm: @bitofacoder/omni-mcp-server