Command Palette

Search for a command to run...

UnylyUnyly
Browse all

Org Ai Force

FreeNot checked

Enterprise Angular 21 AI agent workspace with NestJS orchestrator, RAG, MCP tools, SSE streaming, Playwright workers, admin console, and internal pilot workflow

GitHubEmbed

About

Enterprise Angular 21 AI agent workspace with NestJS orchestrator, RAG, MCP tools, SSE streaming, Playwright workers, admin console, and internal pilot workflows.

README

Enterprise Angular 21 agent workspace prototype with a NestJS orchestrator, admin-governed tools, RAG-ready services, MCP-style integrations, SSE streaming hooks, Playwright/browser workers, and internal pilot operations.

This repo is a prototype and architecture proof project, not a claim of production enterprise adoption. It is designed to show how an internal AI agent workspace could be structured across frontend, backend, admin governance, and pilot rollout concerns.

What Is Implemented Vs Mock Vs Planned

Implemented

  • Angular 21 workspace shell with routes for agents, admin, pilot, ops, logs, readiness, and debug tools
  • NestJS server modules for auth, agents, tools, RAG, connectors, pilot ops, observability, and browser workers
  • role and permission guards for the frontend and backend
  • Docker and Docker Compose setup for a local or pilot-style environment
  • Prisma schemas for SQLite and PostgreSQL-oriented deployment paths
  • mock-safe workspace behavior for agent sessions, artifacts, tool events, approvals, and test-worker style flows

Mock Or Demo-Safe

  • many agent responses and runtime events in frontend demo mode
  • demo tools, demo workflows, demo approvals, and pilot feedback seed data
  • browser and Playwright worker experience when used as a safe prototype path
  • some admin and pilot dashboard content when running without a fully wired backend stack

Planned Or Still Maturing

  • deeper production-grade provider integration and hardening
  • fuller RAG citation and retrieval UX
  • richer evaluation dashboards and agent scorecards
  • multi-tenant controls and broader connector coverage
  • stronger production observability and automated validation coverage

Architecture

flowchart LR
    User["Internal user"] --> Frontend["Angular 21 workspace"]
    Frontend --> Agents["Agent workspace routes"]
    Frontend --> Admin["Admin console"]
    Frontend --> Pilot["Pilot hub"]
    Frontend --> Ops["Ops and readiness views"]
    Frontend --> Api["NestJS orchestrator API"]

    Api --> Auth["Auth and RBAC"]
    Api --> Orchestrator["Agent orchestration"]
    Api --> RAG["RAG and context layer"]
    Api --> Tools["Tool registry and approvals"]
    Api --> MCP["MCP-style integrations"]
    Api --> Browser["Browser and Playwright workers"]
    Api --> Observability["Metrics, readiness, logs"]
    Api --> Data["Prisma with SQLite or PostgreSQL"]

Local Docker Quick Start

  1. Copy the environment template:
cp .env.docker.example .env
  1. Set required values in .env, especially secrets such as POSTGRES_PASSWORD, JWT values, and provider keys when needed.

  2. Start the stack:

docker compose up --build
  1. Open the frontend:
http://localhost:8080

Use local development instead if you want to run frontend and backend separately.

Local Development

Frontend:

npm install
npm start

Backend:

cd server
npm install
npm run build
npm run start:dev

Demo Routes

  • /login
  • /dashboard
  • /agents
  • /agents/:slug
  • /admin
  • /pilot
  • /pilot/metrics
  • /pilot/readiness
  • /agent-readiness
  • /ops
  • /mcp-debug
  • /internal-tools-debug
  • /browser-test-debug

Demo Surfaces

  • agent workspace with chat, artifacts, approvals, tool window, and runtime events
  • admin overview with visible mock tools, workflows, approvals, and platform summary
  • pilot hub with rollout guidance, feedback loops, and readiness framing
  • readiness report showing priority-agent status

Screenshots

Available assets:

  • docs/assets/screenshots/workspace.png
  • docs/assets/screenshots/admin-dashboard.png
  • docs/assets/screenshots/pilot-hub.png
  • docs/assets/screenshots/readiness-report.png
  • docs/assets/screenshots/tool-execution-timeline.png
  • docs/assets/screenshots/org-ai-force-demo.gif

Org AI Force workspace screenshot

Org AI Force admin dashboard screenshot

Org AI Force pilot hub screenshot

Org AI Force readiness report screenshot

Org AI Force tool execution timeline screenshot

Capture guidance:

Security Model

  • no secrets should be committed to the repo
  • admin and debug routes are permission-gated
  • tool execution and approvals are treated as governed flows
  • mock mode exists for safe demoing when live systems are unavailable
  • Docker and environment templates are examples, not a substitute for real vaulting, HTTPS, or production secret handling

Start with:

Documentation

Recruiter Review

For the fastest walkthrough, use:

Validation Commands

Frontend:

npm run build
npm run typecheck

Backend:

cd server
npm run build
npm run typecheck

Docker:

docker compose config

from github.com/AnkitParekh007/org-ai-force

Installing Org Ai Force

This server has no published package — it is built from source. Open the repository and follow its README.

▸ github.com/AnkitParekh007/org-ai-force

FAQ

Is Org Ai Force MCP free?

Yes, Org Ai Force MCP is free — one-click install via Unyly at no cost.

Does Org Ai Force need an API key?

No, Org Ai Force runs without API keys or environment variables.

Is Org Ai Force hosted or self-hosted?

Self-hosted: the server runs locally on your machine via the install command above.

How do I install Org Ai Force in Claude Desktop, Claude Code or Cursor?

Open Org Ai Force on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.

Related MCPs

Compare Org Ai Force with

Not sure what to pick?

Find your stack in 60 seconds

Author?

Embed badge for your README

Browse similar

All development MCPs