Testing Guide - Ameniti Hotel Booking MCP Server

Overview

This guide provides Anthropic with comprehensive testing scenarios for the Ameniti Hotel Booking MCP Server. The server operates as a remote HTTP-based MCP service that AI assistants connect to via MCP client connectors.

Remote MCP Server Access

Production MCP Endpoint

  • MCP Server URL: https://hotel.ameniti.ai/mcp
  • Protocol: HTTP POST with MCP JSON-RPC format
  • Environment: Production service with test mode enabled
  • Authentication: OAuth 2.1 required for all tools
  • OAuth Metadata: https://hotel.ameniti.ai/.well-known/oauth-protected-resource/mcp

MCP Client Configuration

To test with an MCP client, configure with OAuth authentication:

{
  "mcpServers": {
    "ameniti-booking": {
      "command": "npx",
      "args": [
        "@modelcontextprotocol/server-fetch",
        "https://hotel.ameniti.ai/mcp"
      ],
      "env": {
        "OAUTH_TOKEN": "<your-oauth-bearer-token>"
      }
    }
  }
}

OAuth Authentication Setup

Before testing, obtain an OAuth 2.1 bearer token:

  1. Contact support@ameniti.ai for OAuth credentials
  2. Implement OAuth 2.1 flow using the metadata endpoint
  3. Include bearer token in Authorization header for all MCP requests
  4. All tools (get_price, get_rooms, setup_booking, cancel_booking) require authentication

Required Environment Variables

For OAuth authentication setup, configure these environment variables:

# OAuth Authentication Configuration
OAUTH_AUTHORIZATION_SERVER=<your-authorization-server-url>
OAUTH_RESOURCE_NAME=<your-resource-identifier>
OAUTH_RESOURCE_DOCS_URL=<your-resource-documentation-url>

# Optional - Development Mode
NODE_ENV=development  # Bypasses OAuth for local testing

Contact support@ameniti.ai for the specific values for your OAuth configuration.

🛠️ Development Mode

For local development and testing:

  • Authentication is automatically bypassed when NODE_ENV=development
  • No OAuth tokens required for local testing
  • Production environment always enforces OAuth authentication
  • This allows developers to test MCP functionality locally without OAuth setup

Support for Testing

Contact Information

Response Times

  • Critical Issues: 2-4 hours
  • General Questions: 24 hours
  • Test Access Requests: 48 hours

This testing framework ensures comprehensive verification of the remote MCP server functionality through both natural language interactions.