TSG Indexer

Created By
entrepeneur4lyfa year ago
A library for indexing code repositories using Tree-sitter Stack Graphs, designed to be used in MCP servers and other tools.
Overview

what is TSG Indexer?

TSG Indexer is a Rust library designed for indexing code repositories using Tree-sitter Stack Graphs, enabling powerful code navigation and analysis capabilities.

how to use TSG Indexer?

To use TSG Indexer, add it as a dependency in your Cargo.toml or clone the repository and build it. You can then use the library's API or the command-line interface (CLI) to index code.

key features of TSG Indexer?

  • Supports 20+ programming languages including Rust, Python, JavaScript, and more.
  • Recursive directory traversal for comprehensive codebase analysis.
  • Multiple output formats (JSON, DOT graph).
  • Optional CLI and LSP support via feature flags.
  • Ability to generate TSG files for unsupported languages.

use cases of TSG Indexer?

  1. Analyzing large codebases for better navigation.
  2. Integrating with Model Control Protocol (MCP) servers for enhanced code indexing.
  3. Generating visual representations of code structure for documentation.

FAQ from TSG Indexer?

  • What programming languages does TSG Indexer support?

TSG Indexer supports over 20 languages including Rust, Python, JavaScript, and more.

  • How can I install TSG Indexer?

You can add it to your Cargo.toml or clone the repository and build it using Cargo.

  • Can I use TSG Indexer with MCP servers?

Yes, TSG Indexer is designed to be integrated with MCP servers for code indexing and navigation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
entrepeneur4lyf
Star
0
Language
Rust
License
Activity

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago