Config Weather Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 24, 2026

Measure local configuration complexity and environment contract pressure without returning...

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that scans a project's configuration files and reports a clear, cloudy or stormy complexity signal to the assistant.

What you can do
  • Inspect a local project's configuration weather from a given path
  • Summarize configuration file count, environment reference pressure, duplicate key signals and format spread
  • Return only counts and broad categories, with values, secrets, paths, source text and key names suppressed
When to use it
Useful when you want a quick, privacy-conscious read on how tangled a project's configuration and environment contract have become, for example before a refactor or when onboarding to an unfamiliar repository.
Requirements
Runs as a local process over stdio, installed from the npm package config-weather-mcp (Node.js and npm needed). No authentication, environment variables or headers are declared. It needs a local project path to inspect.
Before you install
It reads configuration and source-like files on the local machine, though the README says only counts and broad categories are returned. It is a complexity signal, not a configuration validator, so results should not be treated as correctness checks.

Installation

In SourceWeft

  1. Open Config Weather 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.

Other MCP clients

Follow the launch instructions in the repository.

README

config-weather-mcp

Config Weather reports whether a project feels clear, cloudy, or stormy based on configuration file count, environment reference pressure, duplicate key signals, and format spread.

Quick start

bash
npm installnpm testnpm start

Use inspect_config_weather with a local project path.

Privacy and limits

The scanner reads bounded configuration and source-like files but returns only counts and broad categories. Values, secrets, paths, source text, and configuration key names are suppressed. This is a complexity signal, not a configuration validator.

Source: README.md at commit e2c9b45

Tools

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

Version history

1
  1. v1.0.1LatestSep 22, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.