wafle MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (default info) | info |
| WAFLE_API_KEY | Yes | Your wafle admin key (required) | |
| WAFLE_API_URL | No | The wafle API URL (default: https://wafle.click/wp-json/waffle/v1) | https://wafle.click/wp-json/waffle/v1 |
| WAFLE_MCP_TOKENS | No | Comma-separated bearer tokens for legacy admin-tier auth (fallback when REQUIRE_JWT is unset) | |
| WAFLE_TIMEOUT_MS | No | Timeout in milliseconds for API calls (optional, default 30000) | 30000 |
| WAFLE_MCP_HTTP_HOST | No | Host for HTTP transport (only used with --transport=http, default 0.0.0.0) | 0.0.0.0 |
| WAFLE_MCP_HTTP_PORT | No | Port for HTTP transport (only used with --transport=http, default 7100) | 7100 |
| WAFLE_MCP_JWT_SECRET | No | Shared HS256 secret for tenant-scoped JWT auth (recommended, generate with openssl rand -hex 64) | |
| WAFLE_MCP_REQUIRE_JWT | No | Set to '1' to refuse legacy bearer tokens in production |
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
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/the33warehouse-tech/wafle-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server