Skip to content

v0.2.0 — stdio MCP transport, mistral-vibe integration, JOSS-ready

Choose a tag to compare

@maurinl26 maurinl26 released this 24 Jun 09:25

Highlights

  • stdio MCP transport for fortranspire mcp — IDE-spawned servers (mistral-vibe, Claude Code, Claude Desktop) over JSON-RPC framing. No port, no auth, local-by-construction. Pytest smoke test verifies the 9-tool surface.
  • mistral-vibe integration officielle — turnkey 60-second quickstart in docs/getting-started/with-mistral-vibe.md, full walkthrough on PHYEX in docs/integrations/mistral-vibe.md.
  • JOSS paper muscled with Real-world demonstration (PHYEX kernel — 1 routine, ~$0.04 codestral, 2 s estimation), Quality control (equivalence harness on real gfortran -fopenacc kernels), and Limitations / Roadmap sections.
  • README cleanup — 1353 → 332 lines. Rich Fortran patterns content (11 patterns with before/after code) migrated to docs/concepts/fortran-patterns.md.
  • Infra cleanup — removed obsolete Dockerfile.ci and Apptainer.analyze (broken paths). ROADMAP neutralised for JOSS-friendly framing.
  • Affiliation standardised across paper.md / CITATION.cff / .zenodo.json / codemeta.json — Independent Researcher, Toulouse, France.
  • CI — new .github/workflows/docs.yml builds Sphinx in nitpicky mode on every PR touching docs.

Tooling

  • 9 MCP tools exposed: analyze_kernels, explain_port_cost, build_call_graph, generate_docs, translate_kernel_gpu, translate_kernel, profile_kernels, ask_agent, agent_status.
  • 4 of the 9 are no-LLM (deterministic Loki / AST work).

Install

uv tool install fortranspire

Full changelog: see docs/changelog.md.