# Unified AI System [Health: Active]
**Category:** 💻 Developer Tools
**Repository:** https://github.com/happy520ai/unified-ai-system
**GitHub Stars:** 6
**Views:** 0
**Installs:** 0
**Upvotes:** 0
**Directory Page:** https://allmcps.com/mcp/unified-ai-system
## Description
Terminal-first AI gateway for Codex with eight governed MCP tools and local fake-provider startup.
## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):
```json
"mcpServers": {
"unified-ai-system": {
"command": "npx",
"args": ["-y","skills"]
}
}
```
## Documentation & README
# Unified AI System: Self-Hosted AI Gateway & MCP Server
Open-source AI gateway for deterministic prompt enhancement, governed execution, and reproducible verification.
English |
zh-CN |
Project Site
Unified AI System turns a rough request into a structured, reviewable prompt before execution. It gives teams one self-hosted surface for OpenAI-compatible SDKs, MCP, A2A, CLI, and HTTP while keeping provider calls explicit — with virtual keys and token budgets, exact response caching plus an opt-in lexical-approximate similarity layer, reverse MCP governance with REST→MCP generation, a terminal-first JSON operations overview, and operations-focused observability.
> **Current maturity:** hardened **Public Preview**. The credential-free path is
> reproducible and CI-gated; production deployment still requires your own
> provider staging, HA/DR drills, security review, and operating evidence.
## Try Before Installing
The original request stays visible. The local enhancer adds execution requirements, output requirements, and completion criteria.
[**Open a ready-to-run coding example in the browser Prompt Lab**](https://happy520ai.github.io/unified-ai-system/#enhance?prompt=Build+a+small+API+for+my+team&profile=coding&language=en)
The link loads a real request and renders the enhanced prompt locally. No
account, API key, or provider call is required.
Run the same proof against the published container:
```bash
docker run --rm ghcr.io/happy520ai/unified-ai-system/ai-gateway-service:0.7.0 pnpm gateway demo "Build a small API for my team" --enhance --profile coding --evidence
```
The evidence confirms that the original request was preserved, the result is
deterministic, and `providerCalled=false`. Codex, VS Code, Claude Code, Gemini
CLI, OpenCode, Cursor, Cline, Continue, and generic stdio clients can reach the
same gateway through twelve governed MCP tools. The source build also provides a
protocol-tested MCP Streamable HTTP endpoint for clients that connect by URL.
Useful in a real workflow? [Star the repository](https://github.com/happy520ai/unified-ai-system) or [share one reproducible result](https://github.com/happy520ai/unified-ai-system/issues/new?template=usage-verification-report.yml&title=%5BUsage%20Report%5D%20Quickstart).
## The Gateway at a Glance
Clients keep their native protocols; the gateway adds keys, budgets, cache, and audit. Twelve governed MCP tools are inspectable from any MCP client.
## Choose Your First Path
| Your goal | Start here | What you get |
| --- | --- | --- |
| Try it before installing | [Browser Prompt Lab](https://happy520ai.github.io/unified-ai-system/#enhance) | A local, deterministic preview with no account or API key. |
| Verify the published runtime | [60-second Docker demo](#try-it-in-60-seconds) | A disposable fake-provider run with visible evidence and cleanup. |
| Connect an agent client | [Codex and MCP quickstart](https://happy520ai.github.io/unified-ai-system/codex-mcp-docker-quickstart.html) | A pinned MCP container and twelve inspectable tools. |
| Choose a client path | [MCP compatibility matrix](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/mcp-client-compatibility.md) | Install commands, first checks, and honest evidence boundaries. |
| Integrate with an application | [Prompt enhancement guide](https://happy520ai.github.io/unified-ai-system/prompt-enhancement.html) | CLI, HTTP, SDK, curl, Python, and JavaScript paths. |
| Keep an existing OpenAI client | [OpenAI-compatible API](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/openai-compatible-api.md) | Point `baseURL` at `/v1` for Chat Completions, function tools, Responses, streaming, and model discovery. |
| Connect another agent | [A2A v1.0 gateway](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/a2a-protocol.md) | Verify an optionally signed Agent Card/JWKS and run tenant-scoped tasks with bounded memory, same-host SQLite, or cross-host PostgreSQL state plus fenced execution leases. |
| Check client runtime certification | [Client runtime certification](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/client-runtime-certification.md) | Current evidence-backed catalog state: 52 verified, 2,084 pending manual evidence, and 0 failed across 2,136 unique entries. |
| Run mainstream certification one-by-one | [Client runtime certification](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/client-runtime-certification.md) | Run `node tools/verify-client-runtimes-serial.mjs --client tag:mainstream` for sequential reports and explicit manual evidence states. |
| Run global protocol coverage | [Client runtime certification](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/client-runtime-certification.md) | Run `node tools/run-global-client-discovery.mjs --source-manifest docs/client-runtime-catalog-sources-worldwide.json --execute --serial --max 0`. |
| Run strict global certification | [Client runtime certification](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/client-runtime-certification.md) | Add `--require-manual-evidence --manual-evidence docs/client-runtime-evidence.example.json` to fail on missing manual proof. |
| Inspect the enhancement contract | [Credential-free evaluation](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/prompt-enhancement.md#prompt-enhancement-evaluation) | Eight representative cases for profiles, languages, signals, determinism, and zero provider calls. |
| Diagnose a first-run problem | [Troubleshooting matrix](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/first-run-troubleshooting.md) | Shell-specific checks without exposing credentials. |
| Verify an MCP client | [MCP client report](https://github.com/happy520ai/unified-ai-system/issues/new?template=mcp-client-report.yml) | Record one Codex, Cursor, Cline, or generic stdio run with a small evidence set. |
| Contribute or report a run | [Usage report](https://github.com/happy520ai/unified-ai-system/issues/new?template=usage-verification-report.yml) or [good first issue #106](https://github.com/happy520ai/unified-ai-system/issues/106) | A reproducible feedback path for users and maintainers. |
## Gateway Capabilities
Everything below runs from the same self-hosted process — opt-in and
fake-provider-first, so you can try every feature with zero credentials:
| Capability | What you get | Docs |
| --- | --- | --- |
| OpenAI + Anthropic + Gemini compatible APIs | `/v1/chat/completions` (SSE streaming, tools, image/audio input, n>1), `/v1/messages` with **native Anthropic streaming and prompt-caching passthrough**, **native Gemini inbound** `:generateContent/:streamGenerateContent/:batchGenerateContent`, the Responses API, and model discovery — keep your existing SDK, change only the base URL. | [OpenAI-compatible API](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/openai-compatible-api.md) · [Gemini](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/gemini-provider.md) |
| Virtual keys + budgets | Issue `uai-` keys with periodic token budgets (daily/monthly windows), per-key request limits, soft-budget alerts, spend attribution, and instant revocation. Consumers never hold provider keys. | [Virtual keys](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/virtual-keys.md) · [Spend reporting](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/spend-reporting.md) |
| Response cache — exact + lexical-approximate | Tenant-scoped hot-path caching with byte-identical JSON/SSE replay, plus an opt-in similarity layer for near-duplicate requests. The default layer is deterministic lexical approximation, not a semantic model; attach a real embedding endpoint via the HTTP embedding hook for semantic-grade matching. | [Response cache](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/response-cache-hot-path.md) |
| Operations overview API (terminal-first) | `GET /api/overview` returns a compact JSON snapshot (provider mode, health, readiness, request stats, circuit state) behind `dashboard:read` — a lightweight companion to `/metrics` for CLI and dashboard tooling. The gateway serves no browser page; the public-clone gate keeps it terminal-first. | [Observability](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/observability-export.md) |
| Guardrails — deterministic & local | Input/output scans: pasted secrets block, PII redacts, injection phrasings warn, banned terms and size limits enforce — no cloud tier, no extra credentials, <0.2 ms measured overhead, runtime-configurable per rule. | [Guardrails](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/guardrails.md) |
| Reverse MCP governance | Aggregate upstream MCP servers (Streamable HTTP and stdio) behind one authenticated, audited, allow-listed surface — plus **REST→MCP**: any OpenAPI 3 spec becomes governed MCP tools. | [Reverse MCP governance](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/reverse-mcp-governance.md) |
| Observability | Chat-specific Prometheus metrics on `/metrics` — tokens per model, cache hit rates, TTFT histograms, virtual-key rejections, guardrail findings — plus an opt-in Langfuse export and a per-key spend report API/CLI. | [Observability](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/observability-export.md) |
| Vector retrieval | A credential-free deterministic embedding provider and the SQLite vector store activate `mode: "vector"` RAG with strict tenant isolation. | [Providers & knowledge](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/providers.md) |
| Provider governance | A three-gate whitelist matrix for real providers, a runtime credential store (locally permissioned file; virtual keys and user tokens are stored SHA-256-hashed, provider runtime credentials in cleartext for local execution — see the honest-boundaries note), request cost guards, circuit breakers, and fallback chains. | [Provider enablement](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/real-provider-enablement.md) |
| Local-client intelligence gateway | Tenant-scoped inventory; server-bound per-client PoP with optional durable single-host replay protection; policy-pinned fake-provider dispatch for OpenAI, Anthropic, Gemini, and native chat; dry-run autonomous management; governed execution with durable dispatch/receipt reconciliation, a receipt-feedback outbox, and exactly-once aggregate learning; irreversible revocation; and transactional MCP onboarding for Claude-compatible, Cursor, and VS Code JSON profiles. Credential-free fixture flows are proven; real-client atomic-receipt certification, real-provider certification, distributed state, external rollback anchors, and a deployed protected Windows authority remain release gates. | [Design and evidence boundary](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/local-client-intelligence-gateway.md) |
| Enterprise governance + security drills | JWT auth, RBAC, tenant isolation with audit hash chains — verified by a repeatable 23-attack live security regression. | [Security drill](https://github.com/happy520ai/unified-ai-system/blob/HEAD/tools/security-attack-regression.mjs) |
| Enterprise identity & provisioning | **OIDC SSO** (authorization code + PKCE + JWKS signature verification, issues an API token on login) and **SCIM 2.0** user provisioning (bearer-auth create/get/list/patch/deactivate). | [Security drill](https://github.com/happy520ai/unified-ai-system/blob/HEAD/tools/security-attack-regression.mjs) · [Enterprise SSO & SCIM](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/enterprise-sso.md) |
| Operator traffic control | Configurable **weighted routing splits** and **shadow traffic** (`AI_GATEWAY_WEIGHTED_ROUTES_JSON`): shadow calls are separately accounted; real-provider shadowing also requires `AI_GATEWAY_SHADOW_REAL_PROVIDER_ENABLED=true`. | [Multi-process deployment](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/multi-process-deployment.md) |
| Hot-path RAG + billing evidence | Opt-in `unified_ai.rag` knowledge injection on `/v1/chat/completions`; central usage evidence and an admin-only exact-attempt USD statement comparison. Local statement previews remain explicitly non-legal and no payment gateway is connected. | [Spend reporting](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/spend-reporting.md) |
| Multi-instance controls | `AI_GATEWAY_MULTI_INSTANCE=true` keeps same-host SQLite defaults. Explicit PostgreSQL modes cover cross-host quotas, response idempotency, dispatch tombstones, WebSocket/A2A/Workforce leases and terminal fences, approvals, billable usage, and a shared HMAC audit chain. Current source also gates governed irreversible built-ins, webhooks, MCP/OpenAPI mutations, and custom tools with durable effect tombstones. A destructive CI drill restores PostgreSQL 17, builds a real asynchronous streaming standby, proves WAL replay, then uses a bounded three-failure-plus-confirmation controller to promote the one known standby and switch a stable endpoint. Before destruction, a real Docker-bridge partition separates the probe/standby from a still-writable primary; an independent fence must block promotion, then bridge healing must restore health and replay the partition marker. After failover, the fenced old-primary volume is `pg_rewind -R` synchronized and first starts only as a standby; it must keep streaming after the promoted primary restarts. A separate manifested physical base backup and continuous WAL archive are also restored archive-only to an exact LSN where an included marker exists and a later marker does not. The same eight clients recover after switch/restart. This is bounded LSN-PITR, single-bridge fencing, old-primary safe rejoin, single-standby automatic-failover, and at-most-once admission evidence, not provider-side exactly-once, multi-candidate election/quorum, external HA control, long-duration/off-host archive custody, time-based PITR, arbitrary multi-host partition/rejoin control, complete split-brain safety, or production RTO/RPO; resumable call-stack recovery, complete HA/DR, external WORM, and authenticated provider statements remain deployment work. | [Multi-process deployment](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/multi-process-deployment.md) · [PostgreSQL recovery drill](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/postgresql-recovery-drill.md) · [External-effect fencing](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/external-effect-fencing.md) |
Published infrastructure benchmark (fake provider, single node): chat JSON p50 **15.6 ms**, SSE TTFT p50 **2.8 ms**, **402 req/s** at concurrency 8, cache hits **5.6× faster** than misses — see the [gateway benchmark](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/benchmarks/2026-08-gateway-benchmark.md).
## Why People Use It
- Prompt enhancement for teammates who do not write perfect prompts.
- Clean-clone verification without credentials or hidden setup.
- Provider-free HTTP examples for curl and Python's standard library.
- OpenAI SDK, CLI, HTTP API, shared SDK, MCP, Codex, Cursor, Cline, and Continue entry points.
- Clear boundaries: no AGI claim, no L5 claim, no silent provider behavior.
- Protocol-first onboarding: the governed JSON transaction path currently supports
Claude-compatible, Cursor, and VS Code profiles. Other MCP, A2A, or HTTP clients
require an explicit adapter/principal binding and reproducible certification report.
## Try It in 60 Seconds
Verify the project without signing in:
```bash
docker run --rm ghcr.io/happy520ai/unified-ai-system/ai-gateway-service:0.7.0 pnpm gateway demo
```
Expected behavior:
- local fake-provider execution
- visible `execution: fake`
- deterministic output
- no API key or account needed
- container exits automatically
One-command natural-language enhancement preview:
```bash
docker run --rm ghcr.io/happy520ai/unified-ai-system/ai-gateway-service:0.7.0 \
pnpm gateway demo "Build a small API for my team" --enhance --profile coding --evidence
```
This starts an isolated fake-provider gateway, enhances the request locally,
prints the structured prompt, and cleans up without an API key.
You can also pipe a request directly into the published image without cloning
the repository:
```bash
printf '%s' "Plan a launch for a small API" \
| docker run --rm -i ghcr.io/happy520ai/unified-ai-system/ai-gateway-service:0.7.0 \
pnpm --silent gateway demo --enhance --profile planning --language en --json
```
PowerShell equivalent for a request file:
```powershell
Get-Content .\request.txt -Raw |
docker run --rm -i ghcr.io/happy520ai/unified-ai-system/ai-gateway-service:0.7.0 `
pnpm --silent gateway demo --enhance --profile planning --language en --json
```
The container still uses the disposable fake-provider path and exits after the
result is printed.
Use `--language zh-CN` or `--language en` when the enhancement output should
follow an explicit language instead of automatic detection.
Prompt enhancement example:
Start the gateway first (from a source checkout):
```bash
pnpm gateway serve
```
Then, in another terminal:
```bash
pnpm gateway enhance "Build a small API for my team" --profile coding
pnpm gateway chat "Build a small API for my team" --enhance --profile coding
```
The CLI also accepts a request from stdin, which is useful for shell pipelines
and text files:
```bash
printf '%s' "Plan a launch for a small API" \
| pnpm gateway enhance --profile planning --language en
cat request.txt | pnpm gateway enhance --profile auto --json
```
PowerShell users can pipe the same path with `Get-Content .\request.txt -Raw`.
### Existing OpenAI SDKs
Start the source gateway with `pnpm gateway serve`, then keep your existing
OpenAI client and change only its base URL:
```js
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "http://127.0.0.1:3100/v1",
apiKey: process.env.PME_AUTH_TOKEN || "local-development",
});
const result = await client.chat.completions.create({
model: "local-fake-model",
messages: [{ role: "user", content: "Build a small API for my team" }],
});
console.log(result.choices[0].message.content);
```
The credential-free gate verifies this path with the official OpenAI
JavaScript SDK `7.4.0`. With the source gateway running, reproduce it with:
```bash
node docs/examples/openai-sdk-chat.mjs
```
The focused compatibility layer supports text completions, streaming, model
listing, and optional local prompt enhancement. See the
[OpenAI-compatible API guide](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/openai-compatible-api.md) for Python,
supported fields, auth behavior, and explicit limitations.
Prefer Node.js? The dependency-free example verifies the provider-free response
before printing the enhanced JSON:
```bash
node docs/examples/prompt-enhancement.mjs "Help me plan a small API for my team" --profile planning --language en
```
Prefer Go? The standard-library example checks provider-free readiness and
prints JSON evidence before showing the enhanced prompt:
```bash
go run docs/examples/prompt-enhancement.go "Help me plan a small API for my team" --profile planning --language en
```
For a no-clone prompt-enhancement walkthrough, start the published gateway
image and follow the [provider-free curl example](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/examples/prompt-enhancement-curl.md):
```bash
read -rsp "Enter a random gateway token (32+ characters): " PME_AUTH_TOKEN
printf '\n'
export PME_AUTH_TOKEN
docker run --rm --publish 127.0.0.1:3100:3100 \
--env AI_GATEWAY_SERVICE_HOST=0.0.0.0 \
--env AI_GATEWAY_PROVIDER_MODE=fake \
--env AI_GATEWAY_REAL_PROVIDER_ENABLED=false \
--env PME_ENTERPRISE_AUTH_ENABLED=true \
--env PME_AUTH_TOKEN \
ghcr.io/happy520ai/unified-ai-system/ai-gateway-service:0.7.0
```
Keep that process running while you send the curl request. The response
includes `metadata.providerCalled=false`. For a credential-free HTTP stream,
use the [curl SSE example](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/examples/streaming-chat-curl.md) to inspect
`start`, `chunk`, and `done` events with `executionMode=fake`.
The gateway refuses non-loopback listening when authentication is disabled;
see the [critical attack-chain hardening report](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/security-hardening-attack-chain.md).
## Use It
### Terminal Workflow
After `pnpm install`:
```bash
pnpm gateway serve
pnpm gateway status
pnpm gateway doctor
pnpm gateway chat "Hello from Unified AI System"
```
The protected local-client control plane has read-only inspection plus explicit
governed lifecycle commands. Prefer supplying the admin virtual key through the
environment so it is not written to shell history:
```powershell
$env:AGENT_CONSOLE_ADMIN_KEY = ""
pnpm gateway clients --json
pnpm gateway clients discover --json
pnpm gateway clients --help
```
Discovery and smart-management default to dry-run. Mutations require explicit
confirmation and an admin key; uncertain writes are never retried. A registry
inspection is not proof that a named application was configured or controlled. See
[Local Client Intelligence Gateway](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/local-client-intelligence-gateway.md)
for the adapter and evidence boundary.
### MCP / Codex / Cursor / Cline
Published MCP command:
```bash
codex mcp add unified-ai-system -- docker run --rm -i ghcr.io/happy520ai/unified-ai-system/mcp-server:0.7.0
```
Restart Codex, run `/mcp verbose` to verify the twelve tools, then follow the
[60-second Codex MCP quickstart](https://happy520ai.github.io/unified-ai-system/codex-mcp-docker-quickstart.html) for a safe first
prompt-enhancement call and removal command.
For MCP clients that connect by URL, the source build provides a loopback-only
Streamable HTTP endpoint:
```bash
pnpm mcp:http
# http://127.0.0.1:3210/mcp
```
See the [MCP server guide](https://github.com/happy520ai/unified-ai-system/blob/HEAD/packages/mcp-server/README.md#streamable-http) for
remote-bind authentication and the published-release boundary.
### Installable Agent Skill
```bash
codex plugin marketplace add happy520ai/unified-ai-system --ref master
npx skills add happy520ai/unified-ai-system --skill unified-ai-gateway --agent codex --copy --yes
```
The plugin pins the [reviewed immutable v0.4.9 MCP image](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/security/mcp-image-review-0.4.9.md)
and starts it without container networking or Linux capabilities.
Skill hub: https://skills.sh/happy520ai/unified-ai-system/unified-ai-gateway
For local source work:
Requires Node.js 22.18.0 or newer and pnpm 11.19.0.
```bash
git clone https://github.com/happy520ai/unified-ai-system.git
cd unified-ai-system
corepack enable
corepack prepare pnpm@11.19.0 --activate
pnpm install --frozen-lockfile
pnpm verify:public-clone
pnpm gateway demo
```
For a prepared cloud workspace, use [GitHub Codespaces](https://codespaces.new/happy520ai/unified-ai-system?quickstart=1). See the value first:
```bash
pnpm gateway demo "Build a small API for my team" --enhance --profile coding --evidence
```
For the complete credential-free clone check, run `pnpm verify:public-clone`
after the demo. The repository's devcontainer keeps the default path
provider-free. Codespaces availability and usage limits are controlled by
GitHub.
### Docker Compose
For a source checkout, start the gateway with a readiness check:
```bash
docker compose up --build -d
docker compose ps
curl http://127.0.0.1:3100/health/check
```
The service becomes `healthy` only after `/health/check` responds successfully.
When finished, stop it with:
```bash
docker compose down
```
The Compose file treats `.env` as optional and leaves provider behavior explicit;
the credential-free fake-provider path remains the default.
## Share a Verified Result
If the project helps your workflow, run one reproducible path, [star the
repository](https://github.com/happy520ai/unified-ai-system), and share the
smallest useful result through the [structured Usage Report](https://github.com/happy520ai/unified-ai-system/issues/new?template=usage-verification-report.yml).
For a ready-to-review CLI packet, append `--evidence` to the enhanced demo:
```bash
pnpm gateway demo "Build a small API for my team" --enhance --profile coding --evidence
```
Review the original request and output before sharing the generated JSON. The
packet also records `detectedSignals` and the item count for each
`compiledSections` entry, so a reviewer can see which request signals were
carried into the structured prompt without reading internal logs.
For the browser Prompt Lab, use its `Copy evidence` or `Download evidence`
action, then paste or attach the JSON in the optional Prompt Lab evidence field
of the same report.
Use `Copy share link` when you want another browser to reproduce the same local
input, profile, and language; review the prompt first because the URL fragment
contains the input text.
## Next Steps
- [Documentation](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/README.md) for setup, the CLI, prompt enhancement, and providers.
- [Codex MCP quickstart](https://happy520ai.github.io/unified-ai-system/codex-mcp-docker-quickstart.html) for the fastest agent-tool integration; the [source guide](https://github.com/happy520ai/unified-ai-system/blob/HEAD/docs/codex-mcp-quickstart.md) is kept in the repository.
- [Contributing guide](https://github.com/happy520ai/unified-ai-system/blob/HEAD/CONTRIBUTING.md) for focused changes and safe verification.
- [Usage Report template](https://github.com/happy520ai/unified-ai-system/blob/HEAD/.github/ISSUE_TEMPLATE/usage-verification-report.yml) for reproducible feedback.
- [Cite this project](https://github.com/happy520ai/unified-ai-system/blob/HEAD/CITATION.cff), [Roadmap](https://github.com/happy520ai/unified-ai-system/blob/HEAD/ROADMAP.md), and [Support](https://github.com/happy520ai/unified-ai-system/blob/HEAD/SUPPORT.md).
## Honest Boundaries
We separate what is verified from what is not claimed:
- Clean clone + fake-provider path: **Yes**
- Hosted public API: **No**
- Real provider execution by default: **No**, must be explicitly enabled
- Browser chat UI in this repo: **No** (CLI/API/MCP are first-class)
- Production ready / AGI / L5: **Not claimed**
Real provider calls are disabled by default. Configure safely via `.env.example` and `docs/providers.md`.
## Verify the Project
```bash
pnpm check
pnpm test
pnpm check:public
pnpm verify:public-clone
pnpm verify:mcp
```
CI on `master` runs Linux checks, container startup smoke tests, MCP discovery, and process-cleanup checks.
## Project Links
- [Official MCP Registry entry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.happy520ai%2Funified-ai-system/versions/0.7.0)
- [Release v0.5.0](https://github.com/happy520ai/unified-ai-system/releases/tag/v0.7.0)
- [Codex MCP server README](https://github.com/happy520ai/unified-ai-system/blob/HEAD/packages/mcp-server/README.md)
- [Roadmap](https://github.com/happy520ai/unified-ai-system/blob/HEAD/ROADMAP.md)
- [Vision](https://github.com/happy520ai/unified-ai-system/blob/HEAD/VISION.md)
- [Support](https://github.com/happy520ai/unified-ai-system/blob/HEAD/SUPPORT.md)
## Star History
If the gateway saves you a proxy migration or an afternoon of prompt cleanup,
[a star](https://github.com/happy520ai/unified-ai-system/stargazers) helps
more people find it.
[](https://star-history.com/#happy520ai/unified-ai-system&Date)