Skip to main content
Glama

wiswa-mcp

Python versions PyPI - Version GitHub tag (with filter) License GitHub commits since latest release (by SemVer including pre-releases) CodeQL QA Tests Coverage Status Dependabot Documentation Status mypy uv pytest Ruff Downloads Stargazers pre-commit.ci status Prettier

@Tatsh Buy Me A Coffee Libera.Chat Mastodon Follow Patreon

FastMCP server exposing Wiswa settings discovery to AI assistants such as Claude Code, Cursor, and GitHub Copilot.

Installation

pipx install wiswa-mcp

Related MCP server: 1mcpserver

Usage

wiswa-mcp

The server publishes the following MCP tools:

  • get_defaults — return resolved default settings, optionally narrowed to a dot-separated key path.

  • lookup_setting — return a single setting's default value plus a ready-to-paste .wiswa.jsonnet override snippet.

  • list_settings — enumerate the keys available at a given path and depth.

  • search_settings — substring search across fully-qualified setting key paths.

Claude Code

claude mcp add wiswa-mcp -- wiswa-mcp

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "wiswa-mcp": {
      "command": "wiswa-mcp"
    }
  }
}

GitHub Copilot CLI

Add to .github/copilot/mcp.json:

{
  "mcpServers": {
    "wiswa-mcp": {
      "command": "wiswa-mcp"
    }
  }
}

Available Tools

4 tools
get_defaultsA

Get resolved default settings, optionally narrowed to a dot-separated key path.

Inputs: key_path. Returns: result

list_settingsA

List setting keys at a given path and depth.

Inputs: key_path, depth. Returns: result

lookup_settingA

Look up a setting by dot-separated key path and get its default value plus override snippet.

Inputs: key_path (required). Returns: result

search_settingsA

Search for settings by substring match on their fully-qualified key path.

Inputs: query (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: getting resolved defaults, listing keys, looking up a specific setting, and searching by substring. No overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (get_defaults, list_settings, lookup_setting, search_settings), making them predictable and easy to remember.

    Tool Count5/5

    With 4 tools, the server is well-scoped for a settings management utility. Each tool covers a distinct operation without unnecessary bloat or deficiency.

    Completeness5/5

    The tool set covers the core operations for inspecting settings: retrieving defaults, exploring the key hierarchy, looking up specific keys, and searching. No obvious gaps for a read-only configuration server.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers