dtwo
v1.1.8Manage Dtwo gateways, policies, and Rego with the Dtwo MCP server.
By DtwoLicense: MIT1 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 16, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install dtwo for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install dtwo@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/dtwoai/pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is dtwo/.
Plugin files
├── .claude-plugin/plugin.json├── skills/dtwo-gateway-config/SKILL.md├── skills/dtwo-gateway-policy/SKILL.md├── skills/dtwo-policy-rego/SKILL.md├── skills/setup/SKILL.md└── .mcp.json
Included Skills4
Manage Dtwo gateway YAML configuration and MCP server definitions: edit, validate, save draft, publish, deploy, and roll back. TRIGGER when: user says "add/remove/edit MCP server", "gateway config/YAML", "change gateway auth/JWKS/SSRF/CORS", "publish/revert gateway config", "deploy gateway" after a config change; or wants to inspect/list gateway versions. SKIP when: task is writing or explaining Rego (use dtwo-policy-rego); task is attaching/detaching policies on a pipeline or pinning policy versions (use dtwo-gateway-policy).
Create, validate, attach, publish, deploy, verify, and roll back Dtwo policies and their pipeline attachments — the system-of-record skill for policy lifecycle (create/update/publish/revert), pipeline lifecycle (attach/deploy/verify), the session-state marker registry, and (when intent tools are enabled) the intent registry. TRIGGER when: user says create/modify a policy, block/allow/redact something, attach/detach policy, set/update pipeline, publish/pin a policy version, or deploy gateway after a policy change; also manage a marker/marker registry; or (only when intent tools are enabled) intent capture/registry/transitions or intent/marker compatibility. Always pair with dtwo-policy-rego for the Rego authoring step. SKIP when: task is purely explaining existing Rego with no save/attach/deploy intent (use dtwo-policy-rego); or editing gateway YAML / MCP server entries (use dtwo-gateway-config).
Generate, modify, explain, and debug Rego policy code for the Dtwo MCP Gateway (ingress and egress) — input schema, allow/deny/transform patterns, markers/session-state, debugging, and policy-store catalog contribution structure. TRIGGER when: user asks to write/modify/explain/debug a Rego policy; says block/allow/redact/transform a tool call or response; mentions OPA, package paths, input.payload, or default allow; pastes Rego for review; writes a marker writer/reader or session_writes; (only when intent tools are enabled) recognizes the platform intent-capture policies; contributes to the dtwoai/policy-store catalog; or diagnoses blanket denies or transform conflicts. Pair with dtwo-gateway-policy when the resulting Rego must be saved or deployed. SKIP when: policy CRUD or pipeline attachment that does not change Rego (use dtwo-gateway-policy); general OPA usage outside the MCP Gateway; or editing gateway YAML (use dtwo-gateway-config).
Guide a first-time user through complete Dtwo gateway setup end to end — verify the Dtwo MCP connection, choose a deployment type, create the gateway, configure authentication, add MCP servers, attach starter policies, publish, activate (self-hosted), deploy, print ready-to-paste connection instructions, and finish by authenticating to the gateway and testing the attached policies. TRIGGER when: user is setting up Dtwo for the first time, onboarding, just installed the plugin, or says "set up dtwo", "create my first gateway", "get me started", "walk me through setup". SKIP when: the user already has a gateway and wants a single focused change — editing gateway YAML or MCP server entries (use dtwo-gateway-config); attaching/detaching or publishing policies (use dtwo-gateway-policy); writing/modifying/explaining Rego (use dtwo-policy-rego).
MCP servers1
- url
- https://mcp.us1.prod.dtwo.ai/mcp
Plugin manifests1
{
"name": "dtwo",
"version": "1.1.8",
"description": "Manage Dtwo gateways, policies, and Rego with the Dtwo MCP server.",
"author": {
"name": "Dtwo",
"email": "[email protected]"
},
"homepage": "https://dtwo.ai",
"repository": "https://github.com/dtwoai/plugins",
"license": "MIT",
"keywords": [
"agentic",
"security",
"governance",
"RBAC",
"ABAC",
"Zero Trust",
"DevSecOps",
"AppSec",
"SOC",
"Guardrails",
"AI Gateway",
"LLM Proxy",
"Policy-as-Code",
"ai-gateway",
"mcp",
"mcp-gateway",
"claude-code",
"agentic-security",
"governance",
"policy-as-code",
"rego",
"opa",
"zero-trust",
"rbac",
"abac",
"pii-redaction",
"guardrails",
"llm-proxy",
"appsec",
"devsecops",
"tool-call-firewall",
"audit",
"compliance"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[dtwo on Agent Plugins Marketplace](https://pluginsmp.com/plugins/dtwo)