Mistral Vibe MCP config support#49
Merged
LittleCoinCoin merged 11 commits intoCrackingShells:devfrom Mar 23, 2026
Merged
Conversation
Add the adapter, strategy, model wiring, and core validations needed to treat Mistral Vibe as a first-class MCP host inside the shared host-configuration layer.
Reuse the existing MCP configure flags where possible and map them onto Mistral Vibe's native transport and auth fields so the host works through the same CLI workflow as the other integrations.
Extend the canonical fixture registry and generated filtering matrix so future MCP host changes exercise Mistral Vibe through the same shared coverage paths as the other supported hosts.
Keep the implementation notes for the new host in a dedicated reports commit so the code history stays focused while the discovery context remains available for later review.
Agent-Id: agent-7d172f15-6b95-455e-a27a-bc58509026fe
- Replace 'Mistral Vibe IDE with MCP support' with 'Mistral Vibe CLI coding agent' - Ensure accurate description across all documentation files - Maintain consistency in host identifier (mistral-vibe)
Agent-Id: agent-4b2c06a4-05c6-47fd-84e7-4c704eb9fa05 Linked-Note-Id: 3d4ca15e-5b56-430d-9ea4-f5b77e4207aa
Agent-Id: agent-4b2c06a4-05c6-47fd-84e7-4c704eb9fa05 Linked-Note-Id: 3d4ca15e-5b56-430d-9ea4-f5b77e4207aa
Agent-Id: agent-3a5c1a45-c9cd-44cf-8caf-a2ba36ec4cd7 Linked-Note-Id: de87f08e-40a3-4c70-8f99-833526ed8cd5
Agent-Id: agent-ab465f6f-4347-4a55-a0d3-064e4d929c77
cracking-shells-semantic-release bot
pushed a commit
that referenced
this pull request
Mar 23, 2026
## <small>0.8.1-dev.3 (2026-03-23)</small> * Merge pull request #49 from LittleCoinCoin/dev ([73666d9](73666d9)), closes [#49](#49) * fix(mcp-hosts): add explicit HTTP transport type for Claude URL-based co ([62f99cf](62f99cf)) * fix(mcp-hosts): always set HTTP transport type for Claude URL-based conf ([904f22b](904f22b)) * fix(mcp-hosts): remove redundant Claude Desktop/Code URL validation ([d6a75a8](d6a75a8)) * test(mcp-hosts): keep mistral vibe in shared adapter coverage ([1a81ae0](1a81ae0)) * test(mcp): add fixture for claude remote setup ([d1cc2b0](d1cc2b0)) * test(mcp): fix whitespace in Claude transport serialization test ([b5c7191](b5c7191)) * docs: correct Mistral Vibe terminology to CLI coding agent ([bfa8b9b](bfa8b9b)) * docs(mcp-hosts): add mistral vibe to supported platforms ([5130c84](5130c84)) * docs(mcp-hosts): capture mistral vibe host analysis ([4ff2758](4ff2758)) * feat(cli): let shared mcp configure target mistral vibe ([0e801d0](0e801d0)) * feat(mcp-hosts): let hatch manage mistral vibe configs ([f213971](f213971)) * ci: semantic-release streamlining ([db0fb91](db0fb91))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Features
Mistral Vibe MCP host support
Adds full MCP host support for Mistral Vibe, covering the complete adapter contract:
MCPHostType.MISTRAL_VIBEenum value andMISTRAL_VIBE_FIELDSconstant — TOML-native field set:transport,prompt,sampling_enabled,api_key_env,api_key_header,api_key_format, plus universal and timeout fieldsMistralVibeAdapter— validates exactly-one transport (commandXORurl), derives the Vibe-native discriminator (stdio/http/streamable-http) from canonical MCP fields; cross-host sync supported by promotinghttpUrltourlat serialize timeMistralVibeHostStrategy— reads/writes TOML[[mcp_servers]]array-of-tables; project-local.vibe/config.tomltakes precedence over user-global~/.vibe/config.toml; normalizestransport↔typeon read for round-trip compatibilityMCPServerConfigfields:transport(host-native discriminator),prompt,sampling_enabled,api_key_env,api_key_header,api_key_format;startup_timeout_sec/tool_timeout_secwidened frominttofloat; transport predicates (is_local_transportetc.) consulttransportbeforetype— backward-compatible with all existing hosts__init__,AdapterRegistry,BackupInfo,reporting, andEnvironmentPackageEntry.validate_host_names()_apply_mistral_vibe_cli_mappings()translates generic CLI flags to Vibe-native fields:--bearer-token-env-varmaps toapi_key_env+ Authorization header;--env-headercapped at one mapping;--cwdsuppressed; new exclusive flags:--prompt,--sampling-enabled,--api-key-env,--api-key-header,--api-key-formatBug Fixes
Claude URL-based remote config missing transport field (
fix(mcp-hosts))ClaudeAdapter.serialize()was not emitting"type": "http"for URL-based remote server configs — downstream consumers had no way to distinguish remote Claude configs from stdio ones by inspecting the serialized output alone.ClaudeAdapter.serialize()now explicitly setsfiltered["type"] = "http"whenever"url"is present in the filtered output--urlforclaude-desktop/claude-code; transport validation is the adapter's responsibility, not the CLI'sclaude_transport_regressions.jsonandtest_claude_transport_serialization.pypin the correct URL-based serialization behaviour for Claude Desktop, Claude Code, and Claude remote configurationsDeveloper Experience
CI release pipeline streamlining
Consolidated the release, publish, and Discord-notify chain into a single orchestrated workflow:
semantic-release.ymlnow owns the full pipeline:test → release → publish → notify-discord; standaloneprerelease-discord-notification.ymlandrelease-discord-notification.ymlremovedreleasejob exposespublishedandtagoutputs;publishfires only whenpublished == 'true';notify-discordfires only when publish succeedspublish.ymlmigrated frompush.tagstrigger toworkflow_call+workflow_dispatch, consumingtagdirectly from thereleasejob — eliminates the redundant manual checkout steptestandreleasejobs skip themselves onchore(release):bump commits, preventing self-triggering loopsDocumentation updates