Skip to content

Overview ​

MuleSoftForge: Platforms are Communities, Assets Save Time, Open Source is Fun

MuleSoftForge is one home for open-source MuleSoft assets built by the community: connectors, modules, tools and policies, documented the same way and installable from public repositories.

What you get ​

  • One place to look. Every asset is listed in All Assets, with its latest version, requirements and license.
  • Consistent docs. Each asset has an overview, a Set Up page and a page per operation, with its own sidebar.
  • Installable releases. Connectors and modules are published to Maven Central; the version on each page is read from Maven Central when the site is built.
  • Open source. Source is on GitHub. Fork it, fix it, and send it back.

How it works ​

  1. Propose. Someone opens a proposal for an asset the community needs.
  2. Build. The asset is built in its own repository under the MuleSoft-Forge organization, with tests and a working example.
  3. Publish. A release goes to Maven Central (or the right channel for a tool or policy), and the docs land on this site.
  4. Maintain. A named maintainer answers issues, and anyone can contribute fixes.

Origin story ​

In September 2007, MuleSource launched MuleForge, a shared community environment for MuleSoft assets.

In February 2025, a LinkedIn outreach seeking help to build a MuleSoft Java SDK connector led to the revival of MuleSoft Forge.

Hello MuleSoft Community!

View LinkedIn Post

Personal and partner-hosted assets are valuable, but scattered across the ecosystem they cause asset sprawl: hard to find, inconsistently documented, and easy to abandon. A central home fixes that. The MuleSoft IDP Connector, led by Reza Lexén and George Jeffcock, was the first asset built this way.

Contributors ​

jeffcockrhoeggamirkhan-ak-sfmtransierrlexen

Want to join them? Start with How to Contribute.

Site content released under the Apache License 2.0. Each asset carries its own license. RSS · llms.txt