glyph

Created By
benmylesa year ago
🔮 glyph – mcp server to map your codebase with symbol outlines
Overview

What is glyph?

Glyph is a Model Context Protocol (MCP) server designed to extract symbol outlines from your codebase using Tree-sitter's declarative query language, providing LLM coding agents with the necessary context for efficient coding.

How to use glyph?

To use glyph, install it via Go, and run it either as an MCP server for integration with AI coding assistants or as a standalone CLI tool to extract symbols from your codebase.

Key features of glyph?

  • Declarative query-based extraction using Tree-sitter
  • Glob-based file discovery for easy code file matching
  • Language-agnostic architecture for adding new languages
  • Configurable detail levels for symbol extraction
  • Multi-file support for unified project views
  • High performance with optimized queries

Use cases of glyph?

  1. Assisting AI coding agents in understanding code structure.
  2. Extracting symbol outlines for various programming languages.
  3. Enhancing code navigation and comprehension in large codebases.

FAQ from glyph?

  • What languages does glyph support?
    Glyph supports Go, Java, JavaScript/TypeScript, and Python, with easy extensibility for new languages.

  • Is glyph free to use?
    Yes, glyph is open-source and available for free.

  • How does glyph improve LLM coding agents?
    By providing clean, efficient symbol maps, glyph helps LLM coding agents understand the structure of the code better, leading to improved coding assistance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
benmyles
Star
0
Language
Go
License
MIT license

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
Crevio

2 days ago