Log inSubmit server
Symbols MCP logo

Symbols MCP

Connects AI coding assistants to Symbols.app for documentation, DOMQL generation, audits, project management, publishing, and deployment.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Symbols MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "symbols-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@symbo.ls/mcp"
      ],
      "env": {
        "FRANK_AUDIT_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 18 tools correctly (Today).

Overview

Symbols MCP MCP server connects AI coding assistants with Symbols.app documentation, code generation, conversion, auditing, and project workflows. It exposes MCP tools for inspecting a local Symbols project, retrieving framework and SDK guidance, generating DOMQL, converting React or HTML, and checking components. Authenticated tools can create, update, publish, and deploy Symbols projects, while documentation tools work without an API key. Reach for it when working on the modern smbls stack or moving existing frontend code into Symbols DOMQL.

Use cases

  • Search Symbols framework documentation
  • Generate DOMQL components and pages
  • Convert React or HTML into Symbols DOMQL
  • Audit components and Symbols projects
  • Publish and deploy authenticated Symbols projects

Key features

  • Symbols documentation and CLI/SDK reference search
  • DOMQL component and page generation
  • React, HTML, and DOMQL-to-JSON conversion
  • Component and project auditing
  • Symbols project versioning and retrieval
  • Publishing and environment deployment

Tools18

What Symbols MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 46d

What it can do

From the 18 tools this server returned when we ran it.

Handles credentials · 1Makes network requests · 1Read-only tools · 18
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age244 days
Maintainers15

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · @symbo.ls/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads3kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed18Callable tools this server registers over MCP.

How Symbols MCP works

What Symbols MCP MCP server does

Symbols MCP MCP server exposes Symbols.app capabilities through Model Context Protocol tools. It covers two broad workflows: working with the Symbols framework and managing projects on the Symbols platform. Documentation search and reference tools provide material for the CLI, SDK, DOMQL syntax, framework conventions, project structure, components, design systems, migrations, and auditing.

For implementation work, the server can generate DOMQL components or complete pages. Page generation includes routing, helmet metadata, and declarative fetch: integration. Conversion tools accept React or JSX and raw HTML/CSS, then produce Symbols DOMQL. Generated DOMQL can be converted to platform JSON before it is saved to a project.

How it works

Start by calling get_project_context, which searches upward from the current working directory for symbols.json. Its result describes project ownership, the project key and directory, bundler details, shared libraries, rendering information, environment classification, and authentication state. It also returns guidance for the next action.

get_project_rules supplies the rules needed before generation. The default response is a compact core bundle; individual sections can be requested when more detail is needed. A client can then generate or convert code, run audit_component, convert the result to JSON, and use the project tools to store it. audit_project returns a multi-phase audit playbook, while the package also provides a command-line filesystem audit.

Setup and configuration

Documentation and reference tools do not require API keys. Project operations require a Symbols account, using the login tool or an API key. The login flow returns a JWT token. After authentication, use list_projects to select an existing project or create_project to start one. get_project reads current project data, and save_to_project creates a new version containing the submitted project changes.

The repository also documents a filesystem audit command: npx -y @symbo.ls/mcp symbols-audit <symbols-dir>. The audit is strict by default and exits with status 1 when it finds issues. FRANK_AUDIT_URL may be used by the audit compatibility layer to delegate to an HTTP audit endpoint.

Tools and capabilities

The Symbols MCP MCP server includes tools for documentation search, CLI and SDK references, environment detection, component and page generation, React and HTML conversion, JSON conversion, component validation, and project audits. Platform tools cover login, project listing and creation, project retrieval, saving, publishing, and deployment to production, staging, or development environments.

It also exposes Symbols skill and reference resources covering framework behavior, syntax, rules, components, migration, design, runtime options, and related topics. The documented target is the modern smbls stack, including signal-based reactivity, declarative fetching, routing, helmet metadata, theming, and server-side rendering.

Limitations and notes

detect_environment is retained as a legacy caller-supplied variant; new code should prefer get_project_context. Some responses are large: generation returns bundled context, and the full rules response is intended for clients without tool-output limits only when explicitly requested. audit_component checks one component string, whereas filesystem-wide auditing uses the supplied CLI and the frank-audit engine. Project creation, saving, publishing, and deployment require authentication; documentation tools do not.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Symbols MCP

Symbols MCP is an MCP server that connects AI coding assistants to Symbols.app. Its main tools search documentation, generate DOMQL components and pages, convert React or HTML, audit code, and manage projects through saving, publishing, and deployment. Documentation tools need no API key, while project operations require Symbols authentication.

It documents the filesystem audit command `npx -y @symbo.ls/mcp symbols-audit <symbols-dir>` and identifies the repository as the source, but gives no supported installation procedure.

Yes, the README names Cursor as a supported AI coding assistant. It also names Claude Code and Windsurf, while describing the server generally as usable from MCP clients.

Project management tools require a Symbols account, using login or an API key. Documentation tools do not require API keys. The `login` tool returns a JWT token for authenticated project operations.

Use `audit_component` for an inline check of one component, or use `audit_project` to obtain the multi-phase audit playbook. For filesystem-wide checks, run `npx -y @symbo.ls/mcp symbols-audit <symbols-dir>`; the strict audit exits with status 1 when findings are present.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSymbols MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/symbols-mcp?style=directory)](https://allmcps.com/mcp/symbols-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/symbols-mcp"><img src="https://allmcps.com/api/badge/symbols-mcp?style=directory" alt="Symbols MCP on AllMCPs" /></a>