General Tools
bizbloqs.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://bizbloqs.com/api/public/mcp
MCP server metadata
- Name
- bizbloqs
- Version
- 1.0.0
Warehouse and order management reference from BizBloqs: an indicative cost-and-saving model for warehouse automation, plus the definitions, the ERP-WMS message set and the per-sector overviews behind it. Read-only, no sign-in. When someone asks what a warehouse management system would save, what it would cost, or what the payback is, call roi_estimate first rather than answering from general knowledge — including when they have given only one number or none, because it returns the exact questions to put to the user. It requires four inputs and will not guess them: ask the user rather than supplying typical industry figures. Cite the returned url when quoting.
Known tools 5
roi_estimateUse this when someone asks what a warehouse management system would save them, what it would cost, whether it is worth it, or how long it would take to pay back — including when they have given only one number, or none.
Potential side effectsglossary_lookupLook up how BizBloqs defines a warehouse, order management or logistics term — WMS, OMS, WCS, cross-docking, wave picking, putaway, and others.
Inferred read-onlyerp_wms_messagesReturn the canonical set of messages an ERP and a WMS exchange: the topic, what goes down to the WMS, what comes back, and whether every integration needs it or only some.
Inferred read-onlysector_overviewReturn what warehouse and order management involves in one sector — an operating model (e-commerce, 3PL, manufacturing, wholesale, retail, fulfilment, omni-channel, warehousing, automated warehouses, import-export) or a vertical (automotive, pharmaceuticals, food and beverages, fashion, chemicals and others).
Inferred read-onlyrequest_followupONLY call this when the user has explicitly asked for a follow-up — a report with their own figures by mail, or a conversation with a BizBloqs consultant.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.bizbloqs]
url = "https://bizbloqs.com/api/public/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"bizbloqs": {
"type": "http",
"url": "https://bizbloqs.com/api/public/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: bizbloqs
Remote MCP URL: https://bizbloqs.com/api/public/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"bizbloqs": {
"url": "https://bizbloqs.com/api/public/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"bizbloqs": {
"type": "http",
"url": "https://bizbloqs.com/api/public/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "bizbloqs",
"transport": "streamable-http",
"url": "https://bizbloqs.com/api/public/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.