Scout Code

Inspiration

Cursor is great(ofcourse we hacked our way till now with the saviour) but every time we work across repos, providing context is a huge hurdle. Either cursor will not catch a foreign repo, or it will execute a long list of commands and greps just to find the repo. The result? slower performance, and off the charts Cursor bills! We address exactly that.

What it does

Scout Code is a CLI tool that incrementally indexes your codebase in real time, and serves it to coding agents via a MCP Server. Let's say you have a complete backend repo, you want to make a frontend around the APIs, our MCP will provide API, schema and model context in a fraction of time (AND yes with lesser tokens used as well)!

How we built it

1.⁠ ⁠We have CLI indexer tool that can pointed to any repo, this will incrementally index any codebase in small chunks (in real-time) 2.⁠ ⁠User generates a Scout Code API key from the web with a single click(or you may say, a tab). 3.⁠ ⁠Using this key along with CLI we serve your codebase over an MCP. 4.⁠ ⁠Add our MCP to an AI agent (like Cursor) and get context served for any foreign repo in fraction of the time!

Challenges we ran into

•⁠ ⁠We used cocoindex a python library for codebase indexing but had our CLI tool built in TypeScript. As a result we had to execute some chunks of Python code from TypeScript. While this sounds an easy fix, it took a good share of our sanity while debugging. •⁠ ⁠When you publish and npm package and call the package from your CLI, it resolves for local tool first then the remote one - took us 2 hours to figure out. •⁠ ⁠We provide documentations indexed like codebases. Most of the tools which help us build that are MCPs. Calling an MCP from another MCP is an add on latency and MCP server-server calls are not practical, instead we had to default to a custom API that crawls and indexes the web for you.

Accomplishments that we're proud of

•⁠ ⁠We've deployed every code of line we've written. It's not some repos lying on our local machine, the world can see what we've built. •⁠ ⁠This is an actual problem that is solved, even if not for hackathon, I will be using this tool personally (I hope fellow programmers do as well)