The public install page
The moment you deploy an MCP server, Elva publishes a hosted, public-facing install page for it: a branded landing page where anyone can see exactly which tools your server exposes, pick their client, and connect in under a minute. Think of it as your API’s storefront for the agent era — no README to write, no onboarding doc to maintain, no “how do I connect this?” tickets.
You host nothing. Elva renders the page from your deployment and your settings, and it updates the instant either one changes.
Live at a predictable URL
Every deployment’s page is reachable the moment it goes live, at an address built from its deploymentId:
https://app.getelva.ai/mcp/:companySlug/:mcpSlug/install
Prefer something you can say out loud? Set a custom slug in the MCP settings and the same page answers at a short vanity path:
https://app.getelva.ai/mcp/:customSlug/install
What a visitor sees
The page is one scroll, ordered the way a connecting developer thinks: what is this → how do I connect → what can it do.
Section | What it shows |
Brand header | Your logo, the server's name, the live MCP endpoint with one-click copy, and a documentation button styled in your primary color |
Connect your MCP client | Six client tabs — Claude Desktop, Claude Code, Cursor, VS Code, Gemini CLI, Codex CLI — each with a numbered installation guide and copy-paste commands |
Available tools | Every exposed tool with its HTTP method, path, tag, description, and tool ID — plus live search and tag filtering |
Raw configuration | The plain |
Two details do a lot of quiet work here:
- The install steps adapt to your auth. A server configured for OAuth walks the visitor through it — run the add command, then
/mcp→ select the server → Authenticate, approve in the browser, done. A header-authenticated server shows the exact environment variables to export instead. Visitors never have to figure out which flow applies; the page already knows. - The tool list is full disclosure. Method, path, description, and tool ID for everything the server exposes — searchable and filterable by tag. A developer (or their security reviewer) sees precisely what an agent will be able to call before anything connects. That transparency is what makes the page shareable outside your team.
So the visitor’s whole journey is three moves:
1
Open the link
You share one URL — in your docs, a partner email, a launch post. No account needed to view a public page.
2
Pick a client, paste the setup
The visitor selects their client tab and runs the command or pastes the JSON, copy button included.
3
Authenticate and go
They complete the auth flow the page walked them through, their agent lists your tools, and the first call lands in your logs.
Make it yours
Admins customize the page from the MCP server’s Settings tab, under Install Page Branding. Four controls cover the whole surface:
Control | What it does |
MCP Logo | Upload an SVG, PNG, or JPG; it renders in the page header next to the server name |
Primary Color | Pick from the ten-swatch palette or use the eyedropper for any custom hex; it drives the page's accents, including the documentation button |
Documentation link | A link to your own MCP documentation, featured at the top of the page |
Documentation label | What that button says — "View Docs", "API Reference", whatever fits your voice |
Hit Customize and the change is live for everyone holding the link. The page is a live view of your settings, not a build artifact — there is no publish step, no cache to bust, no stale copy of your onboarding floating around.
Decide who sees it
The same Settings tab controls visibility, so the storefront can be as open or as gated as the API behind it:
Visibility | Who can open it | Behavior |
Public | Anyone with the link | Page and tool list load immediately. This is the default. |
Private | Anyone with the password | The page returns |
Disabled | No one | The endpoint responds with |
Private pages are password-gated, not credential-gated. A visitor enters the password once; Elva bcrypt-checks it and issues a signed install token valid for 24 hours, which unlocks the page and its tool list. The upstream API credentials your tools actually use are handled separately by the MCP gateway and never appear on this page.
This page is the distribution half of going agent-ready: the gateway makes your API safe to expose, and the install page makes it easy to adopt. Share one link and every visitor onboards themselves.
Where to go next
Connect any MCP client
The exact commands and JSON the page generates for all six clients, and what the auth headers do.
MCP insights & logs
Watch who connects after you share the link: per-agent activity, call volume, and the full call log.
On this page
- The public install page