MCP Tools Reference

The Thruline tools available to your AI editor over MCP, with their parameters.

Your editor calls these tools automatically, but you can also request one by name. Authentication is handled by your editor on first connect (see Set-Up).

thruline_index

Index a repository. In remote mode, Thruline reads the repository from GitHub. Commit and push before indexing, since local uncommitted files aren't visible.

ParameterRequiredDescription
repo_pathNoGitHub repository in owner/repo form (for example, FixateIndustries/thruline).
incrementalNoIf true, only process changes since the last indexed commit. Defaults to false (full index).
repo_idNoExisting Thruline repository ID. If omitted, Thruline creates a new record or finds the existing one by name.

See Indexing for how full and incremental indexes differ.

thruline_review

Return Thruline's knowledge for a single file: its domain patterns, segment conventions, file summaries, API surfaces, connection weights, and git history. Your editor uses this context to review the file.

ParameterRequiredDescription
file_pathYesRelative path to the file within the repository.
repo_idNoThruline repository ID. Auto-detected if omitted.
repo_nameNoRepository name, used to auto-resolve in remote mode.

thruline_review_changeset

Review a set of changed files together and surface what the repository's history says should also change:

ParameterRequiredDescription
file_pathsNoFile paths to review. If omitted, Thruline auto-detects the changed files.
repo_idNoThruline repository ID. Auto-detected if omitted.
repo_nameNoRepository name, used to auto-resolve in remote mode.

thruline_get_domains

List all domains discovered for a repository, both repository-scoped and activated global domains, with their patterns, file counts, and languages.

ParameterRequiredDescription
repo_idNoThruline repository ID. Auto-detected if omitted.
repo_nameNoRepository name, used to auto-resolve in remote mode.

thruline_get_segments

List the code segments (cohesive groups of related files) with their conventions, file summaries, and API surfaces.

ParameterRequiredDescription
repo_idNoThruline repository ID. Auto-detected if omitted.
repo_nameNoRepository name, used to auto-resolve in remote mode.

thruline_get_network

Return the domain connection graph, with the learned weights that indicate how strongly two domains are coupled. See Domain Connections.

ParameterRequiredDescription
repo_idNoThruline repository ID. Auto-detected if omitted.
repo_nameNoRepository name, used to auto-resolve in remote mode.

thruline_get_findings

Return the history of commits and domain activity for a repository — which domains are most active, change velocity, and commit patterns.

ParameterRequiredDescription
repo_idNoThruline repository ID. Auto-detected if omitted.
repo_nameNoRepository name, used to auto-resolve in remote mode.

thruline_report_findings

Report the findings from a review back to Thruline. Tagging each finding with a domain lets Thruline learn which connections are valuable. See Domain Connections.

ParameterRequiredDescription
file_pathYesRelative path to the file that was reviewed.
findingsYesAn array of findings. Each has severity (error, warning, or info) and message, and optionally domain and line.
repo_idNoThruline repository ID. Auto-detected if omitted.
repo_nameNoRepository name, used to auto-resolve in remote mode.

thruline_similar_files

Find files semantically similar to a given file, scoped to the repository and any cross-repository inclusions configured for it. Use it to find an existing implementation of a pattern before writing a new one, or to check whether a fix should also be applied elsewhere.

ParameterRequiredDescription
file_pathYesRelative path to the file to find similar code for.
limitNoMaximum number of results. Defaults to 20, capped at 100.
repo_idNoThruline repository ID. Auto-detected if omitted.
repo_nameNoRepository name, used to auto-resolve in remote mode.