From 00216ae8345d0afc780c4d9d4f5015a77b0de564 Mon Sep 17 00:00:00 2001 From: Suriyakumarvijayanayagam Date: Thu, 13 Aug 2026 13:29:34 +0530 Subject: [PATCH] Point the docs at the real API domain, mcp.nearle.ai.in The deployment landed on mcp.nearle.ai.in, not the mcp.catalogue.nearle.ai.in these references were written against. Only comments, README and .env.example are affected - nothing reads the hostname at runtime - but a wrong host in the connection snippet is a wrong host somebody pastes into an MCP client. API_CORS_ORIGINS is unchanged: it takes the FRONTEND's origin (catalogue.nearle.ai.in), not the API's, so moving the API does not affect it. Co-Authored-By: Claude Opus 5 (1M context) --- .env.example | 2 +- README.md | 2 +- app/main.py | 2 +- app/mcp_server.py | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.env.example b/.env.example index 4073af1..3f239b1 100644 --- a/.env.example +++ b/.env.example @@ -65,7 +65,7 @@ # credentials off if it sees one, so a wildcard silently breaks every call). # # Production - the React app is served from catalogue.nearle.ai.in and calls -# the API at mcp.catalogue.nearle.ai.in, so that frontend origin must be listed: +# the API at mcp.nearle.ai.in, so that frontend origin must be listed: # # API_CORS_ORIGINS=https://catalogue.nearle.ai.in # diff --git a/README.md b/README.md index 6324698..393c018 100644 --- a/README.md +++ b/README.md @@ -92,7 +92,7 @@ long-running client has to refresh. Raise the TTL if that is a problem. "mcpServers": { "nearle-catalogue": { "type": "http", - "url": "https://mcp.catalogue.nearle.ai.in/mcp", + "url": "https://mcp.nearle.ai.in/mcp", "headers": { "Authorization": "Bearer " } } } diff --git a/app/main.py b/app/main.py index b565c4b..cb91a77 100644 --- a/app/main.py +++ b/app/main.py @@ -175,7 +175,7 @@ if _mcp_app is not None: # Serve built frontend static files if dist exists (single-port unified # deployment). Off in the normal setup: the React app is served by its own # nginx on catalogue.nearle.ai.in and this API answers on -# mcp.catalogue.nearle.ai.in, so no dist/ is present here and the JSON root +# mcp.nearle.ai.in, so no dist/ is present here and the JSON root # handler at the bottom of this file is what responds to /. # # The candidates cover both repo layouts - the sibling checkout is named diff --git a/app/mcp_server.py b/app/mcp_server.py index 06df29f..f8bb094 100644 --- a/app/mcp_server.py +++ b/app/mcp_server.py @@ -2,7 +2,7 @@ MCP server exposing the catalog as tools for AI clients. Mounted onto the FastAPI app at /mcp (see app/main.py), so it ships in the same -container and answers on the same host - mcp.catalogue.nearle.ai.in/mcp. +container and answers on the same host - mcp.nearle.ai.in/mcp. Scope: reads only. Every tool here maps to a service function the REST API already exposes through a GET. None of the write or compute endpoints - catalog