mcpField
F
flyto-indexer

flyto-indexer

Local
github.com/flytohubDeveloper Tools
Repository

About flyto-indexer

flyto-indexer is a local code-intelligence MCP server and CLI for coding agents working in existing repositories. It maps change impact, carries repository requirements into a task, and verifies evidence before work is considered complete.

Key features

  1. 01Local code and dependency indexing
  2. 02Transitive and cross-project impact analysis
  3. 03Task plans linked to rules and requirements
  4. 04Repository, security, and quality verification
  5. 05CLI and MCP access

Use cases

  1. 01Assess callers and tests before a refactor
  2. 02Check requirements against changed files
  3. 03Verify repository readiness before merging

MCP support

Exposes search, impact, task, audit, and structure tools to MCP clients. Setup can configure supported clients, and task state can be resumed by another client.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "chesterhsu-flyto-indexer": {
      "command": "uvx",
      "args": [
        "flyto-indexer"
      ]
    }
  }
}
Run commanduvx flyto-indexer

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiflyto-indexer1.0.2

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.