Skip to main content
TalkOps Plugins Marketplace

Installation and multi-host setup

The talkops-ai/devops-plugins marketplace packages every plugin in three synchronized formats—Claude Code (.claude-plugin/), OpenAI Codex (.codex-plugin/ and .agents/plugins/marketplace.json), and the portable Agent Plugins 1.0.0 standard (plugin.json, skills/, mcp.json).

Prerequisites​

Before installing plugins that launch local MCP servers or execute deterministic safety hooks, ensure the following tools are available on your workstation or container:

RequirementPurposeVerification / Setup
uv / uvxLaunches Python-based awslabs stdio MCP servers and mcp-proxy-for-aws-cli on demandInstall uv (curl -LsSf https://astral.sh/uv/install.sh | sh)
Node.js (npx)Launches @drawio/mcp for architecture diagram plugins (aws-solutions-architect, aws-well-architected)node --version && npx --version
AWS CLI v2Provides credential resolution via AWS_PROFILE, IAM Identity Center (SSO), or IAM task/instance rolesaws --version && aws sts get-caller-identity
AWS_REGIONTarget AWS region for MCP servers (defaults to us-east-1 in Claude Code; set explicitly on other hosts)export AWS_REGION=us-east-1
Python 3Executes deterministic PreToolUse and PostToolUse safety hooks (secret-safety.py, aws-mutation-gate.py)python3 --version
Docker (Optional)Required only for optional container-based connectors like hashicorp/terraform-mcp-server or Crossplane renderingdocker info
Foundational AWS auth preflight

Install the aws-essentials vertical plugin when onboarding a new environment—it bundles signing-in-to-aws, aws-auth-and-environment-preflight, /aws-essentials:setup-auth, /aws-essentials:whoami, and the session-aws-preflight.py hook to verify credentials and region settings automatically.

Host setup guides​

1. TalkOps Framework (talkops) & OpsCode (ops)​

TalkOps and OpsCode connect natively to the talkops-ai/devops-plugins catalog both from the shell and through the interactive /plugins modal.

# Add the TalkOps DevOps Plugins marketplace
talkops plugin marketplace add talkops-ai/devops-plugins
talkops plugin marketplace list

# Install specialist sub-agents (Agent Plugins)
talkops plugin install aws-sre-agent
talkops plugin install aws-iac-engineer
talkops plugin install aws-finops-engineer

# Or install main-agent capability bundles (Vertical Plugins)
talkops plugin install aws-networking
talkops plugin install aws-serverless
talkops plugin install aws-databases

In OpsCode (ops), you can also qualify plugins with @talkops-devops-plugins:

ops plugin marketplace add talkops-ai/devops-plugins
ops plugin install aws-sre-agent@talkops-devops-plugins
ops plugin install aws-containers@talkops-devops-plugins

To manage plugins interactively inside an active TUI session:

  1. Run /plugins to open the plugin manager modal.
  2. Browse the Marketplaces tab to inspect bundled sub-agents, skills, commands, and MCP servers.
  3. Click Install, then run /reload to activate the plugin immediately without restarting your session.

2. Claude Code (claude)​

1
Add the marketplace catalog

Register talkops-ai/devops-plugins in Claude Code (which reads .claude-plugin/marketplace.json):

claude plugin marketplace add talkops-ai/devops-plugins
2
Install specialist sub-agents or vertical bundles

Install any combination of the 17 specialist agent plugins, 21 vertical plugins, or 2 partner-built plugins:

# Install specialist sub-agents (isolated context & MCP tools)
claude plugin install aws-sre-agent@talkops-devops-plugins
claude plugin install aws-iac-engineer@talkops-devops-plugins
claude plugin install aws-solutions-architect@talkops-devops-plugins

# Or attach domain capabilities directly to your main agent
claude plugin install aws-networking@talkops-devops-plugins
claude plugin install aws-serverless@talkops-devops-plugins
claude plugin install aws-databases@talkops-devops-plugins
3
Invoke sub-agents, skills, and slash commands
  • Automatic sub-agent delegation: Claude delegates to an installed agent plugin automatically based on its description routing signal.
  • Explicit sub-agent mention: Mention @agent-<plugin>:<agent> (for example, @agent-aws-sre-agent:aws-sre-agent).
  • Run a specialist as the main thread: 
    claude --agent aws-sre-agent:aws-sre-agent
  • Vertical skills & multi-phase workflows: When using a vertical plugin, skills activate automatically on relevant tasks or explicitly via /<plugin>:<skill>, and multi-phase operational playbooks execute via /<plugin>:<command>: 
    /aws-networking:trace-connectivity
    /aws-databases:troubleshoot-db
    /aws-observability:triage-incident
    /aws-cost-optimization:waste-hunt-audit

3. OpenAI Codex (codex)​

1
Register the Codex marketplace

Codex reads .agents/plugins/marketplace.json at the repository root:

codex plugin marketplace add talkops-ai/devops-plugins
2
Enable plugins in Codex

Install plugins interactively from the Plugins Directory (/plugins), or enable them declaratively in ~/.codex/config.toml:

~/.codex/config.toml
[plugins."aws-iac-engineer@talkops-devops-plugins"]
enabled = true

[plugins."aws-networking@talkops-devops-plugins"]
enabled = true

Codex automatically loads each plugin's skills, MCP servers (from the portable mcp.json), and hooks. Approve the hooks when Codex prompts you to trust them.

3
Optional: Install Codex custom sub-agent definitions

Because Codex plugins cannot bundle sub-agent personas directly, every agent plugin ships a pre-rendered Codex custom agent definition under codex/agents/<name>.toml. Copy it into ~/.codex/agents/ to spawn the specialist as a sub-agent in Codex:

cp plugins/agent-plugins/aws-iac-engineer/codex/agents/aws-iac-engineer.toml ~/.codex/agents/
cp plugins/agent-plugins/aws-sre-agent/codex/agents/aws-sre-agent.toml ~/.codex/agents/
4
Pass AWS profile and region to Codex MCP servers

Codex starts MCP server subprocesses with a minimal environment. If an MCP server cannot see your shell's AWS profile, configure AWS_PROFILE and AWS_REGION in ~/.codex/config.toml.

4. Other Agent Plugins 1.0.0 hosts (Cursor, Copilot, Gemini CLI / Antigravity, Windsurf)​

Every agent, vertical, and partner plugin includes a root plugin.json, skills/ directory, and portable mcp.json conforming to the Agent Plugins 1.0.0 specification:

# Clone the marketplace locally to load individual plugin directories into any host
git clone https://github.com/talkops-ai/devops-plugins.git

Point your agent host at devops-plugins/plugins/agent-plugins/<name> or devops-plugins/plugins/vertical-plugins/<name> to load its SKILL.md playbooks and portable mcp.json server definitions.

Configuring optional connectors (CONNECTORS.md)​

Bundled MCP servers start automatically using only your ambient AWS credentials. However, 11 connection-bound MCP servers require a specific target endpoint, cluster identifier, Secrets Manager ARN, or local Docker runtime at startup (for example, Aurora DSQL, DocumentDB, Neptune, Keyspaces, Valkey, Memcached, SQL Server, Oracle, Timestream for InfluxDB, scoped Lambda/Step Functions tools, and hashicorp/terraform-mcp-server).

Because plugin MCP manifests have no cross-host "disabled": true flag, these servers are documented in each plugin's CONNECTORS.md with copy-pasteable registration commands:

# Example: Adding the HashiCorp Terraform MCP connector in Claude Code
claude mcp add terraform -- docker run -i --rm hashicorp/terraform-mcp-server:1

# Example: Adding the Aurora DSQL connector
claude mcp add aurora-dsql -- uvx awslabs.aurora-dsql-mcp-server@latest \
  --cluster_endpoint <your-cluster-endpoint> \
  --region us-east-1 \
  --database_user admin

Once registered under the documented key (such as terraform or aurora-dsql), specialist agent plugins automatically grant access to mcp__<key>__* in their tool allowlist. See MCP Coverage & Authoring for the complete connector matrix.

On this page