OmegaAI

com.queryomegaPublished by queryomega.comOfficial publisherv2.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant query, browse and automate OmegaAI workspaces, connected over Streamable HTTP with OAuth 2.0 sign-in.

What you can do
Query OmegaAI workspace content from an MCP client. Browse workspace data and resources. Automate workspace actions through the assistant. Connect over Streamable HTTP with OAuth 2.0 authentication.
When to use it
Useful when you already work in OmegaAI workspaces and want an assistant to read, browse or automate that content without leaving the chat client. It fits teams that prefer a hosted endpoint over a locally installed package.
Requirements
A remote MCP client that supports Streamable HTTP. An OmegaAI account with OAuth 2.0 authorization; no API keys or environment variables are declared. Network access to the hosted endpoint.
Before you install
Access is granted through OAuth 2.0, so review which workspace permissions you authorize. The description mentions automating workspaces, which may change data; confirm the scope of any action before letting an assistant run it. Workspace content is sent to the hosted third-party service.

Installation

In SourceWeft

  1. Open OmegaAI in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.queryomega%2Fomega/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "omegaai": {
      "type": "http",
      "url": "https://mcp.cloud.queryomega.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.