Omega API MCP
by DaiLui
README.md
# @dailui/omega-api-mcp
An [MCP](https://modelcontextprotocol.io) server that gives an AI agent one tool to reach the **Omega-API judge**.
> Give agents access to the judge without moving the judge into the agent.
The agent calls the tool with a turn; the judge — which stays on the server — returns a decision and a gate action.
Zero judge logic runs in the agent. Apache-2.0. Node 18+.
## The tool
**`omega_judge_turn`** — judge one agent turn: does the conversational process move? Returns a decision and a gate
action. It measures process shape, not whether the goal was reached.
Input:
| field | type | notes |
| -------------- | -------------------- | ------------------------------------------------- |
| `input` | string (optional) | the user / incoming message |
| `output` | string (optional) | the agent's drafted reply (at least one of these) |
| `session_id` | string (optional) | one id per conversation |
| `privacy_mode` | `FULL` \| `REDACTED` | optional |
Result:
```json
{
"turn_id": "t_…",
"decision": "PROCEED | CLARIFY | STOP",
"reason_family": "…",
"side": "…",
"gate": { "action": "release | clarify | suppress | none", "release_original": true }
}
```
Act on the gate **before** showing the reply: `release` → show · `clarify` → regenerate then call again ·
`suppress` → stop or escalate · `none` → observe only, show.
## Before you start: register → key → judge → meter
Register a project and get an API key (`oapi_live_…`) at <https://omega.dailui.com/signup.php>. Your first 100
judgments are free; after that, billing applies.
## Add it to your MCP host
Most hosts (Claude Desktop, IDE agents) launch MCP servers from a config file. Add:
```json
{
"mcpServers": {
"omega-api": {
"command": "npx",
"args": ["-y", "@dailui/omega-api-mcp"],
"env": { "OMEGA_API_KEY": "oapi_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }
}
}
}
```
The host starts the server over stdio and the `omega_judge_turn` tool becomes available to the agent.
## What it does not claim
It measures whether the process **moved**. It does not promise the agent achieved the user's goal — the two are
independent. It returns no scores or internal measures, only the decision and the gate.
## Links
- Learn more: <https://omega.dailui.com/integrations.php>
- Python client: `pip install omega-api` · JavaScript client: `npm install @dailui/omega-api`
- Examples & HTTP runner: <https://github.com/DaiLui/omega-api-examples>
## License
Apache-2.0.
TDQS
A4.4/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clearly specified and distinct by default.
Naming Consistency5/5
The single tool name 'omega_judge_turn' follows a clear verb-object pattern and is internally consistent. There is no other tool to conflict with.
Tool Count3/5
The server has only one tool, which feels thin for a general-purpose API server. While the tool is well-scoped, the count is borderline per the calibration guidelines.
Completeness5/5
Within the narrow domain of judging agent turns, the tool provides a complete lifecycle: it evaluates a turn and returns a decision with the necessary gate action. No obvious dead ends or missing operations are apparent.
Maintenance
ActivitySlowing
ResponsivenessNo issues