Engineer view.GFT engineer Existing MCP servers teams submitted that are waiting for review. Approve to publish into the registry, or Reject with a reason.
Consumer view.any team The live registry of approved MCP servers, discoverable by keyword (name, tag, or owner). Only APPROVED servers appear here.
Entitlement view.any team The approved servers your POSIX groups entitle you to, at your permitted risk tiers.
Producer view.customer / producer A team that already built an MCP server submits it here. It enters the onboarding queue as PENDING_REVIEW until an engineer approves it. The requester is taken from your token, not this form.
Publish an existing MCP server
Classification
Producer view.customer / producer Ask Ogma to front an existing backend — a Lambda, an OpenAPI or Smithy service, or an MCP server — behind a governed AgentCore Gateway target. No AWS resource is created by submitting. The request enters the onboarding queue as PENDING_REVIEW; the Gateway target is created only when an engineer approves it.
Onboard a backend to AgentCore
A remote topology needs a registered Ogma cross-account role in that account, or approval-time creation fails with a precondition naming the role.
A Lambda exposes no introspectable interface, so CreateGatewayTarget requires a tool schema.
A request without one is refused at intake.
The spec is the schema; do not also supply a tool schema.
Classification
Approver view.GFT engineer Continuous assurance, the class kill-switch, and the full governance record set including rejected, quarantined and revoked servers.