Hindsight MCP

io.github.RbfinchPublished by GitHub account Rbfinchv0.1.5Updated Oct 27, 2026

MCP server for AI-assisted coding with development history: git, tests, Copilot.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server that indexes git commits, test results and GitHub Copilot sessions into SQLite so an assistant can search and summarize your development…

What you can do
  • Search commits and Copilot chat messages with full-text queries
  • View a chronological timeline of commits and test runs, filtered by workspace
  • Inspect test failures and per-commit details, including linked test outcomes
  • Summarize activity over a chosen number of days
  • Refresh the local database by ingesting git, Copilot or all sources
When to use it
Useful when you want an assistant in VS Code to answer questions about your own project history — what you worked on recently, which commits touched a topic, or which tests are failing — without manually digging through git logs and chat sessions.
Requirements
Runs as a local binary (installed via cargo or a platform archive) over stdio; needs VS Code 1.99+ with GitHub Copilot for the documented setup, and cargo-nextest for test ingestion. Data is stored in a local SQLite database whose path can be set with HINDSIGHT_DATABASE; HINDSIGHT_WORKSPACE sets the default workspace.
Before you install
It reads and stores your Copilot chat sessions, including prompts, responses and attached files, plus commit and test-failure output in a local database — review where that database lives and who can access it. The ingest tool writes to that database, and the test command runs cargo nextest in your workspace.

Installation

In SourceWeft

  1. Open Hindsight MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Hindsight Logo]

hindsight-mcp

An MCP server for AI-assisted coding that leverages development history.

Overview

hindsight-mcp consolidates development data (git logs, test results, and GitHub Copilot sessions) into a searchable SQLite database, making it accessible to AI assistants through MCP tool calls in VS Code.

Key Features:

  • Full-text search across commits and Copilot conversations
  • Track test results linked to specific commits
  • Activity summaries and timeline views
  • Automatic git and Copilot session ingestion

Quick Start

Prerequisites

  • VS Code v1.99+ with GitHub Copilot
  • cargo-nextest (for test ingestion): cargo install cargo-nextest

Installation

bash
cargo install hindsight-mcp

Configure VS Code

Create .vscode/mcp.json in your project:

json
{  "servers": {    "hindsight": {      "type": "stdio",      "command": "hindsight-mcp",      "args": ["--workspace", "${workspaceFolder}"]    }  }}

Verify Setup

  1. Open VS Code Command Palette (Cmd+Shift+P)
  2. Run "MCP: List Servers"
  3. Confirm hindsight is listed
  4. In Copilot Chat, switch to Agent mode
  5. Ask: "What have I been working on recently?"

That's it! Copilot will use hindsight tools to answer questions about your development history.

MCP Tools

ToolPurposeExample Prompt
hindsight_timelineChronological activity view"Show recent commits and test runs"
hindsight_searchFull-text search"Find commits about authentication"
hindsight_failing_testsQuery test failures"What tests are failing?"
hindsight_activity_summaryAggregate stats"Summarise my week"
hindsight_commit_detailsCommit info with tests"Details for commit abc123"
hindsight_ingestTrigger data refresh"Refresh development history"
Tool Arguments Reference

hindsight_timeline

  • limit (int): Max events, default 50
  • workspace (string): Filter by path

hindsight_search

  • query (string): Search query (required)
  • source (string): "all", "commits", or "messages"
  • limit (int): Max results, default 20

hindsight_failing_tests

  • limit (int): Max tests, default 50
  • workspace (string): Filter by path
  • commit (string): Filter by SHA

hindsight_activity_summary

  • days (int): Days to summarise, default 7

hindsight_commit_details

  • sha (string): Commit SHA (required)

hindsight_ingest

  • workspace (string): Path to ingest (required)
  • source (string): "git", "copilot", or "all"
  • incremental (bool): Only new data, default true
  • limit (int): Max items

Test Ingestion

Run tests and automatically ingest results:

bash
# Run all tests and ingesthindsight-mcp test
# Test specific packagehindsight-mcp test -p my-crate
# Preview without writing to databasehindsight-mcp test --dry-run

The test command automatically:

  • Spawns cargo nextest with correct flags
  • Auto-detects the current git commit
  • Ingests results to the database
CI / Advanced Usage

For CI pipelines or custom nextest invocations:

bash
# Using stdin modeNEXTEST_EXPERIMENTAL_LIBTEST_JSON=1 cargo nextest run \  --message-format libtest-json 2>/dev/null | \  hindsight-mcp test --stdin
# Using ingest command with explicit commitNEXTEST_EXPERIMENTAL_LIBTEST_JSON=1 cargo nextest run \  --message-format libtest-json 2>/dev/null | \  hindsight-mcp ingest --tests --commit $(git rev-parse HEAD)

Data Sources

SourceData Collected
GitCommits (SHA, author, message, timestamp, parents)
TestsRun metadata, outcomes, durations, failure output
CopilotChat sessions, prompts, responses, attached files

Git and Copilot data are ingested automatically. Test results require running hindsight-mcp test.

CLI Reference

hindsight-mcp [OPTIONS] [COMMAND]
Commands:  ingest    Ingest data from various sources  test      Run tests and ingest results
Options:  -d, --database <PATH>   Database path [default: ~/.hindsight/hindsight.db]  -w, --workspace <PATH>  Workspace path [default: current directory]  -v, --verbose           Debug logging  -q, --quiet             Errors only      --skip-init         Skip database init  -h, --help              Print help  -V, --version           Print version
Test Subcommand Options 
hindsight-mcp test [OPTIONS] [-- <NEXTEST_ARGS>...]
Options:  -p, --package <PKG>     Package(s) to test      --bin <BIN>         Binary(ies) to run  -E, --filter <EXPR>     Filter expression      --stdin             Read from stdin      --dry-run           Preview only      --no-commit         Do not link to commit      --commit <SHA>      Explicit commit SHA      --show-output       Show test output

Environment Variables

VariableDescription
HINDSIGHT_DATABASEDatabase path
HINDSIGHT_WORKSPACEDefault workspace

Database Location

PlatformDefault Path
macOS~/Library/Application Support/hindsight/hindsight.db
Linux~/.local/share/hindsight/hindsight.db
Windows%LOCALAPPDATA%\hindsight\hindsight.db

Troubleshooting

ProblemSolution
Server does not startCheck binary path; run with --verbose
No data showingRun hindsight_ingest tool via Copilot
Log interferenceUse --quiet in production

Development

Building from Source
bash
git clone https://github.com/Rbfinch/hindsight-mcp.gitcd hindsight-mcpcargo build --release
Running Tests
bash
cargo install cargo-nextestcargo nextest run --workspace
Workspace Structure 
hindsight/├── crates/│   ├── hindsight-mcp/      # MCP server binary│   ├── hindsight-git/      # Git log processing│   ├── hindsight-tests/    # Test result processing│   └── hindsight-copilot/  # Copilot session parsing
Fuzzing
bash
cd crates/hindsight-testscargo +nightly fuzz run fuzz_nextest_run
cd crates/hindsight-copilotcargo +nightly fuzz run fuzz_session_json

License

MIT

Source: README.md at commit dab92d5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts