OmniGlyph
Give agents local Unicode ground truth and code-symbol linting so UI copy, identifiers, and docs do not ship ambiguous or wrong characters.
Overview
OmniGlyph is a MCP server for the Ship phase that provides local Unicode lookup and code-symbol linting for AI-assisted code review.
What is this MCP server?
- PyPI omniglyph package (0.3.2-beta / 0.3.2b0) with stdio MCP under title OmniGlyph
- Local symbol ground truth for Unicode lookup without cloud glyph APIs
- Code-symbol linting to flag misleading or inconsistent characters in source
- Runs fully local—suitable for air-gapped or privacy-sensitive repos
- GitHub source at github.com/aidi1723/OmniGlyph
- MCP catalog version 0.3.2-beta with PyPI release 0.3.2b0
- stdio transport via PyPI identifier omniglyph
- Repository github.com/aidi1723/OmniGlyph
Community signal: 2 GitHub stars.
What problem does it solve?
Agents and fast commits introduce subtle Unicode mistakes—lookalike characters and wrong symbols—that slip past normal diff review.
Who is it for?
Indie builders with i18n-heavy frontends or docs who want a private, agent-driven Unicode linter in the review loop.
Skip if: Teams with zero Unicode-sensitive surfaces or those needing cloud icon search and brand asset management only.
What do I get? / Deliverables
After you add the local stdio server, the agent can query glyph ground truth and run symbol lints so risky characters are caught before ship.
- Local Unicode symbol lookups usable inside agent review sessions
- Code-symbol lint findings for risky or ambiguous characters
- Fewer production issues from mojibake and lookalike punctuation in shipped text
Recommended MCP Servers
Journey fit
Symbol correctness is enforced before release when reviewers catch mojibake, homoglyphs, and inconsistent punctuation that hurt trust and accessibility. Review is the canonical shelf because OmniGlyph is a ground-truth checker and linter MCP, not a feature generator or deploy connector.
How it compares
Local Unicode lint MCP for review, not a design Figma plugin or general ESLint replacement.
Common Questions / FAQ
Who is OmniGlyph for?
It is for solo builders and small teams using MCP agents on codebases where Unicode accuracy in strings, identifiers, and docs matters before release.
When should I use OmniGlyph?
Use it during ship and review when polishing UI copy, localization files, or public docs and you want local symbol verification without external APIs.
How do I add OmniGlyph to my agent?
Install the PyPI package omniglyph, configure the stdio OmniGlyph MCP server in Claude Code or Cursor per the OmniGlyph GitHub README, and invoke lookup or lint tools in your review workflow.