Schema | Innergy MCP Gateway

Innergy MCP Gateway

Describes the environment variables required to run the server.

Name	Required	Description
`AUTH0_SCOPE`	Yes	Auth0 scope, e.g. innergy.read
`AUTH0_DOMAIN`	Yes	Auth0 domain, e.g. dev-scza6vay6a66c87e.au.auth0.com
`AUTH0_ISSUER`	Yes	Auth0 issuer, e.g. https://dev-scza6vay6a66c87e.au.auth0.com/
`AUTH0_AUDIENCE`	Yes	Auth0 audience, e.g. https://repulsive-nimble-editor.replit.app/mcp
`MCP_AUTH_TOKEN`	Yes	Bearer token required by every /mcp request.
`MCP_SERVER_URL`	Yes	Canonical public MCP URL, e.g. https://repulsive-nimble-editor.replit.app/mcp
`INNERGY_API_KEY`	Yes	Innergy API key. Never put it in source or chat.
`INNERGY_BASE_URL`	Yes	Innergy API origin, such as https://your-company-api.example.com. Do not include /api/projects.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aaronleeclarke-cmd/innergy-mcp-gateway'

If you have feedback or need assistance with the MCP directory API, please join our Discord server