A side-by-side look at the Alza MCP and SOMA Brewing Company MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
SOMA Brewing Company tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Alza MCP
No confirmed install command for Alza MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
SOMA Brewing Company
No confirmed install command for SOMA Brewing Company yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Alza MCP is categorized under E-Commerce and uses an install path we have not confirmed yet. SOMA Brewing Company belongs to E-Commerce and uses an install path we have not confirmed yet. Pick Alza MCP for e-commerce work and SOMA Brewing Company for e-commerce.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Alza MCP is listed as free. SOMA Brewing Company has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add alza-mcp and soma-brewing-company as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Alza MCP has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 82 GitHub stars. SOMA Brewing Company has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.