generator-app-remote -generic

This MCP server template is designed to help you deploy an Adobe MCP (Model Context Protocol) server onto Adobe I/O Runtime. It leverages the official MCP TypeScript SDK to provide Tools, Resources, and Prompts endpoints that other AI assistants can call through the MCP protocol. After deploying, you can connect clients such as Cursor or Claude Desktop to your deployed MCP server by pointing them at the provided runtime URL. The server exposes a structured interface for interactive functions (Tools), static content access (Resources), and reusable prompt templates (Prompts), all with type-safe validation via Zod and production-ready error handling and CORS protection.

To use it in Claude Desktop or similar clients, configure your mcpServers entry to run the MCP server via npx mcp-remote with the server URL. For Cursor, use the URL-based configuration with the provided web endpoint. Once configured, you can invoke the server’s Tools (e.g., echo, calculator, weather) to perform dynamic operations, fetch static Resources, and apply reusable Prompts with parameterized inputs to generate consistent responses.

Prerequisites

• Node.js 18+ (LTS)
• npm (comes with Node.js)
• Adobe I/O CLI: npm install -g @adobe/aio-cli
• Access to an Adobe I/O Runtime-enabled project (for deployment)

Installation steps

1. Install the generator package globally or use npx to scaffold a new project (examples assume npm package name from the template):

   npm install -g @adobe/generator-app-remote-mcp-server-generic

2. Scaffold a new MCP server project using the generator (follow prompts in your terminal):

   aio app init

   Note: You may be prompted to select the generic MCP server template and provide project name and configuration details.

3. Install dependencies and run tests (within the generated project directory):

   npm install npm test npm run e2e

4. Deploy to Adobe I/O Runtime

   • Configure your Adobe I/O Runtime project (workspace.json) with the necessary credentials
   • Deploy the app using the Adobe I/O CLI as described in the template’s Quick Start:

   cd my-mcp-server aio app use <your-workspace-config.json> aio app deploy

5. Run the MCP server remotely via npx (example usage):

   npx mcp-remote https://<runtime-endpoint>/api/v1/web/<workspace>/mcp-server

6. Validate the deployment by issuing a test prompt or integration call to verify Tools, Resources, and Prompts are functioning.

Tips and common considerations:

• Replace placeholder URLs with your actual Adobe I/O Runtime endpoint and workspace path after deployment.
• The server exposes Tools (interactive functions like echo, calculator, weather), Resources (static content), and Prompts (templates with parameters). Ensure your API surface is properly documented for client integrations.
• For Claude Desktop configuration, you typically point the client to the npx-based command that resolves to your remote MCP server.
• If you encounter CORS or authentication issues, verify that your Adobe I/O Runtime deployment is accessible from your client environment and that any required tokens or session cookies are properly configured.
• The template emphasizes Type Safety via Zod; ensure your prompts and tool inputs conform to the defined schemas to avoid runtime validation errors.