techne
techne is a server of the Model Context Protocol (MCP) that gives an AI coding agent the code navigation and the refactorings of an IDE in ten languages: C, C#, Go, Java, JavaScript, Python, Ruby, Rust, Scala and TypeScript.
接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
techne is a server of the Model Context Protocol (MCP) that gives an AI coding agent the code navigation and the refactorings of an IDE in ten languages: C, C#, Go, Java, JavaScript, Python, Ruby, Rust, Scala and TypeScript.
An MCP server that gives AI agents the code navigation and refactorings of an IDE in ten languages, and states the evidence behind every answer
techne parses code with the tree-sitter grammar of each language, which is built into the binary. It binds names through the language server of the language, and it checks each change before it writes a file. Every answer states its evidence, so an agent can tell an empty list that proves absence from an empty list that does not.
Install techne with Homebrew:
brew install --cask dokimasia/tap/techne
The cask supports arm64 and amd64. It downloads the release archive for your machine and links
techne into the bin directory of Homebrew. The binary is not notarized, so on macOS the cask
removes the quarantine attribute. To update techne, run brew upgrade --cask dokimasia/tap/techne.
To install techne with brew bundle, add these lines to your Brewfile:
tap "dokimasia/tap"
cask "dokimasia/tap/techne"
Download techne_<version>_windows_amd64.zip or techne_<version>_windows_arm64.zip from the
latest release. Check its digest against
checksums.txt, and put techne.exe from the archive on your PATH.
The latest release has archives for Linux, macOS and Windows on amd64 and arm64, and
checksums.txt with the SHA-256 digest of each archive. cosign signs checksums.txt without a
key, and each archive has an SPDX SBOM. gh attestation verify checks the build provenance of an
archive or of an installed binary:
gh attestation verify "$(command -v techne)" --repo dokimasia/techne
techne uses cgo, because the grammars are C. You need Go 1.27.3 or later and a C compiler. From a checkout of this repository, run:
go build -o techne ./cmd/techne
Put the binary on your PATH. go install go.dokimi.dev/techne/cmd/techne@latest fails, because
the go.mod of techne has replace directives. techne --version prints the version of a binary.
workspace, outline, search, relations and document.symbol need only the grammar.
resolve, verify, rename.symbol, move.file and extract.function need the language server
of the language on PATH. With the server, relations returns resolved sites instead of the
sites that spell the name.
Homebrew installs every server but csharp-ls, and the .NET SDK installs csharp-ls:
brew install gopls pyright typescript-language-server rust-analyzer jdtls llvm ruby-lsp metals
dotnet tool install --global csharp-ls
Install only the servers of your languages. A server from the packages of your distribution works
as well, when its program is on PATH.
csharp-ls needs the .NET 10 SDK or later. Put ~/.dotnet/tools on your PATH, because
dotnet tool install writes the program there. capabilities lists each engine that cannot run,
with the reason.
Add techne to Claude Code for every project:
claude mcp add --scope user techne -- techne
Claude Code starts techne in the directory of each session, and techne serves that directory.
Without --scope, claude mcp add adds techne to the current project alone. --scope project
writes it into the .mcp.json of the project for everyone who works on it.
Install the skill, so that the agent uses techne in place of grep, find, cat and sed for code:
mkdir -p ~/.claude/skills/techne
curl -fsSL -o ~/.claude/skills/techne/SKILL.md \
https://raw.githubusercontent.com/dokimasia/techne/main/skills/techne/SKILL.md
Start Claude Code in a repository and ask about its code. Ask what calls a function, or ask the agent to rename a type. The first call that needs a language server starts it. Most servers start in a few seconds, and jdtls and metals take tens of seconds.
A client that reads a JSON configuration starts techne with the same command:
{
"mcpServers": {
"techne": {
"command": "techne"
}
}
}
When a client starts techne outside the project, add the path of the project to args. With
"args": ["--trust", "~/Projects"], a call can also set its field wd to any other project under
~/Projects.
An agent without techne reads code with grep and changes it with find and replace. grep
matches spelling. It returns every Close in a repository and every comment that mentions one,
and it cannot report whether it found every caller. A find and replace also renames the old name
in comments and in strings.
techne asks the parser, the type checker or the language server of the language instead. To list
the types that implement the interface Relator of this repository, an agent calls relations
with these arguments:
{"scope": "techne-core/engine/port.go", "name": "Relator", "relation": "implemented-by"}
techne returns each type with its line of code:
implemented-by Relator — 9 sites
techne-core/engine/doc_test.go:16:6 in server
type server struct{ complete }
techne-core/engine/port_test.go:57:6 in complete
type complete struct {
techne-lang-go/checker/engine.go:27:6 in Engine
type Engine struct {
techne-lang-go/constrained.go:38:6 in constrained
type constrained struct {
techne-lang-mock/engine.go:21:6 in Engine
type Engine struct {
techne-lang/lsp/engine.go:37:6 in Engine
type Engine struct {
techne-lang/lsp/lsptest/outline.go:62:6 in parser
type parser struct{ root string }
techne-lang/treesitter/engine.go:30:6 in Engine
type Engine struct {
techne-service/query/service_test.go:42:6 in answering
type answering struct {
resolved, partial coverage. the build constraints exclude 3 files from the build that the answer reads, such as techne-service/workspace/files/lock_other.go.
A Go type implements an interface without naming it, so a text search for Relator cannot list
these types. The last line states the evidence. resolved means that a type checker or a
language server bound the names. The coverage is partial because the build for Linux excludes 3
of the files that the answer reads.
techne serves each role of a language with an engine, and capabilities lists the engines:
workspace,
outline, search, relations and document.symbol at the syntactic tier, where a name
matches every declaration of that spelling.resolve,
relations, verify and the write tools at the resolved tier.golang.org/x/tools/go/packages and the go command. It serves resolve, relations,
verify and the write tools of Go, as gopls does.A call goes to the engine with the strongest evidence that can run. When a server did not offer a request at its start, its engine declines, and the next engine of the language serves the call.
techne starts the server of a language at the first call that needs it, and keeps it running until
techne exits or closes the workspace. Later calls reuse the index of the running server. A server
that does not reply to initialize within 10 seconds declines each call until it replies, and the
next engine of the language serves the call.
A server analyses the buffers that it receives, not the files on disk. Before each call, techne sends the server each file that changed on disk since the server received it. It also sends the creations, changes and deletions of the files that the watchers of the server match. So an answer takes the edits of an editor or of another tool into account.
A call waits until the server has ended its progress jobs and has been idle for 300 milliseconds. An answer from a server that has not settled is partial. A server whose process exits is replaced at the next call.
The last line of every answer states its fidelity and its coverage, such as
resolved, total coverage.
syntactic means that a parser matched the
text. indexed means that an index resolved the name without a type checker. resolved means
that a type checker or a language server bound each name to its declaration.an empty answer here means there are none.A language server that binds names through types and still indexes the workspace returns
resolved, partial coverage. Its empty answer does not prove absence, and techne refuses a rename
on its evidence. With --structured, the JSON of a result contains the evidence as fidelity,
completeness and supportsNegativeClaim.
A write tool returns a preview unless the call sets dry_run to false. techne projects the change
over the files in memory and checks the projection before it writes anything. The preview contains
the rewritten lines, the engine that checked them and a handle. apply.change takes the handle and
writes every file of the change or none of them.
rename.symbol and move.file need resolved fidelity and total coverage, because a claim to
have found every reference is a claim that no other reference exists. Otherwise techne refuses
the change and states the reason.apply.change refuses a handle when a file of the change changed after the preview.techne serves one workspace per process. --trust DIR lets one process serve every project under
the folder DIR:
claude mcp add --scope user techne -- techne --trust ~/Projects
With a trusted folder, every tool takes the field wd. Its value is a directory under a trusted
folder, and a relative directory is relative to the workspace. A call with wd runs in the
workspace of that directory, and the paths of the call and of its answer are relative to it. A
call without wd runs in the workspace that techne serves. One session can then read a library
and the service that uses it, each in its own workspace.
wd outside the trusted folders. Trust only folders whose builds you would
run, because a language server runs the build of its project.apply.change refuses their handles.--trust repeats for more than one folder. techne expands a leading ~, because an editor
starts techne without a shell.techne [-h | --help] [--version] [--structured] [--trust DIR]... [workspace]
workspace is the root of the workspace, and the working directory when you omit it.--structured sends each result as JSON beside its text, and declares the output schema of
each tool.--trust DIR adds a trusted folder, and repeats for more than one folder.-h and --help write the usage to standard output and exit. --version writes the version
and exits.While techne serves a workspace, standard output contains the messages of the protocol alone.
Every diagnostic goes to standard error. techne exits with status 0 when the client closes
standard input and after SIGINT or SIGTERM. It exits with 1 for a workspace or a trusted folder
that it cannot serve, and with 2 for an unknown flag, a --trust that lacks a folder or a second
workspace.
By default a result contains its answer as text written for a model, and techne declares no
output schema. Claude Code passes the JSON of a result to the model when the result contains
JSON, and the text is about half its size. Pass --structured when your client validates or
processes the JSON.
The grammar of Go is the fork dokimasia/tree-sitter-go, which parses the type parameters of a method.
skills/techne/SKILL.md is a skill for Claude Code. It covers:
From a checkout of this repository, link the skill instead of a copy, so that it changes with the checkout:
ln -s "$PWD/skills/techne" ~/.claude/skills/techne
A project can also include the skill in its own .claude/skills/ directory.
techne starts the language server of a language at the first call about it. A server runs the
build of its project. rust-analyzer runs cargo check, and jdtls imports a Gradle or a Maven
build. Serve only a workspace whose build you would run.
Report a vulnerability by email to [email protected] and not in an issue. SECURITY.md describes what a report contains and which bugs to report privately.
The repository uses ergon for its checks and its releases. CONTRIBUTING.md describes the setup and how to propose a change. The project follows the Contributor Covenant 2.1.
make check # the gate: lint, tests, race detector and vulnerability scan of every module
make test # the tests of every module
make corpus # drive the binary over large repositories, hours on a first run
make help lists every target. To drive the tools without a language server, set
TECHNE_MOCK=1. techne then adds a mock language that serves every tool but extract.function
at the resolved tier.
Dokimasia B.V. licenses techne under the MIT license. See LICENSE.
An MCP server that gives AI agents the code navigation and refactorings of an IDE in ten languages, and states the evidence behind every answer
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Techne 透過 stdio 在本機執行。
上次檢查時間:2026-10-28。 An MCP server that gives AI agents the code navigation and refactorings of an IDE in ten languages, and states the evidence behind every answer