Skip to content

These environment variables configure your MCP server (resource server), so it can use the Aembit MCP Authorization Server. Use these environment variables to configure your MCP server and not the Aembit-hosted MCP Authorization Server.

The following environment variables configure your MCP server to work with the Aembit MCP Authorization Server.

Default - 0.0.0.0

The network interface address your MCP server binds to.

Example:
0.0.0.0


Default - 8000

The port your MCP server listens on.

Example:
8000


Default - not set

The public URL of your MCP server. OAuth callbacks and token audience validation use this URL. It must match the URL that MCP clients use to connect to your server and the Server Workload configuration in Aembit.

See URL configuration alignment for details on ensuring your URLs match correctly.

Example:
http://localhost:8000


AEMBIT_MCP_AUTH_SERVER Required

Section titled “AEMBIT_MCP_AUTH_SERVER ”

Default - not set

The URL of the Aembit MCP Authorization Server for your tenant. This URL uses the .mcp. subdomain.

You can find this URL in the Aembit MCP Authorization Server URL field when you configure a Server Workload with the MCP application protocol.

Example:
https://abc123.mcp.useast2.aembit.io


Default - not set

The token issuer URL used during JWT verification. This URL uses the .id. subdomain, not the .mcp. subdomain.

See Tenant URL patterns for details on Aembit subdomain usage.

Example:
https://abc123.id.useast2.aembit.io


Default - not set

The JSON Web Key Set (JWKS) endpoint for token signature verification. Your MCP server uses this endpoint to retrieve the public keys needed to validate access tokens issued by the Aembit MCP Authorization Server.

Example:
https://abc123.mcp.useast2.aembit.io/.well-known/openid-configuration/jwks

For an example of how to use these environment variables in a Python MCP server, see Test with a demo MCP server in the setup guide.