@meetbot/mcp 1.1.1 → 1.1.2

package/README.md

@@ -12,7 +12,7 @@ A Model Context Protocol (MCP) server for the Meet.bot Booking Page API, enablin
 - **Health Checks**: Built-in health monitoring using the /v1/pages endpoint
 - **MCP Protocol Compliance**: Full Model Context Protocol server implementation
 - **Dual Mode Support**: Run locally (stdio) or remotely (HTTP/SSE)
-- **Production Deployed**: Live at https://meetbot-mcp-production.up.railway.app
+- **Production Deployed**: Live at https://mcp.meet.bot
 - **Production Ready**: Thoroughly tested and validated for production use
 
 ## Installation
@@ -101,12 +101,11 @@ The MCP server can be run in two modes:
 
 For local integration with AI assistants like Claude Desktop. Uses stdio transport for communication.
 
+**Note**: For stdio mode, you must call the `configure_meetbot` tool first to provide your authentication token. The server does not read environment variables.
+
 ```bash
 # Run locally
 npx @meetbot/mcp
-
-# Or with environment variable
-MEETBOT_AUTH_TOKEN="your_token" npx @meetbot/mcp
 ```
 
 ### 2. HTTP Mode (SSE Transport)
@@ -123,8 +122,12 @@ npm run start:http
 # Or with custom port
 PORT=8080 npm run start:http
 
-# Or run directly with npx
-npx meetbot-mcp-http
+# Or run directly with npx (after installing the package)
+npx --package=@meetbot/mcp meetbot-mcp-http
+
+# Or install globally first, then run
+npm install -g @meetbot/mcp
+meetbot-mcp-http
 ```
 
 #### Server Endpoints
@@ -162,9 +165,9 @@ curl -N -H "Authorization: Bearer YOUR_TOKEN" http://localhost:3000/sse
 
 **Production Testing:**
 ```bash
-# Test the live Railway deployment
+# Test the live deployment
 curl -H "Authorization: Bearer YOUR_TOKEN" \
-     https://meetbot-mcp-production.up.railway.app/health
+     https://mcp.meet.bot/health
 
 # Expected response:
 # {"status":"ok","service":"meetbot-mcp"}
@@ -174,8 +177,7 @@ curl -H "Authorization: Bearer YOUR_TOKEN" \
 
 The HTTP server can be deployed to various platforms:
 
-- **Railway**: `railway up` ✅ **Live at https://meetbot-mcp-production.up.railway.app**
-- **Fly.io**: `fly launch && fly deploy`
+- **Railway**: `railway up` ✅ **Live at https://mcp.meet.bot**
 - **Google Cloud Run**: Container-based deployment
 - **AWS App Runner**: Container-based deployment
 - **Any VPS**: Run with Node.js directly
@@ -183,7 +185,7 @@ The HTTP server can be deployed to various platforms:
 **Example: Connecting to Production**
 ```bash
 # Your MCP client should connect to:
-# https://meetbot-mcp-production.up.railway.app/sse
+# https://mcp.meet.bot/sse
 
 # With Authorization header:
 # Authorization: Bearer <your-meetbot-api-token>
@@ -209,20 +211,29 @@ This MCP server can be integrated with AI assistants like Claude, ChatGPT, and o
 
 #### Configuration Example
 
+For stdio mode, the server will start without authentication. You must call the `configure_meetbot` tool first to provide your token:
+
 ```json
 {
   "mcpServers": {
     "meetbot": {
       "command": "npx",
-      "args": ["@meetbot/mcp"],
-      "env": {
-        "MEETBOT_AUTH_TOKEN": "your_bearer_token_here"
-      }
+      "args": ["@meetbot/mcp"]
     }
   }
 }
 ```
 
+After the server starts, call `configure_meetbot` with your token:
+```json
+{
+  "name": "configure_meetbot",
+  "arguments": {
+    "authToken": "your_bearer_token_here"
+  }
+}
+```
+
 #### Available MCP Tools
 
 The server exposes 6 tools for AI assistants:
@@ -248,7 +259,7 @@ The package has been thoroughly tested and validated:
 ### Package Statistics
 
 - **Package Size**: 12.8 kB (58.0 kB unpacked)
-- **Test Coverage**: 21 passing tests
+- **Test Coverage**: 20 passing tests
 - **Dependencies**: 3 production dependencies
 - **TypeScript**: 100% type coverage
 - **Build Status**: ✅ Passing
@@ -350,22 +361,13 @@ interface Slots {
 
 ## Configuration
 
-### Environment Variables
-
-You can configure the MCP server using environment variables:
-
-```bash
-export MEETBOT_AUTH_TOKEN="your_bearer_token"
-
-# Then run the server
-meetbot-mcp
-```
-
 ### Authentication
 
 The MCP server supports Bearer Token authentication:
 
-1. **Bearer Token**: Use `authToken` for API key authentication
+1. **For Stdio Mode**: Call the `configure_meetbot` tool with your `authToken` after the server starts
+2. **For HTTP Mode**: Provide the token in the `Authorization: Bearer <token>` header for all requests
+3. **Bearer Token**: Use `authToken` for API key authentication with the Meet.bot API
 
 ## Development
 
@@ -391,24 +393,21 @@ The package includes a command-line interface for running the MCP server:
 # Install globally
 npm install -g @meetbot/mcp
 
-# Run the MCP server
+# Run the MCP server (stdio mode)
 meetbot-mcp
 
 # Or run directly with npx (no installation required)
 npx @meetbot/mcp
-```
-
-### Environment Variables
 
-You can configure the server using environment variables:
+# Run HTTP server
+meetbot-mcp-http
 
-```bash
-export MEETBOT_AUTH_TOKEN="your_bearer_token"
-
-# Then run the server
-meetbot-mcp
+# Or with custom port
+PORT=8080 meetbot-mcp-http
 ```
 
+**Note**: For stdio mode, you must call the `configure_meetbot` tool after the server starts to provide your authentication token. For HTTP mode, provide the token in the `Authorization` header.
+
 ## Error Handling
 
 The MCP server provides detailed error messages for common issues:
@@ -438,17 +437,22 @@ MIT License - see [LICENSE](LICENSE) file for details.
 
 ## Changelog
 
+### 1.1.2
+- **Production Host Update**: All docs now reference https://mcp.meet.bot
+- **Deployment Cleanup**: Removed Fly.io deployment instructions
+- **Dev Tooling**: Updated setup script and documentation for the new flow
+
 ### 1.1.1
 - **ES Module Fix**: Fixed ES module compatibility for Railway and other Node.js deployments
 - **Import Extensions**: Added proper `.js` extensions to all relative imports
-- **Live Deployment**: Successfully deployed to Railway at https://meetbot-mcp-production.up.railway.app
+- **Live Deployment**: Successfully deployed at https://mcp.meet.bot
 - **Production Validated**: Confirmed working in production environment
 
 ### 1.1.0
 - **HTTP/SSE Transport**: Added HTTP server with SSE transport for remote deployment
 - **Bearer Token Authentication**: Implemented authentication for HTTP endpoints
 - **Multi-mode Support**: Can run as local stdio server or remote HTTP server
-- **Deployment Ready**: Added Dockerfile and deployment configurations for Railway, Fly.io, etc.
+- **Deployment Ready**: Added Dockerfile and deployment configurations for Railway, Docker, GCP, AWS, etc.
 - **Health Check Endpoint**: Added `/health` endpoint for monitoring
 - **Session Management**: Proper session handling with transport cleanup
 - **Production Ready**: Complete HTTP implementation with authentication and error handling
@@ -483,7 +487,7 @@ MIT License - see [LICENSE](LICENSE) file for details.
 - **Error handling** - Robust error handling with detailed messages
 - **Authentication** - Support for bearer token authentication
 - **Health checks** - Built-in API connectivity monitoring using /v1/pages endpoint
-- **Testing** - Comprehensive test suite with 21 passing tests
+- **Testing** - Comprehensive test suite with 20 passing tests
 - **Documentation** - Complete API documentation and usage examples
 - **Functional Testing** - Verified with real MCP client requests
 - **npm Publishing** - Successfully published to npm registry

package/dist/mcp-server-http.js

@@ -12,7 +12,7 @@ export class MeetbotMCPServerHTTP {
     constructor() {
         this.server = new Server({
             name: 'meetbot-mcp',
-            version: '1.1.1',
+            version: '1.1.2',
         });
         this.setupToolHandlers();
     }

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@meetbot/mcp",
-    "version": "1.1.1",
+    "version": "1.1.2",
     "description": "Model Context Protocol (MCP) server for Meet.bot booking page API",
     "type": "module",
     "main": "dist/index.js",