Developer documentation

Aevah MCP connection

How licensed customers obtain and authorize a connection to their own Aevah MCP surface.

Tenant-specific

Administrator-issued, per instance

A licensed customer's Aevah administrator issues the MCP connection details for that customer's own instance. There is no shared public endpoint and no public customer directory.

The placeholder below communicates shape only. It is reserved and cannot identify or reach a customer environment.

https://your-aevah-instance.invalid/<administrator-issued-mcp-path>

Authorization required

Programmatic access uses OAuth 2.1 through the customer-authorized identity configuration. Exact issuer, audience, connection path, scopes, and credentials are supplied inside the licensed environment by an administrator.

An agent connects either as a delegated person, bounded by that person's session and permissions, or as a service agent principal with a named human owner and administrator-assigned permissions. Those contexts are never combined.

Discovery boundary

Aevah serves discovery metadata inside the licensed environment. The public website does not reveal its exact path or contents. After authorization, capability discovery returns only the tools available to the caller.