Skip to main content
Glama
AI Development Pipeline MCP

AI Development Pipeline MCP

by theburgerllc

AI Development Pipeline MCP Integration

A comprehensive Model Context Protocol (MCP) server implementation that enables seamless integration between Claude AI, VSCode, Augment, and various cloud services including Vercel, Airtable, and Square.

๐Ÿš€ Features

  • Local MCP Server: Direct stdio integration with Claude Desktop

  • Cloud MCP Server: HTTP endpoint for web-based Claude integration

  • 7 Powerful MCP Tools: File operations, shell commands, and AI agent integration

  • Multi-Platform Support: Windows (PowerShell) and Unix (Bash) startup scripts

  • Production Ready: Vercel deployment configuration included

Related MCP server: My MCP Server

๐Ÿ“‹ Prerequisites

  • Node.js 18+ and npm

  • TypeScript and ts-node

  • Claude Desktop (for local integration)

  • Vercel account (for cloud deployment)

๐Ÿ› ๏ธ Installation

  1. Clone the repository:

git clone https://github.com/yourusername/ai-development-pipeline-mcp.git
cd ai-development-pipeline-mcp
  1. Install dependencies:

npm install
  1. Configure environment variables:

cp .env.example .env
# Edit .env with your API keys and configuration

๐Ÿ”ง Configuration

Create a .env file in the root directory with the following variables:

# Vercel Configuration
VERCEL_TOKEN=your_vercel_token_here
VERCEL_PROJECT_ID=your_project_id_here

# Airtable Configuration  
AIRTABLE_API_KEY=your_airtable_api_key_here
AIRTABLE_BASE_ID=your_base_id_here
AIRTABLE_TABLE_NAME=your_table_name_here

# Square Configuration
SQUARE_APPLICATION_ID=your_square_app_id_here
SQUARE_ACCESS_TOKEN=your_square_access_token_here

# Analytics Configuration
ANALYTICS_SECRET=your_analytics_secret_here
NEXT_PUBLIC_APP_URL=https://your-app-url.vercel.app

๐Ÿ–ฅ๏ธ Local MCP Server Setup

For Windows (PowerShell):

.\start-mcp.ps1

For Unix/Linux/macOS (Bash):

chmod +x start-mcp.sh
./start-mcp.sh

Manual Start:

npx ts-node local-mcp-server.ts

๐Ÿ”— Claude Desktop Integration

  1. Start the local MCP server using one of the methods above

  2. Configure Claude Desktop by adding the following to your Claude Desktop configuration:

{
  "mcpServers": {
    "ai-development-pipeline": {
      "command": "npx",
      "args": ["ts-node", "/path/to/your/project/local-mcp-server.ts"],
      "env": {}
    }
  }
}
  1. Restart Claude Desktop to load the MCP server

โ˜๏ธ Cloud Deployment (Vercel)

  1. Connect to GitHub:

    • Go to Vercel Dashboard

    • Click "New Project" and import your GitHub repository

    • Vercel will automatically detect the configuration

  2. Manual Deployment:

npm install -g vercel
vercel deploy --prod

Build Configuration

The project includes a vercel.json configuration that handles:

  • TypeScript compilation

  • API route setup

  • CORS headers

  • Output directory configuration

Environment Variables

Configure these in your Vercel dashboard:

  • AIRTABLE_API_KEY

  • AIRTABLE_BASE_ID

  • AIRTABLE_TABLE_NAME

  • SQUARE_ACCESS_TOKEN

  • SQUARE_APPLICATION_ID

  • NEXTAUTH_SECRET

  • MCP_API_KEY

  • All other variables from .env.example

Claude Integration

Add to Claude as an HTTP MCP server:

  • URL: https://your-app.vercel.app/api/mcp

  • Method: POST

  • Headers: Content-Type: application/json

๐Ÿ› ๏ธ Available MCP Tools

The server provides 7 powerful tools for AI-driven development:

  1. read_project_file - Read files from the workspace

  2. write_project_file - Write/update files in the workspace

  3. run_shell_command - Execute shell commands (npm, git, etc.)

  4. check_file_exists - Check if files exist

  5. list_directory_files - List directory contents

  6. run_augment_prompt - Send prompts to Augment coding agent

  7. run_project_tests - Execute project tests

๐Ÿ“ Project Structure

ai-development-pipeline-mcp/
โ”œโ”€โ”€ app/
โ”‚   โ””โ”€โ”€ api/
โ”‚       โ””โ”€โ”€ mcp/
โ”‚           โ””โ”€โ”€ route.ts          # Cloud MCP endpoint
โ”œโ”€โ”€ src/
โ”‚   โ””โ”€โ”€ hello.ts                  # Example TypeScript module
โ”œโ”€โ”€ local-mcp-server.ts           # Local MCP server implementation
โ”œโ”€โ”€ start-mcp.sh                  # Unix startup script
โ”œโ”€โ”€ start-mcp.ps1                 # Windows startup script
โ”œโ”€โ”€ package.json                  # Dependencies and scripts
โ”œโ”€โ”€ tsconfig.json                 # TypeScript configuration
โ”œโ”€โ”€ .env.example                  # Environment template
โ””โ”€โ”€ README.md                     # This file

๐Ÿงช Testing

Run the TypeScript compiler to check for errors:

npx tsc --noEmit

Test the local MCP server:

npx ts-node local-mcp-server.ts

๐Ÿ”’ Security Considerations

  • Never commit .env files - They contain sensitive API keys

  • Use environment variables for all secrets in production

  • Review API permissions before deploying to production

  • Enable proper authentication for cloud deployments

๐Ÿค Contributing

  1. Fork the repository

  2. Create a feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

๐Ÿ“ License

This project is licensed under the MIT License - see the LICENSE file for details.

๐Ÿ†˜ Troubleshooting

Common Issues:

"Module not found" errors:

  • Ensure all dependencies are installed: npm install

  • Check TypeScript configuration in tsconfig.json

MCP server won't start:

  • Verify Node.js version (18+ required)

  • Check that ts-node is available: npx ts-node --version

Claude Desktop integration issues:

  • Ensure the MCP server is running before starting Claude

  • Check the file path in Claude Desktop configuration

  • Restart Claude Desktop after configuration changes

Getting Help:

๐Ÿ“Š Project Status

โœ… Ready for Production

  • Local MCP server fully functional

  • Cloud deployment configured

  • All 7 MCP tools tested and validated

  • Cross-platform startup scripts included

  • Comprehensive documentation provided


Built with โค๏ธ for the AI development community

Available Tools

7 tools
check_file_existsB

Check if a local file exists (restricted to workspace directory)

Inputs: path (required).

list_directory_filesC

List files in a workspace directory (restricted to workspace directory)

Inputs: dir (required).

read_project_fileB

Read a local file from the VS Code workspace (restricted to workspace directory)

Inputs: path (required).

run_augment_promptC

Send a prompt to the local Augment coding agent

Inputs: prompt (required).

run_project_testsB

Run project tests (npm test, yarn test, etc.)

Inputs: no named parameters.

run_shell_commandB

Run a whitelisted shell command in the workspace (npm, yarn, git, node, npx, tsc, eslint, prettier)

Inputs: command (required).

write_project_fileB

Write to a local file in the VS Code workspace (restricted to workspace directory)

Inputs: path (required), content (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: file operations (check, list, read, write), running tests, executing shell commands, and interacting with an AI agent. The descriptions make it easy to tell them apart, preventing misselection.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (e.g., check_file_exists, list_directory_files, run_project_tests), but 'run_augment_prompt' deviates slightly by including the agent name. Overall, the naming is predictable and readable with only minor inconsistency.

    Tool Count5/5

    With 7 tools, this server is well-scoped for AI development pipeline tasks. Each tool earns its place by covering essential operations like file management, testing, shell commands, and AI interaction, without being too sparse or bloated.

    Completeness4/5

    The toolset covers core AI development workflows effectively, including file CRUD, testing, and command execution. A minor gap exists in version control operations (e.g., git commits or branches), but agents can work around this using the shell command tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers