MCP Bash Framework Updates & Release Notes

44 Einträge aus 1 Quelle. Zuletzt aktualisiert: 9. Oktober 2026

Folge MCP Bash Framework, um die Release Notes in deinen Feed zu holen.

Feed abonnieren:RSS API

2. Dezember 2025

Datum aus der Quelle.

Erstmals gesehen am 6. Oktober 2026.

[0.2.0] - 2025-12-02

Automatic getting-started mode when MCPBASH_PROJECT_ROOT is unset: stages a temporary bootstrap project with a getting_started tool, isolated registry cache, and cleanup traps (including HUP) plus clearer help text.
Framework-only bootstrap helper content and docs updates (Quick Start and Project Structure) explaining the temporary helper and how to configure real projects.
Integration coverage for the bootstrap path and stricter CLI guard for invalid project roots.
Go module for gojq (tools/go.mod/go.sum) and CI caching: setup-go module cache plus GOCACHE restored, with gojq installed via the module for reproducible tooling across OSes.
Tar-based test staging for integration/examples: shared base.tar with ACL-safe flags, reused across tests, reducing Windows I/O; integration tests now use the shared staging helper instead of per-test cp -a.
Windows CI guardrails: duration gate now warns at 4m and fails at 15m only on warm caches; Windows path handling fixed for Go caches; minor prompt/resource/tool tests refactored to honor staging.
Unified server metadata via server.d/server.meta.json: supports MCP spec fields name, title, version, description, websiteUrl, and icons. Smart defaults derive name from project directory, title from titlecase of name, and version from VERSION file or package.json. …

Mehr anzeigenWeniger anzeigen

30. November 2025

Datum aus der Quelle.

Erstmals gesehen am 6. Oktober 2026.

Stdio MCP server targeting protocol 2025-06-18 with negotiated downgrades to 2025-03-26 and 2024-11-05.
Core surfaces: lifecycle, ping, logging/setLevel, tools (list/call), resources (list/read/subscribe), prompts (list/get), completion, pagination, and listChanged notifications.
Concurrency, cancellation, timeout watchdogs, stdout corruption guards, and JSON-tool detection with minimal-mode fallback.
Registry system with TTL-based refresh, hash-based change detection, and manual registration hooks.
Elicitation support (server/client detection, tool helper APIs) and roots integration (server-initiated roots/list with fallbacks).
Tool SDK with logging/progress helpers, scaffolding commands for tools/resources/prompts, and example projects (hello tool, args/logging/progress/resources/prompts/elicitation/roots, advanced ffmpeg studio).
Compatibility and integration tests (Inspector harness, integration suites), lint/test scripts, and docs covering architecture, security, limits, performance, and Windows guidance.

Mehr anzeigenWeniger anzeigen

8. Januar 2025

Datum aus der Quelle.

Erstmals gesehen am 6. Oktober 2026.

Debug file detection: Create server.d/.debug to enable MCPBASH_LOG_LEVEL=debug persistently per-project. Eliminates boilerplate debug detection in server.d/env.sh. Environment variable takes precedence if set. See DEBUGGING.md.
Progress-aware timeout extension: Long-running tools that emit progress can now extend their timeout dynamically instead of being killed after a fixed duration. Opt-in via MCPBASH_PROGRESS_EXTENDS_TIMEOUT=true (global) or "progressExtendsTimeout": true in tool.meta.json (per-tool). The watchdog resets its idle timer on each progress emission, with a hard cap via MCPBASH_MAX_TIMEOUT_SECS (default 600s) to prevent runaway processes. Three timeout variants are now distinguished in error messages: fixed timeout, idle timeout (no progress for N seconds), and max exceeded (hard cap reached). When a tool emits progress but times out with the feature disabled, a warning is logged suggesting enablement. See BEST-PRACTICES.md §4.3 and ENV_REFERENCE.md.
Debug EXIT trap: New MCPBASH_DEBUG=true enables an EXIT trap that logs exit location and call stack on non-zero exits, helping diagnose set -e failures. Use MCPBASH_DEBUG_ALL_EXITS=true to log all exits (not just failures). Installed automatically in lib/timeout.sh when sourced. …

Mehr anzeigenWeniger anzeigen

6. Januar 2025

Datum aus der Quelle.

Erstmals gesehen am 6. Oktober 2026.

mcp_run_with_progress SDK helper: Forward subprocess progress to MCP notifications. Wraps external CLIs and parses their stderr (or a dedicated progress file) to emit progress events. Supports three extraction modes: json (NDJSON output), match1 (percentage patterns like 50%), and ratio (counter patterns like [5/10]). Includes --progress-file option for ffmpeg-style CLIs that write progress to dedicated files. See BEST-PRACTICES.md §4.8 for common patterns and usage examples.
MCPB_INCLUDE config option: New mcpb.conf setting to include custom directories in bundles beyond the defaults (tools, resources, prompts, completions, server.d, lib, providers). Supports nested paths like config/schemas. Rejects path traversal (..) and absolute paths for security. Warns on missing directories.
run-tool environment sourcing: New options for sourcing environment files before tool execution:
- --with-server-env: Sources server.d/env.sh before running the tool, matching server runtime behavior
- --source FILE: Sources any env file before execution (repeatable; sourced after --with-server-env)
- MCPBASH_RUN_TOOL_SOURCE_SERVER_ENV=1: Environment variable to implicitly enable --with-server-env for all invocations
- --print-env now shows WILL_SOURCE_SERVER_ENV and WILL_SOURCE[N] for debugging without execution
Debug enhancements: …

Mehr anzeigenWeniger anzeigen