deploy-mcp 0.2.0 → 0.4.0

package/README.md

@@ -16,72 +16,37 @@ No more context-switching. No more dashboard hunting.
 ---
 
 ## Demo
+─────────────────────────
 
+### Your conversation:
 ```
-// In your AI conversation:
-"Check my latest Vercel deployment"
-
-// Claude's Response:
-✅ **Status**: Success  
-🌐 **Live URL**: https://my-app.vercel.app  
-⏱️ **Deployment Time**: 45 seconds  
-📅 **Last Deployed**: January 15, 2025 at 10:30 UTC  
-🌍 **Environment**: Production  
-
-**Latest Commit**:
-- SHA: `abc123ef`
-- Message: "Update homepage hero section"
-- Author: John Doe
-
-Everything looks good - your deployment is live and running successfully!
+User: "Check my latest Vercel deployment"
 ```
 
+### AI Assistant's Response:
+
+> ## Deployment Status
+> 
+> ### Current Status
+> **Project:** my-app  
+> **Platform:** Vercel  
+> **Status:** ✅ Success  
+> **URL:** https://my-app.vercel.app  
+> **Duration:** 45s  
+> **Deployed:** 2 hours ago  
+> 
+> ### Commit Info
+> **SHA:** `abc123ef`  
+> **Message:** Update homepage hero section  
+> **Author:** John Doe  
+> 
+> Everything looks good - your deployment is live and running successfully!
+
 **Just ask your AI**: *"What's the status of my latest deployment?"*  
 Get instant answers without leaving your conversation.
 
-## Features
-
-<table>
-<tr>
-<td width="50%">
-
-**Universal AI Support**  
-Built for the Model Context Protocol. Works seamlessly with Claude Desktop, VS Code, Cursor, Windsurf, Continue.dev, Cline, and any MCP-compatible AI assistant.
-
-**Secure & Private**  
-Your API tokens stay local on your machine. Never sent to third parties or logged anywhere.
-
-**Lightning Fast**  
-Get deployment status in under 2 seconds. Optimized for developer productivity.
-
-</td>
-<td width="50%">
-
-**Zero Context Switching**  
-Check deployment status without leaving your AI conversation.
-
-**Universal Platform Support**  
-Currently supports Vercel, with Netlify, Railway, and Render coming soon.
-
-**Real-time Status**  
-Get instant deployment status through AI conversation.
-
-**Open Source**  
-Fully transparent, community-driven development.
-
-</td>
-</tr>
-</table>
-
-## Why deploy-mcp?
-
-**The Problem**: Developers context-switch 10-20 times per day to check deployment status, losing 23 minutes of focus each time.
-
-**The Solution**: deploy-mcp brings deployment status directly into your AI conversation. No more alt-tabbing, no more dashboard hunting, no more broken flow state.
-
-Built for the modern developer who uses AI assistants as part of their daily workflow.
-
 ## Quick Start
+─────────────────────────
 
 **Get started in under 30 seconds:**
 
@@ -91,94 +56,117 @@ npx deploy-mcp
 
 That's it! The server is now running and ready to be configured in your AI assistant.
 
-## Configuration
-
-### AI Assistants
-
-<details>
-<summary><strong>Claude Desktop</strong> ✅</summary>
+## Supported Platforms
+─────────────────────────
 
-**Official MCP support** - Ready to use today
+deploy-mcp supports multiple deployment platforms simultaneously. Configure as many as you need:
 
-**macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`  
-**Windows**: `%APPDATA%\Claude\claude_desktop_config.json`  
-**Linux**: `~/.config/Claude/claude_desktop_config.json`
+| Platform | Status | Token Required | Features |
+|----------|--------|---------------|----------|
+| **Vercel** | ✅ Ready | `VERCEL_TOKEN` | Status, Logs, History, Real-time Monitoring |
+| **Netlify** | ✅ Ready | `NETLIFY_TOKEN` | Status, Logs, History, Real-time Monitoring |
+| **Railway** | Coming Soon | `RAILWAY_TOKEN` | - |
+| **Render** | Coming Soon | `RENDER_TOKEN` | - |
 
-</details>
+### Multi-Platform Configuration
 
-<details>
-<summary><strong>VS Code</strong> ✅</summary>
+You can use **multiple platforms simultaneously** by providing tokens for each platform you want to track:
 
-**Official MCP support** - Generally available in VS Code 1.102+
+```json
+{
+  "mcpServers": {
+    "deploy-mcp": {
+      "command": "npx",
+      "args": ["-y", "deploy-mcp"],
+      "env": {
+        "VERCEL_TOKEN": "your-vercel-token",
+        "NETLIFY_TOKEN": "your-netlify-token"
+        // Add more platform tokens as needed
+      }
+    }
+  }
+}
+```
 
-Add to workspace `.vscode/mcp.json` or global `~/.vscode/mcp.json`
+## Platform Configuration
+─────────────────────────
 
-Requires GitHub Copilot subscription and MCP policy enabled by organization.
-</details>
+### Vercel
 
 <details>
-<summary><strong>Cursor AI</strong> ✅</summary>
+<summary><strong>Setup Instructions</strong></summary>
+
+1. **Get your API token:**
+   - Go to [vercel.com/account/tokens](https://vercel.com/account/tokens)
+   - Click "Create Token"
+   - Give it a descriptive name (e.g., "deploy-mcp")
+   - Copy the token
+
+2. **Add to your AI assistant configuration:**
+   ```json
+   {
+     "env": {
+       "VERCEL_TOKEN": "your-vercel-token"
+     }
+   }
+   ```
 
-**Official MCP support** - Available with one-click installation
+3. **Available commands:**
+   - `"Check my Vercel deployment for project-name"`
+   - `"What's the status of my latest Vercel deployment?"`
+   - `"Show me Vercel deployment logs"`
+   - `"Watch my Vercel deployment progress"`
 
-Navigate to Cursor Settings → MCP or create `~/.cursor/mcp.json`
+4. **Required permissions:** Read access to deployments and projects
 
 </details>
 
-<details>
-<summary><strong>Windsurf IDE</strong> ✅</summary>
-
-**Official MCP support** - Native integration with Cascade
-
-Navigate to Windsurf Settings → Advanced Settings → Cascade or edit `~/.codeium/windsurf/mcp_config.json`
-
-</details>
+### Netlify
 
 <details>
-<summary><strong>Continue.dev</strong> ✅</summary>
-
-**Official MCP support** - Available in agent mode
+<summary><strong>Setup Instructions</strong></summary>
+
+1. **Get your API token:**
+   - Go to [app.netlify.com/user/applications](https://app.netlify.com/user/applications)
+   - Under "Personal access tokens", click "New access token"
+   - Give it a descriptive name (e.g., "deploy-mcp")
+   - Copy the token
+
+2. **Add to your AI assistant configuration:**
+   ```json
+   {
+     "env": {
+       "NETLIFY_TOKEN": "your-netlify-token"
+     }
+   }
+   ```
 
-Add to your `config.json` with different structure:
+3. **Available commands:**
+   - `"Check my Netlify deployment for site-name"`
+   - `"What's the status of my latest Netlify deployment?"`
+   - `"Show me Netlify deployment logs"`
+   - `"Watch my Netlify deployment progress"`
 
-```json
-{
-  "experimental": {
-    "modelContextProtocolServer": {
-      "transport": {
-        "type": "stdio",
-        "command": "npx",
-        "args": ["-y", "deploy-mcp"]
-      },
-      "env": {
-        "VERCEL_TOKEN": "your-vercel-token"
-      }
-    }
-  }
-}
-```
+4. **Required permissions:** Read access to sites and deploys
 
-Or create `.continue/mcpServers/` folder in your workspace.
 </details>
 
-<details>
-<summary><strong>Cline (VS Code)</strong> ✅</summary>
-
-**Official MCP support** - Can create and install tools automatically
+## AI Assistant Configuration
+─────────────────────────
 
-Cline can install deploy-mcp through natural language:
-- Ask: *"Add the deploy-mcp tool to check Vercel deployments"*
-- Or manually configure via MCP Servers icon → Advanced MCP Settings
+deploy-mcp works with any MCP-compatible AI assistant. Here's how to set it up:
 
-</details>
-
-**+ Any MCP-compatible tool**  
-Works with all AI assistants that support [Model Context Protocol](https://modelcontextprotocol.io)
+### Claude Desktop
 
-### MCP Configuration
+<details>
+<summary><strong>Configuration</strong></summary>
 
-All AI tools (except Continue.dev) use the same configuration:
+**File location:**
+- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`  
+- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`  
+- **Linux**: `~/.config/Claude/claude_desktop_config.json`
 
+**Configuration:**
 ```json
 {
   "mcpServers": {
@@ -186,399 +174,248 @@ All AI tools (except Continue.dev) use the same configuration:
       "command": "npx",
       "args": ["-y", "deploy-mcp"],
       "env": {
-        "VERCEL_TOKEN": "your-vercel-token"
+        "VERCEL_TOKEN": "your-vercel-token",
+        "NETLIFY_TOKEN": "your-netlify-token"
       }
     }
   }
 }
 ```
 
-💡 Replace `your-vercel-token` with your actual Vercel API token from [vercel.com/account/tokens](https://vercel.com/account/tokens)
-
-## Deployment Status Badges
-
-Get live deployment status badges for your repositories that update in real-time via webhooks.
-
-### Badge URLs
-
-Add these badges to your README to show live deployment status:
-
-```markdown
-![Vercel Deployment](https://deploy-mcp.io/badge/username/repository/vercel)
-```
+</details>
 
-**Examples:**
-- `https://deploy-mcp.io/badge/john/my-app/vercel`
-- `https://deploy-mcp.io/badge/youruser/yourrepo/vercel`
+### VS Code
 
-**⚠️ Requirements:**
-- **Public repositories only** - Private repos not supported for security reasons
-- **Vercel Pro/Enterprise plan** - Webhooks required for real-time badge updates
+<details>
+<summary><strong>Configuration</strong></summary>
 
-**For free tier users:** The MCP server works perfectly for checking deployment status in your AI conversations. Badges are a premium feature requiring paid Vercel plans.
+**File location:**
+- Workspace: `.vscode/mcp.json`
+- Global: `~/.vscode/mcp.json`
 
-### Setting Up Webhooks
+**Requirements:** GitHub Copilot subscription with MCP enabled
 
-For badges to show real-time status, configure webhooks in your deployment platform:
+**Configuration:** Same as Claude Desktop
 
-#### Vercel Setup
+</details>
 
-**Note:** Vercel webhooks require a Pro or Enterprise plan.
+### Cursor AI
 
-1. **Go to your Vercel team settings**
-2. **Navigate to "Webhooks" section**
-3. **Click "Create Webhook"**
-4. **Configure the webhook:**
-   - **URL**: `https://deploy-mcp.io/webhook/yourusername/yourrepo/vercel`
-   - **Events**: Select "Deployment Created", "Deployment Ready", and "Deployment Error"
-   - **Projects**: Choose your specific project or leave empty for all projects
-   - **Secret**: Leave empty (not required for public repositories)
-5. **Save the webhook**
+<details>
+<summary><strong>Configuration</strong></summary>
 
-**Important:** Replace `yourusername` and `yourrepo` with your actual GitHub username and repository name.
+**File location:** `~/.cursor/mcp.json`
 
-**Note:** Vercel's free tier doesn't support webhooks, so badges won't work. Use the MCP server instead for deployment status in your AI conversations.
+**Setup:** Navigate to Cursor Settings → MCP
 
-#### Supported Events
+**Configuration:** Same as Claude Desktop
 
-The webhook will trigger on:
-- ✅ Deployment started (badge shows "building")
-- ✅ Deployment succeeded (badge shows "success")
-- ❌ Deployment failed (badge shows "failed")
-- ⚠️ Deployment errored (badge shows "error")
+</details>
 
-#### Badge Status Colors
+### Windsurf IDE
 
-- 🟢 **Success** - Green badge when deployment is live
-- 🔴 **Failed** - Red badge when deployment failed
-- 🟡 **Building** - Yellow badge during deployment
-- ⚫ **Unknown** - Grey badge when no status available
-- 🔴 **Error** - Red badge when deployment errored
+<details>
+<summary><strong>Configuration</strong></summary>
 
-### Testing Your Setup
+**File location:** `~/.codeium/windsurf/mcp_config.json`
 
-1. **Add the badge** to your repository README
-2. **Configure the webhook** as described above
-3. **Make a commit** and push to trigger a deployment
-4. **Watch the badge** update in real-time during deployment
+**Setup:** Settings → Advanced Settings → Cascade
 
-**Initial badge status will show "unknown" until the first webhook is received.**
+**Configuration:** Same as Claude Desktop
 
+</details>
 
-### Getting API Tokens
+### Continue.dev
 
 <details>
-<summary><strong>Vercel</strong></summary>
+<summary><strong>Configuration</strong></summary>
 
-1. Go to [Vercel Dashboard](https://vercel.com/account/tokens)
-2. Click **"Create Token"**
-3. Give it a descriptive name (e.g., "deploy-mcp")
-4. Select appropriate scope (read-only is sufficient)
-5. Copy the token and add it to your configuration
+**File location:** `~/.continue/config.json`
 
-</details>
-
-<details>
-<summary><strong>Netlify</strong> (Coming Soon)</summary>
+**Configuration (different structure):**
+```json
+{
+  "experimental": {
+    "modelContextProtocolServer": {
+      "transport": {
+        "type": "stdio",
+        "command": "npx",
+        "args": ["-y", "deploy-mcp"]
+      },
+      "env": {
+        "VERCEL_TOKEN": "your-vercel-token",
+        "NETLIFY_TOKEN": "your-netlify-token"
+      }
+    }
+  }
+}
+```
 
-1. Go to [Netlify User Settings](https://app.netlify.com/user/applications#personal-access-tokens)
-2. Click **"New access token"**
-3. Give it a descriptive name
-4. Copy the token
 </details>
 
-<details>
-<summary><strong>Railway</strong> (Coming Soon)</summary>
-
-Railway integration is on our roadmap. [Star the repo](https://github.com/alexpota/deploy-mcp) to get notified!
-</details>
+### Cline (VS Code Extension)
 
 <details>
-<summary><strong>Render</strong> (Coming Soon)</summary>
+<summary><strong>Configuration</strong></summary>
 
-Render integration is on our roadmap. [Star the repo](https://github.com/alexpota/deploy-mcp) to get notified!
-</details>
+**Natural language setup:**
+- Ask: *"Add the deploy-mcp tool to check deployments"*
 
-## Usage Examples
+**Manual setup:**
+- MCP Servers icon → Advanced MCP Settings
 
-### MCP Server Usage
+**Configuration:** Same as Claude Desktop
 
-Once configured with your AI assistant, simply ask:
+</details>
 
-```
-You: Check my latest Vercel deployment
+## Deployment Status Badges
+─────────────────────────
 
-Assistant: I'll check your latest Vercel deployment for you.
+Get live deployment status badges for your repositories:
 
-✅ **Status**: Success
-🌐 **Live URL**: https://my-app.vercel.app
-⏱️ **Deployment Time**: 45 seconds
-📅 **Last Deployed**: January 15, 2025 at 10:30 UTC
-🌍 **Environment**: Production
+### Badge Format
 
-**Latest Commit**:
-- SHA: `abc123ef`
-- Message: "Update homepage hero section"
-- Author: John Doe
+The deploy-mcp.io endpoint returns JSON data for shields.io. Use the shields.io endpoint wrapper:
 
-Everything looks good - your deployment is live and running successfully!
+```markdown
+![Platform Deployment](https://img.shields.io/endpoint?url=https://deploy-mcp.io/badge/{username}/{repository}/{platform})
 ```
 
-**More examples:**
-- `"Is my website deployment finished?"`
-- `"Show me the deployment status for project-xyz"`
-- `"Check if the production deployment succeeded"`
-- `"What's the status of my latest deploy?"`
-
-### Badge Usage
-
-Add live deployment status badges to your README:
+### Examples by Platform
 
+#### Vercel Badge
 ```markdown
-# My Project
-
-![Vercel](https://deploy-mcp.io/badge/yourusername/yourrepo/vercel)
+![Vercel](https://img.shields.io/endpoint?url=https://deploy-mcp.io/badge/john/my-app/vercel)
+```
 
-<!-- Other content -->
+#### Netlify Badge
+```markdown
+![Netlify](https://img.shields.io/endpoint?url=https://deploy-mcp.io/badge/john/my-app/netlify)
 ```
 
-**Multiple platforms:**
+#### Multiple Badges
 ```markdown
-[![Vercel](https://deploy-mcp.io/badge/user/repo/vercel)](https://deploy-mcp.io)
-[![Netlify](https://deploy-mcp.io/badge/user/repo/netlify)](https://deploy-mcp.io)
+![Vercel](https://img.shields.io/endpoint?url=https://deploy-mcp.io/badge/john/my-app/vercel)
+![Netlify](https://img.shields.io/endpoint?url=https://deploy-mcp.io/badge/john/my-app/netlify)
 ```
 
+### Webhook Configuration
 
-## MCP Tools Reference
-Retrieve the latest deployment status for a project.
+For real-time badge updates, configure webhooks:
 
 <details>
-<summary><strong>Parameters</strong></summary>
+<summary><strong>Vercel Webhooks</strong> (Pro/Enterprise only)</summary>
 
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `platform` | string | ✓ | Deployment platform (`vercel`, `netlify`, etc.) |
-| `project` | string | ✓ | Project name or ID |
-| `token` | string | ✗ | API token (uses env variable if not provided) |
+1. Go to your Vercel team settings
+2. Navigate to "Webhooks" section
+3. Click "Create Webhook"
+4. Configure:
+   - **URL**: `https://deploy-mcp.io/webhook/{username}/{repo}/vercel`
+   - **Events**: Deployment Created, Ready, Error
+   - **Projects**: Select specific or all
 
 </details>
 
 <details>
-<summary><strong>Response Format</strong></summary>
+<summary><strong>Netlify Webhooks</strong></summary>
 
-```typescript
-{
-  status: "success" | "failed" | "building" | "error",
-  url: string,
-  projectName: string,
-  platform: string,
-  timestamp: string,
-  duration: number,
-  environment: "production" | "preview" | "development",
-  commit: {
-    sha: string,
-    message: string,
-    author: string
-  }
-}
-```
+1. Go to Site Settings → Build & deploy → Deploy notifications
+2. Add notification → Outgoing webhook
+3. Configure:
+   - **URL**: `https://deploy-mcp.io/webhook/{username}/{repo}/netlify`
+   - **Events**: Deploy started, succeeded, failed
 
 </details>
 
-## Development
+**Note:** Badges require public repositories. Private repo support coming soon.
 
-For contributors who want to help develop deploy-mcp.
+## Available Tools
+─────────────────────────
 
-### Prerequisites
+deploy-mcp provides these tools to your AI assistant:
 
-- Node.js 22 or higher
-- npm, yarn, or pnpm
+### Core Tools
 
-### Local Development
+| Tool | Description | Example Command |
+|------|-------------|-----------------|
+| `check_deployment_status` | Get latest deployment status | *"Check my deployment status"* |
+| `watch_deployment` | Monitor deployment in real-time | *"Watch my deployment progress"* |
+| `compare_deployments` | Compare recent deployments | *"Compare my last 2 deployments"* |
+| `get_deployment_logs` | Fetch deployment logs | *"Show me deployment logs"* |
 
-```bash
-# Clone the repository
-git clone https://github.com/alexpota/deploy-mcp.git
-cd deploy-mcp
+### Platform-Specific Usage
 
-# Install dependencies
-npm install
+Commands work across all configured platforms:
 
-# Run in development mode  
-npm run dev
+```
+"Check my Vercel deployment for my-app"
+"Check my Netlify deployment for my-site"
+"Show me logs for deployment abc123 on Vercel"
+"Watch my Netlify deployment progress"
 ```
 
-### Testing
+The AI will automatically use the correct platform based on:
+1. Explicit platform mention in your command
+2. Project/site name matching
+3. Available tokens in configuration
 
-```bash
-# Run tests
-npm test
+## Security
+─────────────────────────
 
-# Type checking
-npm run lint
-```
+- **Local tokens only** - Your API tokens stay on your machine
+- **No telemetry** - We don't track usage or collect data
+- **Open source** - Fully auditable codebase
+- **Minimal permissions** - Only read access required
 
-### Building & Deployment
+## Advanced Configuration
+─────────────────────────
 
-```bash
-# Build TypeScript
-npm run build
+### Environment Variables
 
-# Deploy worker to Cloudflare
-npm run deploy
+You can also set tokens via environment variables:
 
-# Development worker server
-npm run dev:worker
+```bash
+export VERCEL_TOKEN="your-vercel-token"
+export NETLIFY_TOKEN="your-netlify-token"
+npx deploy-mcp
 ```
 
-## Project Structure
+### Custom Installation
 
-```
-deploy-mcp/
-├── src/
-│   ├── index.ts              # MCP server entry point
-│   ├── worker.ts             # Cloudflare Worker for website
-│   ├── adapters/             # Platform adapters (new structure)
-│   │   ├── base/             # Base adapter framework
-│   │   │   ├── adapter.ts    # Abstract base class
-│   │   │   ├── types.ts      # Common interfaces
-│   │   │   └── index.ts      # Base exports
-│   │   ├── vercel/           # Vercel platform support
-│   │   │   ├── index.ts      # Main adapter class
-│   │   │   ├── types.ts      # Vercel-specific types
-│   │   │   ├── api.ts        # API client
-│   │   │   └── __tests__/    # Vercel tests
-│   │   └── index.ts          # All adapter exports
-│   ├── core/
-│   │   ├── mcp-handler.ts    # MCP protocol implementation
-│   │   └── tools.ts          # MCP tool definitions
-│   ├── server/
-│   │   └── badge.ts          # SVG badge generation (v0.2.0)
-│   └── types.ts              # TypeScript definitions
-├── tests/                    # Integration tests
-├── dist/                     # Compiled output
-├── wrangler.toml            # Cloudflare config
-├── tsconfig.json            # TypeScript config
-└── package.json             # Project metadata
-```
+For production use, install globally:
 
-## Security
-
-### Our Security Commitments
-
-- **Local-Only Tokens** - Your API tokens never leave your machine
-- **No Data Collection** - We don't track, log, or store any user data
-- **Direct API Calls** - All platform APIs are called directly from your local MCP server
-- **Open Source** - Full transparency with auditable code
-- **Badge Service** - Coming in v0.2.0 with webhook-based live deployment badges
-
-### Best Practices
-
-1. **Use Read-Only Tokens** - When possible, create tokens with minimal permissions
-2. **Rotate Tokens Regularly** - Update your tokens periodically
-3. **Environment Variables** - Store tokens in environment variables, not in code
-4. **Git Ignore** - Never commit configuration files with tokens
-
-## Platform Support
-
-<table>
-  <thead>
-    <tr>
-      <th>Platform</th>
-      <th>Status</th>
-      <th>Features</th>
-      <th>Documentation</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td><strong>Vercel</strong></td>
-      <td><strong>✓ Supported</strong></td>
-      <td>Full deployment tracking with real-time status updates</td>
-      <td><a href="https://deploy-mcp.io/docs/vercel">View Guide</a></td>
-    </tr>
-    <tr>
-      <td><strong>Netlify</strong></td>
-      <td><strong>Coming Soon</strong></td>
-      <td>In active development</td>
-      <td>Coming soon</td>
-    </tr>
-    <tr>
-      <td><strong>Railway</strong></td>
-      <td><strong>Planned</strong></td>
-      <td>On the roadmap</td>
-      <td>-</td>
-    </tr>
-    <tr>
-      <td><strong>Render</strong></td>
-      <td><strong>Planned</strong></td>
-      <td>On the roadmap</td>
-      <td>-</td>
-    </tr>
-  </tbody>
-</table>
-
-Want support for another platform? [Open an issue](https://github.com/alexpota/deploy-mcp/issues/new) or submit a PR\!
+```bash
+npm install -g deploy-mcp
+deploy-mcp
+```
 
 ## Contributing
+─────────────────────────
 
-We love contributions\! Whether it's a bug fix, new feature, or platform support, we'd love to have you.
-
-### Quick Start
+We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
 
-1. Fork the repository
-2. Create your 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
+### Adding New Platforms
 
-### Adding Platform Support
-
-Want to add support for a new platform? Here's how:
-
-1. **Create an adapter folder** in `src/adapters/your-platform/`
-2. **Implement the interface**:
-   ```typescript
-   export class YourPlatformAdapter extends BaseAdapter {
-     async getDeploymentStatus(project: string, token: string) {
-       // Your implementation
-     }
-   }
-   ```
-3. **Add tests** in `src/adapters/your-platform/__tests__/`
-4. **Update docs** with setup instructions
-5. **Submit a PR** and we'll review it\!
-
-See our [Contributing Guide](CONTRIBUTING.md) for more details.
+1. Implement the `BaseAdapter` interface
+2. Add platform-specific API client
+3. Update configuration documentation
+4. Add tests
 
 ## License
+─────────────────────────
 
-This project is licensed under the Apache License 2.0 - see the [LICENSE](LICENSE) file for details.
-
-## Acknowledgments
-
-- Built with [Model Context Protocol SDK](https://github.com/modelcontextprotocol/sdk) by Anthropic
-- Hosted on [Cloudflare Workers](https://workers.cloudflare.com) for global edge performance
-- Icons from [Feather Icons](https://feathericons.com) and [Heroicons](https://heroicons.com)
+Apache 2.0 - See [LICENSE](LICENSE) for details.
 
-## Community & Support
+## Links
+─────────────────────────
 
-<div align="center">
-  <a href="https://github.com/alexpota/deploy-mcp/discussions">
-    <img src="https://img.shields.io/badge/GitHub-Discussions-181717?style=for-the-badge&logo=github" alt="GitHub Discussions" />
-  </a>
-  <a href="https://github.com/alexpota/deploy-mcp/issues">
-    <img src="https://img.shields.io/badge/Report-Issues-ff6b6b?style=for-the-badge&logo=github" alt="Report Issues" />
-  </a>
-  <a href="mailto:alex.potapenko.dev@gmail.com">
-    <img src="https://img.shields.io/badge/Email-alex.potapenko.dev@gmail.com-ff6b6b?style=for-the-badge&logo=gmail" alt="Email" />
-  </a>
-</div>
+- [Website](https://deploy-mcp.io)
+- [npm Package](https://www.npmjs.com/package/deploy-mcp)
+- [GitHub Repository](https://github.com/alexpota/deploy-mcp)
+- [Report Issues](https://github.com/alexpota/deploy-mcp/issues)
 
 ---
 
 <div align="center">
-  <p>Made with ❤️ by <a href="https://github.com/alexpota">Alex Potapenko</a> and contributors</p>
-  <p><a href="https://deploy-mcp.io">deploy-mcp.io</a> • <a href="https://github.com/alexpota/deploy-mcp">GitHub</a> • <a href="https://www.npmjs.com/package/deploy-mcp">NPM</a></p>
-</div>
-
+Made with ❤️ for developers who love AI-assisted coding
+</div>