eGordian AEO MCP Service
by ntxptrevor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to listen on (default `8080`). | 8080 |
| AUTH_MODE | No | Authentication mode: `dev` for local development, `bearer` for production. Note: `AUTH_MODE=dev` is refused when `DEPLOYMENT_ENV=production`. | |
| DATABASE_URL | No | PostgreSQL connection string. If set, uses PostgresRepository; otherwise falls back to SQLite `data.db`. | |
| DEPLOYMENT_ENV | No | Deployment environment, e.g., `production`, `preview`. Affects security restrictions. | |
| SERVICE_TOKENS | Yes | Semicolon-separated entries of the form `token|user|projects|scopes`. Required for bearer authentication (e.g., `REPLACE_TOKEN|trevor|P-1|catalogue:read,egordian:read,aeo:run,aeo:approve`). | |
| CATALOGUE_SHA256 | No | SHA256 of the plaintext catalogue (for the registry-safe variant). | |
| CATALOGUE_DB_PATH | No | Path to the immutable licensed SQLite catalogue (read-only, `immutable=1`). | |
| ALLOW_EGORDIAN_WRITES | No | Set to `true` to allow eGordian writes (default `false`). Writes also require scope and approval envelope. | false |
| ALLOW_ADMIN_OPERATIONS | No | Set to `true` to allow admin operations (default `false`). Gates endpoints like `HealthCheck/RefreshCache`. | false |
| EGORDIAN_AUTH_PROVIDER | No | eGordian authentication provider: `none`, `basic`, `bearer`, or `headers`. Defaults to `none`. | |
| CATALOGUE_DECRYPTION_KEY | No | Passphrase used to decrypt the sealed catalogue (for the registry-safe variant with `Dockerfile.registry`). | |
| ALLOW_LEGACY_2025_CLIENTS | No | Set to `true` to allow legacy 2025 clients (default `false`). | false |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ntxptrevor/egordian-aeo-runtime'
If you have feedback or need assistance with the MCP directory API, please join our Discord server