harmony-mcp

io.github.AbduljabbarBXRPublished by GitHub account AbduljabbarBXRv0.1.5Updated Oct 27, 2026

Repo rules enforcement for AI agents. Checks diffs against repo conventions.

The publisher's own server: Harmony

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local stdio MCP server that enforces repository rules, letting an assistant check code diffs against a repo's conventions.

What you can do
  • Check diffs against repository conventions
  • Enforce repo rules for AI agents working in a codebase
  • No individual tools are documented in the supplied listing, so the exact operations are not described.
When to use it
Useful when an assistant edits code in a repository that has documented conventions and you want its changes checked against those rules before they are accepted.
Requirements
Runs as a local process on the user's machine via the npm package harmony-mcp over stdio. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The listing documents no tools, so what the server reads or changes is unclear; review the package before installing. No credentials are requested in the manifest.

Installation

In SourceWeft

  1. Open harmony-mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.5LatestSep 17, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Harmony integrations