Ory DX: Agent Plugins

Coding agents don't build auth. They use Ory.

Add customer identity, OAuth, permissions, B2B SSO, or agent security with Ory best practices built in. One command spins up a local stack in seconds.

Works with the agents, frameworks, and deployment methods you already use

Give your agents identities of their own.

Ory Agent Security gives every agent its own identity, scoped to what it actually needs and revocable. Early adopters run it on Ory Network at no cost. Free coverage for a limited time.

Building with Ory has never been easier

• Skill catalog

Skills cover full auth setup with Ory Elements, login and registration with recovery, verification, and settings, social sign-in with major providers such as Google, Apple, and more.

• One-command local stack

One command brings Kratos, Hydra, and Keto, online locally — seeded and ready. No cloud account, no config files from scratch necessary.

• Ory best practices baked in

Built on Ory Elements, the Ory SDKs, and OAuth 2.1 with PKCE means your agent generates the same patterns recommended in Ory documentation and examples. Even better? Plugins are out of the box-ready for Ory Agent Security.

• Industry-leading harnesses & SDKs

Same skills and policies across Claude Code, Codex, Gemini CLI, OpenClaw, OpenCode, and more. One package per agent on a shared client enables you to remain platform and framework-agnostic, including SDK frameworks and custom agents.

• MCP server included

The Ory CLI and REST API are exposed as MCP tools. Your agent creates identities, registers OAuth clients, and manages relation tuples without you copy-pasting commands.

• Built for flexibility & security

Self-hostable end-to-end. Run open-source Kratos, Hydra, and Keto locally with no vendor lock-in. Or, use Ory Network to get started in minutes, including Ory Agent Security — all fully managed.

How the Ory Agent Plugin works

Install once, work across agentic coding tools

The plugin ships as an npm package per agentic coding tool (@ory/claude-code, @ory/codex, @ory/gemini-cli, @ory/openclaw, @ory/opencode), all built on a shared client. Install it the way you'd install any other plugin through Claude Marketplace, the Gemini CLI extensions directory, or a single npm command. Your coding agent picks up the Ory skill catalog, slash commands, and local-stack tooling automatically.

Skills that know Ory

Skills are the playbooks your agent follows when you ask it to "add login," "add Google sign-in," or "set up a permission model." The plugin ships a canonical catalog, for example:

• ory-local-dev: drive a local Ory instance for offline or prototyping work
• ory-auth-setup: full Ory Network setup wired through Ory Elements
• ory-login-flow: login, registration, recovery, verification, and settings flows
• ory-social-login: Google, GitHub, Apple, Microsoft, and other OIDC providers
• ory-build-agent: wire Ory into your own agent — Mistral AI, OpenAI, Claude, Salesforce, and more
• ory-temporal-worker: wire Ory into your Temporal worker
• ory-e2b-sandbox: create an E2B sandbox with Ory Agent Security built in
• ory-build-integration: wire an Ory webhook into your app

A local Ory stack, one command away

local up brings up a Docker-based Ory dev environment, all reachable at localhost:4000. The stack is seeded with a working identity schema and example clients, so the moment your agent finishes scaffolding the frontend, there's already a backend that responds to it. local down tears it back down. No leftover containers, no shared cloud state between projects.

MCP server for the Ory CLI

The plugin includes @ory/mcp-server, which exposes the Ory CLI and REST API as MCP tools. Your coding agent can create identities, register OAuth clients, manage relation tuples, and inspect Ory Network projects directly — without you copy-pasting commands. The same MCP server works against a local stack or an Ory Network project, so the agent's workflow doesn't change when you graduate from local dev to a hosted environment.

Ory Agent Security: One security plane for all of your AI agents.

Building agents? Running them in production? Then the gap is already open. The good news is Ory Agent Plugins provide the scaffolding for Ory Agent Security, providing in-the-loop controls and enforcement built directly into the agent runtime.

Frequently asked questions

What are Ory Agent Plugins?

A set of npm packages — one per supported agentic coding tool — that teach AI coding agents how to scaffold Ory authentication, authorization, and identity into a codebase. It ships skills, slash commands, an MCP server for the Ory CLI and REST API, and a local Ory stack manager.

Which agentic coding tools are supported by Ory?

Claude Code (@ory/claude-code), Codex (@ory/codex), Gemini CLI (@ory/gemini-cli), OpenClaw (@ory/openclaw), and OpenCode (@ory/opencode).

How does the plugin handle agent identity and credentials?

By default it uses OAuth 2.0 Dynamic Client Registration (RFC 7591). On first run, the agent registers itself with your project's /oauth2/register endpoint. Issued credentials persist locally and are reused on later sessions. Static credentials (ORY_AGENT_API_KEY or ORY_AGENT_CLIENT_ID + SECRET) can preempt DCR when you need them — useful for CI. Every outgoing Ory API call carries the agent's bearer token, so the audit log shows which agent acted and on whose behalf.

What do I get with a commercial Ory Enterprise License?

Ory Enterprise License (OEL) is the commercial tier for teams running Ory in production on their own infrastructure. It hardens the deployment for scale and performance, adds multi-region replication, ships production-ready defaults, and brings long-term support releases that go beyond the OSS cadence.