@symbo.ls/mcp 1.0.0 → 1.0.5

package/.env.example

@@ -1,16 +0,0 @@
-# OPTION 1: Use public MCP server (no API key needed - easiest for users)
-# Contact the maintainer for the public server URL
-SYMBOLS_MCP_URL=your_mcp_server_url_here
-
-# OPTION 2: Use your own OpenRouter API key (for advanced users)
-# OPENROUTER_API_KEY=your_openrouter_api_key_here
-
-# Optional — Supabase for vector search (falls back to local skills search if not set)
-# SUPABASE_URL=your_supabase_url_here
-# SUPABASE_KEY=your_supabase_key_here
-
-# Optional — AI model to use (default: openai/gpt-4.1-mini)
-# LLM_MODEL=openai/gpt-4.1-mini
-
-# Optional — Path to skills directory (defaults to bundled skills)
-# SYMBOLS_SKILLS_DIR=C:\repos\symbols\skills

package/.env.railway

@@ -1,13 +0,0 @@
-# Railway Environment Variables
-RAILWAY_ENVIRONMENT=production
-PORT=8080
-
-# Required — OpenRouter API key (add in Railway dashboard)
-OPENROUTER_API_KEY=your_openrouter_api_key_here
-
-# Optional — Supabase for vector search (add in Railway dashboard)
-SUPABASE_URL=your_supabase_url_here
-SUPABASE_KEY=your_supabase_key_here
-
-# Optional — AI model (add in Railway dashboard)
-LLM_MODEL=openai/gpt-5.2-codex

package/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026 baronsilver
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

package/mcp.json

@@ -1,57 +0,0 @@
-{
-  "name": "symbols-mcp",
-  "version": "1.0.0",
-  "description": "AI-powered assistant for the Symbols design-system framework. Generates DOMQL v3 components, pages, and full projects; converts React/Angular/Vue code to Symbols; searches Symbols documentation; and provides comprehensive framework reference.",
-  "author": "baronsilver",
-  "license": "MIT",
-  "homepage": "https://github.com/baronsilver/symbols-mcp-server",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/baronsilver/symbols-mcp-server.git"
-  },
-  "capabilities": {
-    "tools": [
-      {
-        "name": "generate_component",
-        "description": "Generate a Symbols/DOMQL v3 component from a natural-language description"
-      },
-      {
-        "name": "generate_page",
-        "description": "Generate a Symbols/DOMQL v3 page with routing support"
-      },
-      {
-        "name": "generate_project",
-        "description": "Generate a complete multi-file Symbols/DOMQL v3 project structure"
-      },
-      {
-        "name": "convert_to_symbols",
-        "description": "Convert React, Angular, Vue, or HTML code to Symbols/DOMQL v3 format"
-      },
-      {
-        "name": "search_symbols_docs",
-        "description": "Search the Symbols documentation knowledge base for relevant information"
-      },
-      {
-        "name": "explain_symbols_concept",
-        "description": "Explain a Symbols/DOMQL concept with examples (state, routing, events, design tokens, etc.)"
-      },
-      {
-        "name": "review_symbols_code",
-        "description": "Review Symbols/DOMQL code for correctness, best practices, and v3 compliance"
-      },
-      {
-        "name": "create_design_system",
-        "description": "Generate Symbols design system files (colors, spacing, typography, theme, icons)"
-      }
-    ],
-    "resources": 9,
-    "prompts": 4
-  },
-  "installation": {
-    "command": "python",
-    "args": ["-m", "uv", "run", "--directory", "{INSTALL_DIR}", "symbols-mcp"],
-    "env": {
-      "OPENROUTER_API_KEY": "required"
-    }
-  }
-}

package/railway.toml

@@ -1,26 +0,0 @@
-[build]
-builder = "NIXPACKS"
-nixpacksPlan = { providers = ["python"] }
-
-[deploy]
-startCommand = "python -m symbols_mcp.server"
-healthcheckPath = "/health"
-healthcheckTimeout = 100
-restartPolicyType = "ON_FAILURE"
-restartPolicyMaxRetries = 10
-
-[[services]]
-name = "symbols-mcp"
-source = "."
-
-[services.variables]
-PORT = "8080"
-PYTHON_VERSION = "3.11"
-RAILWAY_ENVIRONMENT = "production"
-
-# Environment variables should be set in Railway dashboard
-# Do not reference them here to avoid secret detection
-
-[[services.ports]]
-port = 8080
-protocol = "HTTP"

package/run.sh

@@ -1,17 +0,0 @@
-#!/bin/bash
-# Wrapper script for running symbols-mcp server
-
-# Check if Python is available
-if ! command -v python &> /dev/null; then
-    echo "Error: Python is not installed"
-    exit 1
-fi
-
-# Check if uv is available
-if ! command -v uv &> /dev/null; then
-    echo "Installing uv..."
-    pip install uv
-fi
-
-# Run the MCP server
-exec python -m uv run symbols-mcp

package/symbols_mcp/skills/GARY_TAN.md

@@ -1,80 +0,0 @@
-# Claude Code Prompt for Plan Mode
-
-_February 4, 2026_
-
-#prompts
-
-Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction.
-
-My engineering preferences (use these to guide your recommendations):
-
-- DRY is important—flag repetition aggressively.
-- Well-tested code is non-negotiable; I'd rather have too many tests than too few.
-- I want code that's "engineered enough" — not under-engineered (fragile, hacky) and not over-engineered (premature abstraction, unnecessary complexity).
-- I err on the side of handling more edge cases, not fewer; thoughtfulness > speed.
-- Bias toward explicit over clever.
-
-## 1. Architecture review
-
-Evaluate:
-
-- Overall system design and component boundaries.
-- Dependency graph and coupling concerns.
-- Data flow patterns and potential bottlenecks.
-- Scaling characteristics and single points of failure.
-- Security architecture (auth, data access, API boundaries).
-
-## 2. Code quality review
-
-Evaluate:
-
-- Code organization and module structure.
-- DRY violations—be aggressive here.
-- Error handling patterns and missing edge cases (call these out explicitly).
-- Technical debt hotspots.
-- Areas that are over-engineered or under-engineered relative to my preferences.
-
-## 3. Test review
-
-Evaluate:
-
-- Test coverage gaps (unit, integration, e2e).
-- Test quality and assertion strength.
-- Missing edge case coverage—be thorough.
-- Untested failure modes and error paths.
-
-## 4. Performance review
-
-Evaluate:
-
-- N+1 queries and database access patterns.
-- Memory-usage concerns.
-- Caching opportunities.
-- Slow or high-complexity code paths.
-
-## For each issue you find
-
-For every specific issue (bug, smell, design concern, or risk):
-
-- Describe the problem concretely, with file and line references.
-- Present 2-3 options, including "do nothing" where that's reasonable.
-- For each option, specify: implementation effort, risk, impact on other code, and maintenance burden.
-- Give me your recommended option and why, mapped to my preferences above.
-- Then explicitly ask whether I agree or want to choose a different direction before proceeding.
-
-## Workflow and interaction
-
-- Do not assume my priorities on timeline or scale.
-- After each section, pause and ask for my feedback before moving on.
-
----
-
-BEFORE YOU START:
-
-Ask if I want one of two options:
-
-1/ BIG CHANGE: Work through this interactively, one section at a time (Architecture → Code Quality → Tests → Performance) with at most 4 top issues in each section.
-
-2/ SMALL CHANGE: Work through interactively ONE question per review section
-
-FOR EACH STAGE OF REVIEW: output the explanation and pros and cons of each stage's questions AND your opinionated recommendation and why, and then use AskUserQuestion. Also NUMBER issues and then give LETTERS for options and when using AskUserQuestion make sure each option clearly labels the issue NUMBER and option LETTER so the user doesn't get confused. Make the recommended option always the 1st option.

package/windsurf-mcp-config.json

@@ -1,18 +0,0 @@
-{
-  "mcpServers": {
-    "symbols-mcp": {
-      "command": "python",
-      "args": [
-        "-m",
-        "uv",
-        "run",
-        "--directory",
-        "C:\\repos\\symbols-mcp-server",
-        "symbols-mcp"
-      ],
-      "env": {
-        "OPENROUTER_API_KEY": "YOUR_KEY_HERE"
-      }
-    }
-  }
-}