new endpoint, more ready

Author: rishimohan

CHANGELOG.md

@@ -5,6 +5,32 @@ All notable changes to the Orshot MCP Server will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.9.0] - 2025-07-05
+
+### Added
+
+- **Studio Template Name Support** - You can now reference studio templates by name instead of just numeric IDs
+- Template name resolution for all studio template operations (generate, modifications, etc.)
+- Enhanced studio template listing with detailed information including modifications, dimensions, and thumbnails
+- Improved template modification display with better formatting and examples
+- Railway deployment optimization with health check endpoint
+- Railway configuration files (`railway.toml`, `Procfile`)
+- Comprehensive Railway deployment guide (`RAILWAY.md`)
+
+### Changed
+
+- Updated studio templates endpoint to use new `/v1/studio/templates` structure
+- Enhanced `get-studio-templates` tool to show comprehensive template information
+- Improved `get-template-modifications` tool to handle new modification structure
+- Updated all generation tools to support template name resolution
+- Removed Docker support in favor of simpler Railway deployment
+- Enhanced tool descriptions to mention template name support
+
+### Removed
+
+- Docker configuration files (`Dockerfile`, `docker-compose.yml`)
+- Outdated `index_new.ts` file
+
 ## [1.8.0] - 2025-07-05
 
 ### Added

Dockerfile

@@ -0,0 +1 @@
+web: npm run start

Procfile

@@ -0,0 +1,135 @@
+# Railway Deployment Guide
+
+This guide explains how to deploy the Orshot MCP Server on Railway.
+
+## Prerequisites
+
+1. A Railway account (sign up at https://railway.app)
+2. Your Orshot API key
+
+## Deployment Steps
+
+### Method 1: Deploy from GitHub (Recommended)
+
+1. **Connect your repository to Railway:**
+
+   - Go to https://railway.app/dashboard
+   - Click "New Project"
+   - Select "Deploy from GitHub repo"
+   - Connect your GitHub account and select this repository
+
+2. **Configure environment variables:**
+
+   - In your Railway project dashboard, go to "Variables"
+   - Add the following environment variables:
+     ```
+     ORSHOT_API_KEY=your_orshot_api_key_here
+     NODE_ENV=production
+     ```
+
+3. **Deploy:**
+   - Railway will automatically build and deploy your application
+   - The build process uses the `railway.toml` configuration
+
+### Method 2: Deploy via Railway CLI
+
+1. **Install Railway CLI:**
+
+   ```bash
+   npm install -g @railway/cli
+   ```
+
+2. **Login to Railway:**
+
+   ```bash
+   railway login
+   ```
+
+3. **Initialize the project:**
+
+   ```bash
+   cd /path/to/orshot-mcp-server
+   railway init
+   ```
+
+4. **Set environment variables:**
+
+   ```bash
+   railway variables set ORSHOT_API_KEY=your_orshot_api_key_here
+   railway variables set NODE_ENV=production
+   ```
+
+5. **Deploy:**
+   ```bash
+   railway up
+   ```
+
+## Configuration
+
+### Environment Variables
+
+| Variable         | Required | Description                  | Default       |
+| ---------------- | -------- | ---------------------------- | ------------- |
+| `ORSHOT_API_KEY` | Yes      | Your Orshot API key          | -             |
+| `NODE_ENV`       | No       | Environment mode             | `development` |
+| `PORT`           | No       | Port for health check server | `3000`        |
+
+### Health Check
+
+The server includes a built-in health check endpoint at `/health` that Railway uses to monitor your deployment. This endpoint returns:
+
+```json
+{
+  "status": "healthy",
+  "service": "orshot-mcp-server",
+  "version": "1.8.0",
+  "timestamp": "2025-07-05T12:00:00.000Z"
+}
+```
+
+## Monitoring
+
+- **Logs:** View real-time logs in your Railway dashboard
+- **Metrics:** Monitor CPU, memory, and network usage
+- **Health Check:** Automatic health monitoring via `/health` endpoint
+
+## Scaling
+
+Railway automatically handles:
+
+- Auto-scaling based on traffic
+- Zero-downtime deployments
+- SSL certificate management
+- CDN integration
+
+## Troubleshooting
+
+### Common Issues
+
+1. **Build failures:**
+
+   - Check that all dependencies are listed in `package.json`
+   - Verify Node.js version compatibility (requires Node.js ≥18.0.0)
+
+2. **Runtime errors:**
+
+   - Check environment variables are set correctly
+   - Review logs in Railway dashboard
+   - Verify Orshot API key is valid
+
+3. **Health check failures:**
+   - Ensure the PORT environment variable is set
+   - Check if the health server is binding correctly
+
+### Support
+
+- Railway Documentation: https://docs.railway.app
+- Railway Community: https://discord.gg/railway
+- Orshot API Documentation: https://docs.orshot.com
+
+## Cost Optimization
+
+- Railway offers a generous free tier
+- Consider setting resource limits for cost control
+- Monitor usage in the Railway dashboard
+- Use environment-based scaling policies

RAILWAY.md

@@ -67,11 +67,34 @@ Examples:
 
 Generated images with `base64` response type are automatically displayed inline in your chat conversation!
 
+### ✨ NEW: Studio Template Name Support
+
+You can now reference studio templates by their **name** instead of just numeric IDs! This makes it much easier to work with your custom templates:
+
+```json
+// Use template name (much easier!)
+{
+  "templateId": "My Social Media Post",
+  "modifications": {
+    "headline": "Hello World!",
+    "image": "https://example.com/photo.jpg"
+  }
+}
+
+// Or still use numeric ID
+{
+  "templateId": "123",
+  "modifications": { ... }
+}
+```
+
 ### Note on Website Screenshots
 
 Website screenshots are available through the standard library templates (template ID: `website-screenshot`). Simply use the `generate-image` or `generate-image-from-library` tools with the `website-screenshot` template and provide the `websiteUrl` modification.
 
-## 🚀 Quick Start (Production)
+## 🚀 Quick Start
+
+### Local Development
 
 ```bash
 # 1. Install and build
@@ -84,7 +107,23 @@ export ORSHOT_API_KEY="your-api-key-here"
 npm start
 ```
 
-**Claude Desktop Integration:**
+### Railway Deployment (Recommended for Production)
+
+Deploy to Railway in one click:
+
+[![Deploy on Railway](https://railway.app/button.svg)](https://railway.app/template)
+
+Or manually:
+
+1. **Connect Repository:** Fork this repo and connect it to Railway
+2. **Set Environment Variables:**
+   - `ORSHOT_API_KEY`: Your Orshot API key
+   - `NODE_ENV`: `production`
+3. **Deploy:** Railway will automatically build and deploy
+
+> **📚 Complete Railway guide:** [RAILWAY.md](./RAILWAY.md)
+
+### Claude Desktop Integration
 
 ```json
 {
@@ -144,6 +183,51 @@ Add the server to your Claude Desktop configuration in `claude_desktop_config.js
 npm start
 ```
 
+## Usage Examples
+
+### Working with Studio Templates by Name
+
+```typescript
+// 1. First, get your studio templates to see available names
+await use_mcp_tool("get-studio-templates");
+
+// 2. Generate an image using template name instead of ID
+await use_mcp_tool("generate-image", {
+  templateId: "My Social Media Post",  // Use the template name!
+  modifications: {
+    headline: "Join us for the big announcement!",
+    description: "Something amazing is coming...",
+    image: "https://example.com/announcement.jpg"
+  }
+});
+
+// 3. Or use the auto-detect tool (recommended)
+await use_mcp_tool("generate-image", {
+  templateId: "Instagram Story Template",
+  modifications: {
+    profilePhoto: "https://example.com/profile.jpg",
+    username: "@myusername",
+    storyText: "Having a great day!"
+  }
+});
+```
+
+### URL Auto-Mapping for Studio Templates
+
+The server automatically maps image URLs to the correct template fields:
+
+```typescript
+// The server will automatically map these URLs to image fields
+await use_mcp_tool("generate-image", {
+  templateId: "Product Showcase",
+  modifications: {
+    productImage: "https://example.com/product.jpg",  // Will be auto-mapped
+    title: "Amazing Product",
+    price: "$29.99"
+  }
+});
+```
+
 ## Tools
 
 ### Template Discovery Tools