This MCP server provides pre-defined prompt templates for AI assistants to generate comprehensive plans for TypeScript projects, API architectures, and GitHub workflows. It helps ensure consistent, high-quality output following modern TypeScript development standards while working seamlessly with the Local Dev MCP to create a complete workflow from planning to implementation.
Clone the repository
git clone <repository-url>
cd typescript-prompt-mcp
Install dependencies
npm install
Set up environment variables
# Create development environment file
cp .env.example .env.development
# Create production environment file
cp .env.example .env.production
Development Mode:
npm run dev
Production Mode:
npm run build
npm start
Or use the shorthand:
npm run prod
Start the MCP server locally on your machine
Add the MCP to Claude Desktop
TypeScript Prompt MCP
(or any name you prefer)http://localhost:3000
)Alternative: Configure via command
"ts-prompts": {
"command": "node",
"args": [
"YOUR_CUSTOM_PATH/dist/index.js"
]
}
Enable the MCP by toggling the switch next to it
Add Local Dev MCP using the same process for a complete workflow
Verify the connection by starting a new conversation with Claude and asking for help with TypeScript project planning
Once connected, you can ask Claude questions like:
Generates a comprehensive architecture plan for a TypeScript API.
Parameters:
projectName
: Name of the API projectdatabase
: Database to use (postgres, mysql, mongodb, etc.)auth
: Authentication method (jwt, oauth, none)endpoints
: Comma-separated list of main API endpointsGenerates a setup plan for a new TypeScript project.
Parameters:
projectName
: Name of the projectprojectType
: Type of project (api, frontend, library, cli)features
: Key features or requirements separated by commasGenerates a GitHub workflow plan for a TypeScript project.
Parameters:
projectName
: Name of the projectciFeatures
: Comma-separated list of CI features (lint, test, build, etc.)deployTarget
: Deployment target (netlify, vercel, aws, azure, etc.)branchStrategy
: Branch strategy (gitflow, trunk, github-flow)There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"cursor-rules-mcp": {
"command": "npx",
"args": [
"-y",
"cursor-rules-mcp"
]
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.