PitchDeck MCP Server
# PitchDeck MCP Server
An MCP (Model Context Protocol) server that generates AI-powered pitch decks for startups and businesses.
## Features
- **generate_pitch_deck** - Creates a complete investor pitch deck with:
- Title slide
- Problem statement
- Solution overview
- Market opportunity
- Business model
- Competitive landscape (optional)
- Traction & milestones
- Team overview
- Financial projections
- Funding request (optional)
- Closing slide
## Installation
```bash
npm install
npm run build
```
## Usage
### As an MCP Server
Add to your MCP client configuration (e.g., Claude Desktop):
```json
{
"mcpServers": {
"pitchdeck": {
"command": "node",
"args": ["/path/to/pitchdeck-mcp/dist/index.js"]
}
}
}
```
### Tool: generate_pitch_deck
Generate a complete pitch deck for your startup.
**Required Inputs:**
| Parameter | Type | Description |
|-----------|------|-------------|
| `company_name` | string | The name of the company or startup |
| `problem` | string | The problem or pain point the company solves |
| `solution` | string | The solution or product the company offers |
| `market_size` | string | Target market and size (e.g., "$10B healthcare market") |
| `business_model` | string | How the company makes money |
**Optional Inputs:**
| Parameter | Type | Description |
|-----------|------|-------------|
| `industry` | string | Industry vertical (auto-detected if not provided) |
| `competition` | string | Key competitors and landscape |
| `funding_amount` | string | Amount being raised (e.g., "$2M seed round") |
| `use_of_funds` | string | Allocation of funding |
**Example:**
```json
{
"company_name": "TechFlow",
"problem": "Small businesses waste 20+ hours per week on manual data entry",
"solution": "AI-powered automation platform with 99.9% accuracy",
"market_size": "$200B SMB administrative software market",
"business_model": "SaaS subscription: $99/month starter, $299/month pro",
"competition": "Legacy players like SAP are slow and expensive",
"funding_amount": "$3M Seed Round"
}
```
**Output:**
Returns a JSON object with:
- `companyName`: Company name
- `slides`: Array of slide objects with `title`, `content`, and `type`
- `generatedAt`: ISO timestamp
## Development
```bash
# Install dependencies
npm install
# Run in development mode
npm run dev
# Run tests
npm test
# Build for production
npm run build
```
## Testing
```bash
npm test
```
Tests cover:
- Required field generation
- Optional field handling (competition, funding)
- Slide content validation
- Edge cases (company names with spaces)
## License
MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined and distinct by default.
The single tool name 'generate_pitch_deck' follows a clear verb_noun pattern, and with no other tools, consistency is inherently perfect. There are no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'PitchDeck MCP Server', which suggests a broader domain like pitch deck creation and management. This minimal toolset feels thin and limits functionality, as it only covers generation without supporting operations like editing, listing, or deleting pitch decks.
The tool surface is severely incomplete for the implied domain of pitch deck management. While generation is covered, there are significant gaps such as updating existing decks, retrieving or listing decks, deleting decks, or handling slide-level operations, which will likely cause agent failures in broader workflows.