mayankmahavar1mg/mcp

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/mayankmahavar1mg-mcp

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

8 read · 6 write · 0 delete · 1 not yet classified

Secrets

1 (API keys, tokens or passwords)

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (15)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• check_config

  Use when the developer asks: 'is my config correct?', 'check my WEBVIEW_CONFIG', 'validate my setup', 'what's wrong with my config?'. Reads WEBVIEW_CONFIG from the project and validates required fields for both platforms.

• close_task_plan

  Use when the developer says: 'close the task', 'I am done', 'mark plan complete', 'finish the task', 'clean up the task file'. All steps must be terminal (done/skipped/blocked) before closing. Asks the developer whether to delete the task MD file. If delete_file:true, deletes .mcp_tasks/<slug>.md and removes the DB record. If delete_file:false (default), keeps the file for review and marks it done.

• create_github_issue

  Use when the developer wants to create, raise, report, preview, or publish a GitHub issue for catalyst-core, or after the LLM discovers that a problem is likely caused by catalyst-core framework behavior and the developer agrees to raise an issue. This single tool first asks the developer to select labels when labels are omitted. After labels are supplied, it gathers project context, renders the issue using the selected/suggested template, searches duplicates using duplicate_search_query when provided, supports preview with dry_run:true, publishes only when dry_run:false is explicitly passed, …

• create_github_pr

  Use when the developer wants to open, raise, create, or publish a GitHub pull request for catalyst-core. Resolves the head branch from the current git checkout (or the head arg), renders the PR body in the shape of the matching .github/PULL_REQUEST_TEMPLATE (fix / feature / chore) from the structured fields, appends the shared checklist, and previews with dry_run:true. Publishes via the GitHub API only when dry_run:false is explicitly passed, and only if the head branch is already pushed to origin (it does not push for you). Default to dry_run:true first. Intent: feedback.

• create_task_plan

  Use when the developer wants to DO something — 'help me convert this app', 'plan out the migration', 'I want to add camera support', 'guide me through implementing X'. Intent: execute. Creates a step-by-step plan persisted in DB — survives context resets.

• debug_issue

  Use when the developer reports an error, something is broken, or asks 'why is X not working?'. Matches the symptom against known_errors in the DB and returns cause + fix. Also queries relevant framework_knowledge rows by layer.

• explain_error

  Use when the developer has a specific catalyst-core error code (e.g. 'PREFLIGHT-001', 'BUNDLE-000') and wants to know what it means and how to fix it. Looks it up against the generated errors/ registry. If the code isn't catalyst-owned (e.g. a raw Vite/Rollup/Gradle/Xcode code), says so rather than guessing — those are not reinterpreted.

• get_active_task

  Use when the developer asks: 'what was I doing?', 'where did I leave off?', 'resume my task', 'what is the current step?', 'show me my plan'. Returns current active plan with pending steps and progress. Call this at the start of any session to restore context.

• get_architecture_diagram

  Use when the developer asks how something works architecturally — e.g. 'how does the universal app work?', 'explain the bridge', 'show me request lifecycle', 'how does routing work?', 'what part of the config controls X?', 'show me the build pipeline'. Returns a layered a→b→c flow diagram with project-specific context and known pitfalls.

• get_build_flow

  Use when the developer asks about building, serving, or deploying. Returns version-aware flows: webpack-era behavior for Catalyst 0.2.x and Vite client/server behavior for Catalyst 0.3.x+, plus project config warnings and related known errors.

• get_conversion_status

  Use when the developer asks: 'how far along am I?', 'what have I completed?', 'show my conversion progress', or 'what's done vs pending?'. Reports the detected Catalyst generation so 0.2.x and 0.3.x requirements are never mixed.

• get_conversion_tasks

  Use when the developer asks: 'what do I need to convert?', 'what's left to do?', 'show me pending tasks', 'what do I fix next?', or asks to migrate between Catalyst versions. Detects the installed catalyst-core generation and keeps legacy 0.2.x webpack/router guidance separate from current 0.3.x Vite/integrated-router guidance.

• query_knowledge

  Use when the developer asks ANY question about Catalyst — how-to, conceptual, debugging, or setup. Examples: 'how do I add meta tags?', 'how does routing work?', 'what hooks are available?', 'how do I set the page title?', 'explain the bridge', 'list all native hooks', 'how does getDeviceInfo work', 'how do I add SEO?', 'how do I use setMetaData?'. Intent: guidance. CRITICAL: Before calling, expand the user's plain-English terms into Catalyst-specific technical keywords. Examples: 'meta tags' → ['setMetaData', 'metaTags', 'Head', 'seo']; 'page title' → ['setMetaData', 'title', 'meta']; 'SEO' →…

• sync_knowledge_base

  Use when the developer asks: 'sync docs', 'update framework knowledge', 'fetch latest catalyst docs'. Intent: sync. Pulls the latest knowledge-base.json from tata1mg/catalyst-core@main and re-seeds the KB. Maintenance only — no task planning needed after.

• update_task_step

  Use when the developer says: 'mark step X done', 'I finished step 2', 'this step is blocked', 'move to next step', 'add a note to step 1'. Updates the active plan in DB and auto-advances to the next step.

Signals

Stars

92

Forks

29

Open issues

76

Contributors

13

Last commit (this folder)

Oct 22, 2026 (7 days ago)

Last release

Oct 22, 2026 (7 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.mayankmahavar1mg/mcp

Version

1.0.2

Auth

API key

Packages

npm catalyst-mcp

License

MIT

Repository

github.com/tata1mg/catalyst-core

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql