HAM
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HAM_REPO | No | The repository associated with the agent. | |
| HAM_TASK | No | The task identifier, when known. | |
| HAM_SCOPES | No | Comma-separated list of scopes for the agent (e.g., 'shared,project:ham'). | |
| HAM_THREAD | No | The thread identifier, when known. | |
| HAM_API_KEY | No | The agent's API key for authenticating with the HAM API. Required in shared-service mode. | |
| HAM_API_URL | No | The base URL of the HAM HTTP API. Required in shared-service mode. | |
| HAM_DB_HOST | No | Database host for direct DB mode. | |
| HAM_DB_NAME | No | Database name for direct DB mode. | |
| HAM_DB_PASS | No | Database password for direct DB mode. | |
| HAM_DB_PORT | No | Database port for direct DB mode. | |
| HAM_DB_USER | No | Database user for direct DB mode. | |
| HAM_PROJECT | No | The project name associated with the agent. | |
| HAM_AGENT_ID | No | The agent ID to use for the MCP agent. Defaults to the identity bound to HAM_API_KEY. | |
| HAM_MCP_USER_ID | No | The tenant/user ID to use for the MCP agent. Defaults to the identity bound to HAM_API_KEY. | |
| HAM_QKPS_ENABLED | No | Set to 'false' (default) to disable QKPS. | false |
| HAM_SINGLE_USER_ID | No | Set a single user ID for local development. | |
| HAM_LEGACY_FIELD_ENABLED | No | Set to 'false' (default) to disable legacy pickle-backed fields. | false |
| HAM_MCP_DIRECT_DB_ENABLED | No | Set to 'true' to enable legacy direct PostgreSQL mode. | false |
| HAM_TRUST_IDENTITY_HEADER | No | Set to 'true' to trust client-supplied identity headers behind an authenticated proxy. | 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/MonumentalSystems/ham'
If you have feedback or need assistance with the MCP directory API, please join our Discord server