npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@devopsagent/mcp-server

v1.0.6

Published

MCP server for DevOps Agent — manage AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, and more from any MCP-compatible AI client. 727 tools across 17 modules.

Readme

DevOps Agent MCP Server

Manage AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, Docker, Ansible, and more from any MCP-compatible AI client. 727 tools across 17 modules — all accessible via a single connection.

Prerequisites

  • Node.js 18+ — required to run the stdio bridge via npx
  • An API key from devopsagent.io (see Getting Your API Key)
  • No npm account needed — you're just a user of the published package

Getting Your API Key

  1. Log in at devopsagent.io
  2. Navigate to Settings → API Keys
  3. Click Generate Key — your key will be prefixed with doa_live_
  4. Copy it and use it as DEVOPSAGENT_API_KEY in the steps below

Installation via npm (Claude Desktop / Claude Code)

Step 1: Get your API key (see above)

Step 2: Find your Claude Desktop config file:

  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Step 3: Add this to the file (create it if it doesn't exist):

{
  "mcpServers": {
    "devops-agent": {
      "command": "npx",
      "args": ["-y", "@devopsagent/mcp-server"],
      "env": {
        "DEVOPSAGENT_API_KEY": "your_api_key_here"
      }
    }
  }
}

Step 4: Fully quit and restart Claude Desktop.

All 727 tools will appear automatically under the tools (hammer) icon in the chat input.

The npx command downloads and runs the bridge automatically on first use — nothing else to install.

Installation via Remote URL (Claude.ai Connectors)

No Node.js needed for this method — Claude.ai connects directly to the hosted server.

  1. Go to Claude.ai → Settings → Connectors → Add Integration
  2. Enter the Integration URL: https://devopsagent.io/mcp/
  3. Claude.ai will trigger OAuth automatically — log in with your devopsagent.io account to authorize
  4. All 727 tools become available immediately

Verifying the Connection

Run this curl command to confirm your API key works before adding it to Claude Desktop:

curl -s https://devopsagent.io/mcp/ \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'

Expected response:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "protocolVersion": "2025-03-26",
    "serverInfo": { "name": "DevOps Agent", "version": "1.0.3" },
    "capabilities": { "tools": { "listChanged": false } }
  }
}

If you get a 401 response, your API key is invalid or not yet created.

You can also test the stdio bridge directly in your terminal:

DEVOPSAGENT_API_KEY=your_api_key_here npx -y @devopsagent/mcp-server@latest

It will hang waiting on stdin — that means it's working. Paste the line below and press Enter:

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}

You should see the JSON response above. Press Ctrl+C to exit.

Troubleshooting

"Couldn't reach MCP server" in Claude.ai

  • Re-add the connector — go to Settings → Connectors, remove the existing entry, and add it again
  • Make sure the OAuth flow completed fully (you were redirected back to Claude.ai after logging in)
  • Try the curl verification command above to confirm the server is reachable

npx fails with command not found or exits silently

  • Confirm Node.js 18+ is installed: node --version
  • Confirm DEVOPSAGENT_API_KEY is set — if missing, the bridge exits immediately with an error on stderr
  • Try with an explicit version: npx -y @devopsagent/mcp-server@latest
  • Clear the npx cache and retry: npm cache clean --force

Tools not appearing in Claude Desktop

  • Fully quit Claude Desktop (check system tray / menu bar) and reopen — a window close is not enough
  • Check the config file path is correct for your OS (Windows vs macOS differ)
  • Validate your JSON is well-formed — a single missing comma breaks the whole config

401 Unauthorized errors

  • The API key must be created at devopsagent.io/settings (keys prefixed doa_live_ are valid)
  • Keys are per-user — make sure you're logged into the right account when generating

tools_loaded shows an unexpected number

  • The server exposes 727 tools across 17 modules — this is the correct count
  • If you see a different number, the server may be mid-deploy; retry after a minute

Tools

| Module | Count | What you can do | |--------|-------|-----------------| | AWS | 334 | EC2, S3, RDS, Lambda, ECS, EKS, IAM, VPC, CloudWatch, DynamoDB, and more | | Kubernetes | 76 | Pods, Deployments, Services, Namespaces, Ingress, Jobs, Nodes | | Azure | 38 | VMs, Storage, SQL, NSGs, Container Instances, VNets, Public IPs | | GCP | 42 | Compute, GCS, Cloud SQL, GKE, Cloud Run, Pub/Sub, BigQuery, Functions | | CI/CD | 35 | Jenkins + GitHub Actions | | Docker | 22 | Containers, images, volumes, networks, compose, build, push | | Terraform | 25 | init, plan, apply, destroy, state, workspaces, import | | Ansible | 13 | Playbooks, ad-hoc, inventory, vault, galaxy | | Monitoring | 12 | Prometheus, Datadog, Grafana | | Alerting | 16 | PagerDuty + OpsGenie | | SonarQube | 12 | Projects, quality gates, issues, analysis | | Nexus | 12 | Repositories, components, assets | | Git | 47 | Clone, branch, commit, push, pull, merge, rebase, tags, stash, search | | GitHub | 19 | Repos, issues, PRs, branches, releases, workflows, collaborators |

Environment Variables

| Variable | Required | Default | Description | |----------|----------|---------|-------------| | DEVOPSAGENT_API_KEY | Yes | — | API key from devopsagent.io Settings → API Keys | | DEVOPSAGENT_MCP_URL | No | https://devopsagent.io/mcp/ | Override endpoint (self-hosted instances only) |

Server Details

| Property | Value | |----------|-------| | MCP Protocol | 2025-03-26 | | Transports | Streamable HTTP (POST /mcp/) + HTTP+SSE (GET /mcp/sse) + stdio (via npx) | | Auth | OAuth 2.0 (Claude.ai) or API Key (Claude Desktop / npx) | | Registry | io.github.shittuay/devops-agent | | Health check | GET https://devopsagent.io/mcp/health |

Links