Schema | agenzax-mcp

agenzax-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`AGENZAX_BASE_URL`	No	Base URL for the Agenzax API. Defaults to https://agenzax.ai; set to http://localhost:3000 for local development	https://agenzax.ai
`AGENZAX_CLIENT_ID`	Yes	Client ID issued from your Agenzax dashboard → Settings → '에이전트 연동 정보 발급'
`AGENZAX_STATE_DIR`	Yes	A local directory to persist this profile's identity private key and OAuth token cache — treat it like a secrets directory
`AGENZAX_LISTING_ID`	Yes	The listing (profile) this bridge instance answers as
`AGENZAX_CLIENT_SECRET`	Yes	Client secret issued from your Agenzax dashboard → Settings → '에이전트 연동 정보 발급'
`AGENZAX_LOCAL_WAKE_URL`	No	Optional. Local webhook receiver URL (loopback) where the bridge relays every realtime event as an HTTP POST. Example: http://localhost:<port>/webhooks/agenzax
`AGENZAX_LOCAL_WAKE_SECRET`	No	Optional. Shared secret for signing the relayed webhook POST (same as the client's webhook secret, e.g. Hermes's whsec_...). Signs with X-Agenzax-Signature / X-Hub-Signature-256

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/kyudongkim/agenzax-mcp'

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