[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-85120":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":15,"stars30d":15,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":16,"rankGlobal":10,"rankLanguage":10,"license":17,"archived":18,"fork":18,"defaultBranch":19,"hasWiki":20,"hasPages":18,"topics":21,"createdAt":10,"pushedAt":10,"updatedAt":28,"readmeContent":29,"aiSummary":10,"trendingCount":15,"starSnapshotCount":15,"syncStatus":30,"lastSyncTime":31,"discoverSource":32},85120,"MCPify","amarnath3003\u002FMCPify","amarnath3003","MCPify is an AI enablement compiler that transforms existing applications into AI-native, agent-operable systems.","https:\u002F\u002Fmcpify.vercel.app",null,"TypeScript",55,4,1,0,38.1,"Other",false,"main",true,[22,23,24,25,26,27],"ai","ai-agents","hackathon","mcp","mcp-server","npm","2026-06-15 10:04:32","\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Flogo.png\" alt=\"MCPify\" width=\"720\" \u002F>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cstrong>Compile software into AI-operable systems.\u003C\u002Fstrong>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  MCPify is the AI Enablement Compiler. Transform applications, APIs, frontends, workflows, and databases into AI-native systems for autonomous agents.\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fmcpify-cli\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002Fmcpify-cli?color=FCD269\" alt=\"npm version\" \u002F>\n  \u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Famarnath3003\u002FMCPify\u002Factions\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fbuild-passing-FF8383?logo=github\" alt=\"build status\" \u002F>\n  \u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fmcpify-cli\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fdm\u002Fmcpify-cli?color=9A72DE\" alt=\"npm downloads\" \u002F>\n  \u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fmcpify-cli\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fnode\u002Fv\u002Fmcpify-cli?color=4FA2FB\" alt=\"node version\" \u002F>\n  \u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fmcpify-cli\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fl\u002Fmcpify-cli?color=8DE344\" alt=\"license\" \u002F>\n  \u003C\u002Fa>\n  \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Famarnath3003\u002FMCPify\u002Fstargazers\">\n    \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002Famarnath3003\u002FMCPify?color=FC9D59\" alt=\"stars\" \u002F>\n  \u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"#overview\">Overview\u003C\u002Fa> ·\n  \u003Ca href=\"#features\">Features\u003C\u002Fa> ·\n  \u003Ca href=\"#getting-started\">Getting Started\u003C\u002Fa> ·\n  \u003Ca href=\"#cli\">CLI\u003C\u002Fa> ·\n  \u003Ca href=\"#architecture\">Architecture\u003C\u002Fa>\n\u003C\u002Fp>\n\n---\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Fgithub.com\u002Famarnath3003\u002FMCPify\u002Fraw\u002Fmain\u002Fassets\u002Frecgif.gif\" \n       width=\"1080\" \n       alt=\"Demo recording\" \u002F>\n\u003C\u002Fp>\n\n---\n\n## Overview\n\n### Problem Statement\n\nModern software is built for humans, not agents. The useful actions are scattered across frontend interactions, backend services, APIs, databases, and workflows, which forces AI systems into brittle browser automation or hand-written MCP boilerplate.\n\n- manual MCP tool authoring for capabilities that already exist\n- brittle browser automation for UI interactions\n- raw endpoints instead of meaningful workflows\n- permission and safety gaps at the tool boundary\n- schema and tool drift as the application changes\n\n### Solution\n\nMCPify acts as a compiler for your application. It scans the parts of the codebase that matter to agents and produces a runnable MCP server, semantic workflows, permission-aware tools, and the metadata an agent needs to use them safely.\n\nStop hand-writing MCP tools. Compile your stack once. Stay in sync forever.\n\n### Codex Usage\n\nCodex is a natural fit for MCPify in a few ways:\n\n1. **Ideate** - use Codex to explore agent workflows, sketch MCP surfaces, and refine how a product should be exposed to AI.\n2. **Build** - use Codex to implement or extend the compiler, generators, analyzers, and demo apps in this repo.\n3. **Run as MCP inside Codex** - connect the generated MCP server so Codex can call real tools, inspect app surfaces, and operate against the compiled environment.\n\n## Features\n- **Backend Analyzer:** Deep AST analysis of routes, controllers, and services to surface every callable action.\n- **Frontend Action Extraction:** React, Vue, Svelte components mapped to agent-controllable actions.\n- **OpenAPI → MCP:** Drop in a spec, ship a typed MCP server in seconds.\n- **Workflow Engine:** Multi-step processes detected and exposed as atomic agent capabilities.\n- **Permission Layer:** Scopes, roles, and audit trails enforced at the tool boundary.\n- **AI Metadata Enhancement:** Auto-generated descriptions, hints, and examples agents actually understand.\n- **Database Intelligence:** Schemas, relations, and constraints become safe, queryable surfaces.\n- **Event System Integration:** Webhooks, queues, and pub\u002Fsub plugged into agent loops.\n- **Knowledge Graph Engine:** Entities, intents, and relations modeled across your stack.\n- **Self-Updating Sync:** MCP definitions regenerate on every commit. No drift.\n- **AI Simulations:** Run agents against your app in a sandbox before shipping.\n\n## Getting Started\n\nThe easiest way to use MCPify is via `npx`. No installation required:\n\n```bash\nnpx mcpify-cli analyze .\n```\n\nTo run it against the flagship ecommerce example in this repo:\n\n```bash\nnpx mcpify-cli analyze .\u002Fexamples\u002Fecommerce-saas \\\n  --output .\u002Fexamples\u002Fecommerce-saas\u002F.mcpify \\\n  --prisma .\u002Fexamples\u002Fecommerce-saas\u002Fprisma\u002Fschema.prisma \\\n  --swagger .\u002Fexamples\u002Fecommerce-saas\u002Fopenapi.json\n```\n\nAlternatively, to build from source:\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Famarnath3003\u002FMCPify.git\ncd MCPify\nnpm install\nnpm run build\nnpm run mcpify -- analyze .\u002Fexamples\u002Fecommerce-saas \\\n  --output .\u002Fexamples\u002Fecommerce-saas\u002F.mcpify \\\n  --prisma .\u002Fexamples\u002Fecommerce-saas\u002Fprisma\u002Fschema.prisma \\\n  --swagger .\u002Fexamples\u002Fecommerce-saas\u002Fopenapi.json\n```\n\nAfter generation:\n\n```bash\ncd examples\u002Fecommerce-saas\u002F.mcpify\nnpm install\nnpm run build\n```\n\nThe generated `AGENTS.md` explains how to connect the compiled server to an MCP client. The ecommerce walkthrough lives in `examples\u002Fecommerce-saas\u002FDEMO.md`.\n\n## CLI\n\n### `analyze [path]`\n\nDefault command. Runs the full pipeline:\n- backend analysis\n- optional OpenAPI, Prisma, Drizzle, and Mongoose analysis\n- event and webhook discovery\n- optional frontend extraction\n- workflow detection\n- permission classification\n- MCP server generation\n\n```bash\nnpx mcpify-cli analyze . \\\n  --swagger .\u002Ftests\u002Ffixtures\u002Fswagger\u002Fpetstore.yaml \\\n  --prisma .\u002Ftests\u002Ffixtures\u002Fprisma\u002Fsimple.prisma \\\n  --watch\n```\n\nUseful flags:\n- `--output \u003Cdir>` change output directory\n- `--no-frontend` skip UI action extraction\n- `--no-events` skip webhook and listener analysis\n- `--no-workflows` skip workflow detection\n- `--ai-enhance` improve tool descriptions (requires `ANTHROPIC_API_KEY`)\n\n### `interactive`\n\nPrompts for which analyzers to run and which source files to include.\n\n```bash\nnpx mcpify-cli interactive\n```\n\n### `frontend [path]`\n\nExtracts UI actions only and can print raw JSON.\n\n```bash\nnpx mcpify-cli frontend .\u002Fexamples\u002Finternal-tool --json\n```\n\n### `swagger \u003Cfile>`\n\nConverts an OpenAPI or Swagger spec directly into MCP tools.\n\n```bash\nnpx mcpify-cli swagger .\u002Ftests\u002Ffixtures\u002Fswagger\u002Fpetstore.yaml\n```\n\n### `audit [path]` & `simulate [path]`\n\nRun a static safety audit over the discovered tools and workflows. When `ANTHROPIC_API_KEY` is available, `simulate` executes an AI simulation battery against the discovered tool surface.\n\n```bash\nnpx mcpify-cli simulate .\u002Fexamples\u002Fexpress-api\n```\n\n## Architecture\n\nBuilt for the way agents actually operate. A layered system that keeps your application untouched while exposing exactly what agents need:\n\n1. **AI Agents:** Any agent runtime (Claude, GPT, Custom) connects over MCP to start operating your software like a power user.\n2. **MCP Layer:** Generated tools, resources, and prompts that map 1:1 to real surface in your app. The contract agents speak.\n3. **Permissions:** Every call passes through scopes, audit logs, and rate limits before it touches your system.\n4. **Workflows:** Discovered user journeys exposed as composable, stateful operations agents can chain.\n5. **Your App:** Your existing stack (Frontend, Backend, Database, APIs) — untouched. MCPify reads it; it never rewrites it.\n\n## Repository Structure\n\n```txt\nmcpify\u002F\n  apps\u002F\n  docs\u002F\n  examples\u002F\n  landingPage\u002F\n  packages\u002F\n    ai-enhancer\u002F\n    backend-analyzer\u002F\n    cli\u002F\n    event-analyzer\u002F\n    frontend-analyzer\u002F\n    graph-engine\u002F\n    mcp-generator\u002F\n    monitoring\u002F\n    permissions\u002F\n    schema-engine\u002F\n    security\u002F\n    sync-engine\u002F\n    workflow-engine\u002F\n  tests\u002F\n```\n\n## License\n\nSee [LICENSE](LICENSE).\n",2,"2026-06-15 02:30:05","CREATED_QUERY"]