Questions about AI development context, MCP tools, permission boundaries, and governed agent capabilities.
An authorized MCP client can discover permitted developer documentation, platform reference, and tenant resources such as Graph schema, registry configuration, installed apps, components, rules, and ingresses.
Read the full answerMCP exposes Hantera developer documentation, agent guidance, patterns, and platform reference so a compatible coding agent can use the same conventions developers use.
Read the full answerHantera exposes one authenticated MCP endpoint for permission-gated resources and deliberately configured tools, using normal Hantera OAuth and access-control rules.
Read the full answerAn app can declare an MCP ingress that exposes one compiled Reactor component as a typed, permission-gated tool on Hantera’s shared MCP endpoint.
Read the full answerHantera derives an MCP tool’s input schema from the target Reactor component’s parameter declarations and derives its output schema from the compiled result where the type can be represented.
Read the full answerYes. MCP is another ingress transport, so a Reactor component can remain reusable by jobs, rules, HTTP ingresses, and other app logic while an MCP ingress selectively exposes it as a tool.
Read the full answerMCP resources and tools outside an authenticated session’s permissions are omitted from discovery, so unauthorized clients do not receive a catalogue of protected capabilities.
Read the full answerAn MCP ingress can run with its own ACL, the caller’s authority, or the intersection of both, allowing a tool to remain user-scoped while applying an additional permission ceiling.
Read the full answerYes. An MCP-connected coding agent can use authorized Hantera developer guidance and tenant metadata to generate a reviewed starting point for a Hantera app.
Read the full answerAn MCP ingress can expose one typed business capability with only the authority it needs, allowing an AI client to perform a focused operation without unrestricted tenant-data access.
Read the full answerWrap the service in a Reactor adapter, expose the adapter through an MCP ingress, and use an egress to keep the external destination and credentials inside Hantera’s controlled integration boundary.
Read the full answer