Overview
scala-semantic-harness is experimental semantic tooling for Scala and functional-programming projects used by coding agents. It is described as a bounded semantic evidence layer, not a replacement for the Scala compiler, sbt, tests, Metals, or other IDE/LSP tooling. Compiler, build, and test results remain the final correctness oracle. The current tree is a standalone experimental public-alpha source product under the Apache-2.0 license.
The harness provides structured compile, test, and diagnostic reports; SemanticDB inventory, coverage, symbol, and exact-symbol usage evidence; bounded Presentation Compiler symbol and type queries; reconciliation of dynamic compiler evidence with an explicit SemanticDB artifact; conservative syntax-first FP effect summaries; and a stdio MCP server exposing exactly eight public tools. It includes modules for core, cli, sbt-runner, semanticdb-reader, presentation-compiler, semantic-reconciliation, fp-analyzers, mcp-server, and benchmark.
The project uses Scala 3 and sbt. A fresh source setup requires JDK 21, sbt, Git, and Python 3; CI uses Temurin JDK 21. The exact eight-module 0.1.0-alpha.3 release is published on Maven Central, and the public main two-application Coursier channel selects it. The CLI and generic stdio MCP server can be installed with Coursier.
Pricing
Free
Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.
Visit WebsitePrices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.
Use Cases
- Teams use scala-semantic-harness to obtain structured compile, test, and diagnostic reports.
- Teams use it to gather SemanticDB inventory, coverage, symbol, and exact-symbol usage evidence.
- Teams use it to run bounded Presentation Compiler symbol and type queries.
- Teams use it to reconcile dynamic compiler evidence with an explicit SemanticDB artifact.
- Teams use it to expose exactly eight public tools through a stdio MCP server.
- Teams use it to generate conservative syntax-first FP effect summaries.
- Teams use it to integrate sbt compile/test subprocesses.
- Teams use it to provide a client-neutral semantic-scala agent skill.
Features
Check Scala compiler results
Use test results as evidence
Inspect SemanticDB information
Gather presentation compiler evidence
Reconcile Scala symbols
Analyze functional programming code
Access tooling through CLI or MCP
Reviews
No reviews yet. Be the first to share your experience!