fizzy-mcp
by procube-cx
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP/SSE transport, default: 3000 | 3000 |
| LOG_LEVEL | No | Logging level: debug, info, warn, error. Default: info | info |
| MCP_TRANSPORT | No | Transport mode: stdio, sse, or http. Default: stdio | stdio |
| FIZZY_BASE_URL | No | Fizzy API base URL, default: https://app.fizzy.do | https://app.fizzy.do |
| MCP_AUTH_TOKEN | No | Optional bearer token for client authentication (authenticates MCP clients connecting to this server) | |
| FIZZY_ACCESS_TOKEN | No | Your Fizzy API access token. Required for stdio transport only. | |
| MCP_ALLOWED_ORIGINS | No | Allowed CORS origins (comma-separated or * for all), default: * | * |
| MCP_BIND_ALL_INTERFACES | No | Set to true to bind to 0.0.0.0 instead of localhost, 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
- 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/procube-cx/fizzy-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server