can we make this MCP TFS compatible as well, I see the current indexing and cache refresh is based on the git commits history alone only.

[saikrishnabb]

[bbajt]

Hi @saikrishnabb!

Another good question, and you've read the design correctly: indexing and cache invalidation are anchored on git commit history. That's not incidental, it's fairly deep in the architecture:

• Every baseline is stored under store//baselines//, keyed by the commit SHA.
• Incremental updates (the workspace overlay) work by diffing your working tree against that baseline commit.
• Cache reuse across machines keys on the same commit identity.

So native TFVC/TFS support isn't a small adapter, it would mean a second versioning provider that supplies changeset identity and diffs in place of git throughout that pipeline. It's a legitimate ask, but it's a substantial piece of work and it's not currently on the roadmap. I'd rather be straight with you than leave it open-ended.

The practical path today is the git init workaround from your question/issue #3, a local git repo with no remote is a first-class supported mode, so you can keep TFS as your real source control and use a throwaway local .git purely as scaffolding for the index. For most people that closes the gap entirely without waiting on native support. It works.

I'll leave this open as the tracking issue for native TFVC support so anyone else wanting it can chime in. The more demand it gets, the more it earns a spot on the roadmap. Thanks for taking the time to file it clearly.