Publishing to the connector directories

Submission to both directories is a manual form. This page holds the details to paste and the state of each prerequisite, so the form can be filled in one sitting.

Endpoints

Environment	Hostname	Container app
dev	https://mcp-qa.elivaas.com/mcp — live, managed certificate bound	bard-mcp in RG dev
prod	https://mcp.elivaas.com/mcp	bard-mcp in RG bard-prod-rg

Testing runs against dev. The directory submission should carry the prod hostname, for one reason worth being blunt about: a directory entry pins the URL it is given, and there is no way to reach the people who already installed a connector to tell them it moved. Submitting mcp-qa now would mean either living with a QA hostname as the public entry point forever, or re-submitting and abandoning every existing install.

Adding a connector by URL under Settings → Connectors has no such constraint, so mcp-qa is the right host for trying it out and showing it to people ahead of the listing.

Transport is Streamable HTTP, stateless, no authentication. Discovery is open by design — the connector reads a curated channel and hands off to elivaas.com to book.

Never publish the raw Azure hostname

blackriver-831938f9 and nicewave-abbaa2f1 are Azure-generated environment labels. If an environment is ever recreated the label changes, and every install pointing at it breaks silently.

DNS

Both hostnames need two Cloudflare records. The verification id is scoped to the subscription, so the same value serves both:

Environment	Type	Name	Content
dev	TXT	asuid.mcp-qa	DC3847C6C2A75DB115C9F958775BD7996AF5F33D6EACF59595BA1A832686BD31
dev	CNAME	mcp-qa	bard-mcp.blackriver-831938f9.centralindia.azurecontainerapps.io
prod	TXT	asuid.mcp	DC3847C6C2A75DB115C9F958775BD7996AF5F33D6EACF59595BA1A832686BD31
prod	CNAME	mcp	bard-mcp.nicewave-abbaa2f1.centralindia.azurecontainerapps.io

All four DNS-only, never proxied. Azure validates by fetching the hostname directly, and Cloudflare's proxy terminates TLS with its own certificate — an orange-clouded record fails validation and then fails again at certificate issuance. It is the usual way this step goes wrong.

Once the records resolve, run the Bind MCP custom domain workflow, which binds the hostname, issues the managed certificate and verifies with a real tools/list call over the new name.

Listing details

Name — Elivaas

One line — Luxury villa stays across India, searched and compared in the chat.

Description

Find an Elivaas villa without leaving the conversation. Search luxury villas across Goa, the Himalayas, Rajasthan and more by dates, party size, bedrooms and facilities, compare them side by side with photographs and real prices for your dates, and ask anything about a property — what it sleeps, what it costs, which dates are still open. Booking completes on elivaas.com.

Tools shown to the user

Tool	Permission group	What the user sees
search_stays	Interactive	Find and compare villas on Elivaas
view_property	Interactive	Open one villa in a detail card
ask_about_properties	Read-only	Answer questions about villas by their ids

Privacy policy — https://www.elivaas.com/explore/privacy-policy

Terms — https://www.elivaas.com/explore/terms-and-conditions

Prerequisites

	State
Connector live and answering	Ready — dev runs the current build
Three tools published, two UI-bearing	Ready
Privacy and terms pages	Ready, both in the sitemap
Custom domain (dev)	Ready — mcp-qa.elivaas.com bound, SNI enabled, verified with a live tools/list
Custom domain (prod)	Missing — records not created, and prod has nothing to point at
Icon	Missing — see below
ChatGPT plan	Blocked on Free — connectors need Plus or above

Icon

Both directories want roughly a square 512×512 PNG or an SVG, and render it at around 40px in the connector list. Two Elivaas assets exist and neither is quite right:

The Signature wordmark (Black_Signature_logo_1_6a498c211e.png, 325×142) squares up cleanly enough, but it is a wordmark: at 40px the script "signature" becomes an unreadable smudge and the square is mostly empty. It works as a fallback, not as a good icon.

The favicon monogram — the geometric house mark at d4b28jbnqso5g.cloudfront.net/faviconelivaas_dbf00961c0.ico — is exactly the right kind of mark for an icon: one shape, legible at any size. It only exists at 48×48, and upscaling hard-edged geometry from 48px looks visibly blocky.

So the ask is a high-resolution export of the monogram, ideally SVG, from the brand source. Until then the squared wordmark is the usable option.

Prod is not deployed

bard-mcp in bard-prod-rg is still running mcr.microsoft.com/k8se/quickstart:latest — the bootstrap image it was created with. Prod is not running the connector at all, so mcp.elivaas.com has nothing to point at until the main deploy runs.

Submitting

Claude — the directory takes submissions through the developer form at claude.ai/directory; supply the endpoint, name, description, icon and the two policy URLs. Anyone can already add it by URL under Settings → Connectors without waiting for the directory listing, which is the faster way to get it in front of people.

ChatGPT — apps are submitted through the Apps SDK developer flow. The connector already carries the openai/outputTemplate alias next to the MCP Apps key, so the same server renders in both. Adding a connector at all requires Plus or above; on a Free account the option is not offered.

Known limitations to declare

State these in the submission rather than letting a reviewer find them:

• Booking links resolve to a 404 page. Links are built as /villa/{listingId}, but the site routes villas by slug. The site is a single-page app, so the URL returns HTTP 200 and then renders "Not Found" — which means no automated check catches it. Accepted for now as a known gap.
• bedrooms reads 0 on search results.
• Prices are INR only, and the connector sells one curated channel rather than the whole catalogue.