NomOS & MCP
Your agent stays in its own tool and works with NomOS through MCP. It retrieves company knowledge, reads applicable decisions, submits new findings and requests assessments of planned actions.
NomOS for AI agents
Retrieve knowledge, check policies and submit results for review. Connected agents can use these capabilities through MCP.
The agent asks for company knowledge in the relevant room. NomOS returns an answer and its available supporting sources within the agent’s access rights. The agent can inspect a cited passage directly.
ask_brainget_passageDecisions, their status and relationships are available as structured records. The agent can inspect the basis for an earlier decision.
list_decisionsget_decisionget_decision_neighboursAgents submit knowledge and decision proposals for review. Responsible people decide what is adopted or becomes binding.
propose_knowledgepropose_decisionNomOS assesses a submitted action against applicable policies and identifies required approvals. The call returns that assessment to the agent.
validate_actionAgents can propose relationships between decisions or request a justified exception where the policy permits one. Approval remains with a person.
propose_relationrequest_exceptionThe agent can check the status of its proposals, retrieve evidence, and inspect an answer’s prerequisites or conflicts as structured data. Further work can then use the reviewed state.
list_decisionslist_knowledge_proposalsget_evidenceget_answer_relationsYour team approves sources and policies in NomOS. The connected agent retrieves relevant context within its access rights and uses it to prepare a proposal.
The agent submits its finding or decision as a draft in NomOS. The accountable person reviews it and decides whether to adopt it. Code review in the development tool remains a separate step.
Another agent retrieves the reviewed decision as a reference for its work. Checking that it still applies and fits the new case remains part of the review.
NomOS enforces permissions for access to its own resources. validate_action returns an assessment of the submitted action, including applicable policies and required approvals. To stop an external action technically, its execution path must enforce that decision. An MCP connection alone does not monitor local shell commands or direct model access.
For these paths, we agree which events, decisions and approvals are recorded. Signing, export and retention are part of the installation’s configuration.
NomGate is planned to add local control for Windows and macOS. NomOS MCP capabilities do not require a NomGate service. Explore the platform outlook ↗
Control levels and their boundaries ↗Bring your team’s coding agent. We check MCP transport, authentication, access rights and required functions against two specific workflows. This establishes which steps use context and which can also be technically controlled.
MCP stands for Model Context Protocol. For protected HTTP connections, the standard describes OAuth-based authorisation. The MCP server provides protected resources; the authorisation server issues access tokens. Integration checks establish which mechanisms the client and installation both support.