YAADMINWhat is YAADMIN?
A chat-driven administration runtime that selects registered tools and coordinates execution with permissions, approvals and activity/results.
Is YAADMIN free?
All seven audited first-party module manifests declare a free tier, and runtime entitlement enforcement is disabled. An explicit Core pricing/free-distribution contract was not established by the technical audit; this is not a price or future licensing guarantee.
What can YAADMIN connect to?
Current native providers include Action1, read-only AD and read-only 1C HTTP services. Compatible external MCP servers and custom modules can add actual implemented tools.
What is MCP?
A protocol for connecting independent tool servers. YAADMIN implements supported initialization, tool discovery and invocation over STDIO/HTTP; broader protocol features have limits.
Can I connect my own MCP server?
Yes, where its transport/authentication behavior matches the supported implementation. Personal OAuth-protected discovery and full protocol interoperability are not guaranteed.
Can permissions be configured per tool?
Yes. Native tools map to declared permissions, and discovered MCP tools receive dynamic per-tool permissions. Some native tools share a permission; execution access is distinct from catalog visibility.
How do approvals work?
They bind one exact request fingerprint to an owner/session, support preview/approve/reject/expiry and one-time consumption. State is in memory; self-approval defaults to enabled.
Can YAADMIN use Active Directory?
AD authentication paths and read-only directory tools exist. AD availability/configuration matters, and first-login provisioning does not automatically grant roles.
Can I create custom modules?
Yes. External packages provide a manifest, Python entrypoints and registered tools/permissions within the actual SDK contracts.
Do custom modules require Core changes?
Supported external entrypoint/tool contracts integrate through generic discovery and registries without Core edits. Arbitrary new UI contracts are not automatically supported.
What built-in modules exist today?
action1, ad, codex, files, mcp, onec and targets. Codex is disabled by default; its bootstrap tool is internal. RAS, Terminal Server, Dahua/Video, U-Prox and n8n are not verified native modules.
Does YAADMIN currently enforce module licenses?
No. Local entitlement records/subjects exist, but runtime enforcement is explicitly disabled. Remote activation/email verification is not verified.
How do updates work today?
The foundation validates catalogs, versions, compatibility, hashes/signatures and staging. Installation, rollback and restart execution remain incomplete/declarative.