Ogen

com.ogenhqPublished by ogenhq.comOfficial publisherv1.0.1Updated Oct 24, 2026

Eight tools an agent uses; ten more for operating your tenant. Patent pending.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Ogen is a remote, OAuth-protected MCP server that gives an assistant eight agent tools plus ten tools for operating your tenant.

What you can do
Use eight tools as an agent working within Ogen, according to the provider's description. Use ten additional tools to operate your Ogen tenant. The description does not name the tools or say what data they act on, so check the provider's documentation before relying on specific capabilities.
When to use it
Consider it when you want an assistant to work inside an Ogen tenant, both as an agent using its tools and for tenant administration tasks. Because the tool list is not published here, confirm the actual capabilities first.
Requirements
A remote MCP endpoint at the provider's US host, reached over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared. The provider's site is the place to check for account and setup details.
Before you install
OAuth grants the server access tied to your account, so review the scopes requested at sign-in. Ten of the tools operate on your tenant, which may mean changing settings or data; confirm what each tool does before letting an assistant run it. The description gives no detail on what data is stored or sent to third parties.

Installation

In SourceWeft

  1. Open Ogen 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.ogenhq%2Fogen/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": {
    "ogen": {
      "type": "http",
      "url": "https://us.ogenhq.com/api/mcp"
    }
  }
}

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

2
  1. v1.0.1LatestSep 26, 2026
  2. v1.0.0Sep 24, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.