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

mcp-github-mule-devops-actions

v0.1.18

Published

MCP server for using the GitHub Actions API for Mule DevOps

Readme

github-mule-devops-mcp

An MCP server for Mule DevOps GitHub Actions. This server exposes a single tool:

  • setup_mule_project_with_devops: Triggers a specific GitHub Actions workflow to create a new Mule API project repo with fully implemented CI/CD and deployment to a dev environment.

Features

  • Securely triggers a GitHub Actions workflow for MuleSoft DevOps automation
  • Reads required organization and group IDs from environment variables
  • Ready for integration with Claude Desktop, Windsurf, or any MCP-compatible client
  • Modular and ready for future tool expansion

Environment Variables

Set these before running the server:

  • GITHUB_PERSONAL_ACCESS_TOKEN: Your GitHub token (with repo/workflow permissions)
  • GITHUB_ORG: Your GitHub organization name
  • MULESOFT_GROUP_ID: Your Anypoint/MuleSoft group ID

Example (Unix/macOS):

export GITHUB_PERSONAL_ACCESS_TOKEN=ghp_xxx
export GITHUB_ORG=my-org
export MULESOFT_GROUP_ID=12345678-aaaa-bbbb-cccc-1234567890ab

Build & Run

1. Install dependencies

npm install

2. Build the project

npm run build

3. Run the server

node dist/index.js

Usage with MCP Clients

Example MCP config (mcp.json):

{
  "mcpServers": {
    "github-mule-devops-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/github-mule-devops-mcp/dist/index.js"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token_here",
        "GITHUB_ORG": "your_org_here",
        "MULESOFT_GROUP_ID": "your_group_id_here"
      }
    }
  }
}

Tool: setup_mule_project_with_devops

Inputs:

  • artifactId (string, required)
  • apiType (string, default: "system")
  • applicationName (string, required)
  • deployment_target ("cloudhub" | "rtf", default: "cloudhub")
  • cloudhub_region (optional, default: "cloudhub-eu-west-1")

Environment:

  • GITHUB_ORG and MULESOFT_GROUP_ID are read from environment variables.

Local Development with npm link

  1. In your package directory:
    npm run build
    npm link
  2. In your consumer/test project:
    npm link github-mule-devops-mcp
  3. Now you can use the CLI or require the package locally.

To remove:

npm unlink github-mule-devops-mcp
npm unlink -g github-mule-devops-mcp

Publishing to npm

  1. Update your version in package.json.
  2. Login to npm:
    npm login
  3. Publish:
    npm publish --access public
  4. Now anyone can run:
    npx github-mule-devops-mcp

Example: Testing Your Deployed API with Postman or curl

Postman:

  • Method: POST
  • URL: https://your-api-url/api/dates
  • Headers: Content-Type: application/json
  • Body (raw, JSON):
    { "input_date": "2025-07-07" }

curl:

curl --location "https://your-api-url/api/dates" \
  --header 'Content-Type: application/json' \
  --data '{"input_date": "2025-07-07"}'

Contributing

Pull requests and issues are welcome! Please open an issue to discuss your ideas or report bugs.


License

MIT