MCP · cross-repo · self-hosted

comindly indexes a team's repositories into one versioned graph in your own storage and serves it to agents over MCP: who breaks if this changes, which services call this route, and what the team already learned the hard way about this code.

Get started GitHub
curl -LsSf https://raw.githubusercontent.com/sayef/comindly/main/scripts/install.sh | sh
comindly showing create_order in an example shop: its callers across repositories, blast radius and flow walkthrough comindly showing create_order in an example shop: its callers across repositories, blast radius and flow walkthrough
6 languagesPython, TypeScript/JS, Go, Java, Kotlin, Rust
1 binaryCLI, MCP server, web UI and desktop app
0 serversa folder or your own bucket holds the index
~0.2 ssearch against an index in S3

The org map of an example shop: five repositories and the service contracts between them The org map of an example shop: five repositories and the service contracts between them

The org map of an example shop: five repositories in three languages, linked by HTTP routes, an SNS topic and an SQS queue.

  • Deterministic, cross-repo graph

    Calls, imports, inheritance and instantiation from tree-sitter (and SCIP where available) for Python, TypeScript/JavaScript, Go, Java, Kotlin and Rust, linked across repositories.

    Concepts

  • Service contracts

    HTTP routes and clients, queues, topics, buckets and SQL tables, from code, YAML config and Terraform, so blast radius crosses service boundaries.

    Service contracts

  • A reasoning ledger

    Decisions, failed attempts and constraints anchored to symbols. They follow the code, go stale when it changes, and reach agents only when trusted.

    The ledger

  • For people too

    A local web UI with the org map, dependency graphs, contracts, internal packages, conventions and ledger review, and a guide to connecting your agent.

    Desktop, web and terminal UI

  • Your storage, one binary

    A local directory or your own bucket holds everything. No server to run; CI builds a new version, every agent reads it.

    Team setup