Project Info
This project did not submit a demo video on Devpost.
Inspiration
As the use of AI tools surged, we noticed a critical bottleneck: while users rely heavily on prompts, there's no standardized way to manage, share, or execute them across tools and teams. More importantly, users were stuck manually selecting or crafting prompts for each task—wasting time and reducing consistency. We were inspired by the potential of a new standard: MCP (Model Context Protocol). Imagine a world where any AI tool—like Cursor, Claude, or VSCode extensions—can automatically pull the best prompt for your task, intelligently selected and explained. That’s the vision PromptPilot is helping make real.
What it does
Stores, optimizes, and versions AI prompts. Runs an MCP server that understands user intent and intelligently returns the best-fit prompt for external tools or in-app tasks. Lets users configure personal MCP endpoints to plug PromptPilot directly into apps like Claude desktop or IDEs. Includes a Prompt Playground with an AI judge (built using Agentverse) that compares multiple prompts and provides objective, model-based feedback. Encourages community-driven prompt reuse and remixing. But the heart of the platform is its intelligent MCP integration—a game-changing layer for automated prompt delivery and AI workflow optimization.
How we built it
We used Next.js with TypeScript and TailwindCSS for the frontend, and Supabase for the database. The website is deployed using Vercel.
Challenges we ran into
Defining the MCP standard: There was no widely adopted format for AI prompt delivery over API. We had to build a usable, minimal configuration system and ensure it worked smoothly with tools expecting different levels of flexibility. Prompt selection logic: Building a reliable scoring model for prompts based on task intent took time and experimentation. Security concerns: Since MCP endpoints expose access to user data, we had to ensure strict token-based access and private-by-default behavior. Cross-tool compatibility: Ensuring the MCP server could be consumed by tools like Claude, Cursor, or AI-powered extensions required us to maintain a clean, well-documented API spec.
Accomplishments we're proud of
Launched one of the first working MCP server interfaces for prompt selection, opening up a new paradigm for AI task execution. Developed a plug-and-play MCP configuration system, making PromptPilot instantly usable as a backend for third-party AI tools. Enabled automated, intelligent prompt selection, removing friction for users and enhancing the quality of outputs. Created a version-controlled, remixable ecosystem that combines utility and creativity in the prompt design space.
What we learned
The future of AI tooling lies in interoperability. MCP showed us that standardizing how models receive prompts unlocks huge productivity gains. Prompt reuse isn’t enough—intelligent selection and automation must follow. Users want results, not prompt engineering. People will remix and collaborate when given clear attribution and useful defaults—but only if privacy is preserved. Model feedback can be trusted when combined with structured scoring and AI judges—empowering users with real metrics over guesswork.
What's next
MCP 2.0 Spec: Add support for multi-step workflows (e.g., generate → critique → rewrite), prompt chaining, and fallback prompts. Multi-model execution: Allow the MCP agent to select prompts and models across OpenAI, Claude, Gemini, and local LLMs based on performance history. CLI + IDE Plugins: Let developers use MCP directly inside their coding environment. MCP Prompt Marketplace: Allow verified creators to offer premium prompts via MCP endpoints. Analytics + Feedback Loop: Use real-world execution data to continuously retrain and improve prompt selection.
PromptPilot - Intelligent Task Execution MCP
PromptPilot is an advanced Model Context Protocol (MCP) tool that intelligently analyzes user tasks, breaks them down into components, and retrieves suitable prompts from your personal vault for execution in Cursor or Claude Desktop.
🚀 Key Features
Intelligent Task Analysis
- Automatic Task Classification: Identifies task types (research, writing, coding, planning, etc.)
- Complexity Assessment: Determines task complexity (low, medium, high)
- Keyword Extraction: Extracts relevant keywords for better prompt matching
- Step Estimation: Predicts required steps based on task complexity
Dynamic Prompt Retrieval
- Smart Matching: Finds the most relevant prompts from your vault
- Step-based Search: Looks for prompts matching workflow steps
- Keyword Matching: Searches by extracted keywords
- Relevance Scoring: Ranks prompts by relevance to the task
Execution Planning
- Step-by-step Instructions: Clear guidance for executing prompt chains
- Time Estimates: Predicts execution time
- Context Building: Each prompt builds on previous outputs
- Cursor/Claude Ready: Optimized for MCP clients
🛠️ How It Works
1. Task Analysis
When you provide a task like "research AI safety and create a summary":
- Pattern Recognition: Identifies task type using regex patterns
- Complexity Assessment: Analyzes task length and keyword count
- Step Estimation: Determines optimal number of steps
- Breakdown Planning: Maps task to workflow steps
2. Prompt Retrieval
The system searches your vault using:
- Step Matching: Looks for prompts matching workflow steps (background_research, deep_analysis, etc.)
- Keyword Matching: Finds prompts containing task keywords
- Relevance Scoring: Ranks prompts by match quality
- Deduplication: Avoids duplicate prompts
3. Execution Plan Creation
Generates a comprehensive plan with:
- Task Analysis: Shows detected type, complexity, keywords
- Prompt Chain: Ordered list of prompts to execute
- Instructions: Step-by-step execution guidance
- Time Estimates: Expected completion time
📋 Supported Task Types
| Task Type | Keywords | Example Tasks |
|---|---|---|
| Research | research, analyze, investigate, study, explore | "research AI safety", "analyze market trends" |
| Writing | write, compose, create, draft, generate content | "write a blog post", "compose an email" |
| Summary | summarize, condense, brief, overview, recap | "summarize this document", "create a brief" |
| Coding | code, program, develop, debug, review code | "review this code", "implement a feature" |
| Planning | plan, strategy, roadmap, outline, design | "plan a project", "create a roadmap" |
| Review | review, evaluate, assess, critique, analyze | "review this proposal", "evaluate options" |
| Brainstorming | brainstorm, ideate, generate, suggest | "brainstorm solutions", "generate ideas" |
| Problem Solving | solve, fix, resolve, troubleshoot, debug | "solve this bug", "fix the problem" |
| Learning | learn, understand, explain, educate | "explain this concept", "teach me about" |
| Creative | creative, artistic, design, imagine | "design a logo", "create artwork" |
🔧 MCP Tool Specification
Tool: execute_task_workflow
Description: Intelligently analyzes a user's task, breaks it down into components, retrieves suitable prompts from their vault, and returns an executable workflow for Cursor or Claude Desktop.
Input Schema:
{
"type": "object",
"properties": {
"task": {
"type": "string",
"description": "The task you want to accomplish. For example: 'research AI safety and create a summary' or 'write a blog post about machine learning trends'."
}
},
"required": ["task"]
}
Response Format:
{
"task": "research AI safety and create a summary",
"analysis": {
"primaryType": "research",
"secondaryTypes": ["summary"],
"complexity": "medium",
"estimatedSteps": 3,
"keywords": ["research", "safety", "summary"],
"breakdown": ["background_research", "deep_analysis", "synthesis", "summary"]
},
"prompts": [
{
"id": 1,
"title": "Background Research Prompt",
"content": "Conduct initial research on...",
"order": 1,
"step": "background_research",
"instructions": "Execute this prompt and use its output as input for the next step."
}
],
"totalSteps": 3,
"estimatedTime": "6-9 minutes",
"executionInstructions": "1. Execute each prompt in order... 2. Use output as context..."
}
🎯 Usage Examples
Example 1: Research Task
Input: "research AI safety and create a comprehensive summary"
Analysis:
- Primary Type: research
- Secondary Type: summary
- Complexity: medium
- Estimated Steps: 3
Result: 3-step prompt chain:
- Background Research Prompt
- Deep Analysis Prompt
- Summary Creation Prompt
Example 2: Writing Task
Input: "write a blog post about machine learning trends in 2024"
Analysis:
- Primary Type: writing
- Complexity: medium
- Estimated Steps: 3
Result: 3-step prompt chain:
- Outline Creation Prompt
- Content Drafting Prompt
- Review and Polish Prompt
Example 3: Coding Task
Input: "review and optimize this Python code for performance"
Analysis:
- Primary Type: coding
- Secondary Type: review
- Complexity: medium
- Estimated Steps: 3
Result: 3-step prompt chain:
- Code Analysis Prompt
- Performance Review Prompt
- Optimization Suggestions Prompt
🏗️ Architecture
User Task → MCP API → Task Analysis → Prompt Retrieval → Execution Plan
↓
Task Analysis Engine
├── Pattern matching for task types
├── Complexity assessment
├── Keyword extraction
└── Step estimation
Prompt Retrieval Engine
├── Step-based matching
├── Keyword-based matching
├── Relevance scoring
└── Deduplication
Execution Plan Generator
├── Prompt ordering
├── Instruction generation
├── Time estimation
└── Context building
🚀 Getting Started
1. Install Dependencies
npm install
2. Set up Supabase
- Configure your Supabase credentials in environment variables
- Ensure the prompts table exists with the required schema
3. Add Prompts to Vault
- Use the Vault interface to add diverse prompts
- Tag prompts appropriately for better matching
- Include prompts for different task types
4. Test the MCP
- Visit
/test-mcpto test the workflow engine - Try different task types to see dynamic execution plans
- Check the execution instructions and prompt chains
5. Use with Cursor/Claude Desktop
- Configure the MCP server URL in your MCP client
- Use the
execute_task_workflowtool with your tasks - Follow the execution plan to accomplish your goals
🎨 Test Interface
The test page at /test-mcp provides:
- Quick Test Examples: Pre-defined tasks to try
- Task Input: Text area for custom tasks
- Task Analysis Display: Shows detected type, complexity, keywords
- Execution Plan: Step-by-step instructions and time estimates
- Prompt Chain: Ordered list of prompts with content and instructions
- Raw JSON: Toggle to see the complete MCP response
🔮 Future Enhancements
- AI-powered Analysis: Use LLM for more accurate task classification
- Learning System: Improve matching based on successful executions
- Custom Workflows: Allow users to create and save custom workflows
- Advanced Chaining: Support conditional logic and branching
- Integration APIs: Connect with external tools and services
- Collaborative Features: Share workflows and prompts between users
📝 License
MIT License - see LICENSE file for details.
Analysis
View
Metric
- 36
- 11
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- Google GeminiIn code
- JavaScriptIn code
- Next.jsIn code
- ReactIn code
- SupabaseIn code
- Tailwind CSSIn code
- TypeScriptIn code
- VercelClaimed
8 of 9 appear in the indexed code. 1 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
172 KB
Source files
34
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
DavidWangwjh/prompt-pilot
48 files · 1.7 MB · @ e48e2d2
Structure
Interface
17 files · 35%Screens, components and styles rendered to the user.
API & routing
3 files · 6%Request entry points: routes, handlers and controllers.
Application logic
7 files · 15%Domain rules, services and shared utilities.
Data & schema
2 files · 4%Schema definitions, migrations and data access.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- TypeScript88%
- Markdown11%
- CSS1%
- JavaScript0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 24- @google/generative-ai
- @heroicons/react
- @supabase/auth-helpers-nextjs
- @supabase/ssr
- @supabase/supabase-js
- clsx
- fetchai-sdk
- fuse.js
- lucide-react
- next
- react
- react-dom
- tailwind-merge
- +11 more
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.