
Divblox MCP
io.github.divblox-groupv0.1.0Updated Oct 1, 2026
Define requirements, plan tickets and tasks, and track delivery with your Divblox projects.
Overview
AI-generated overview
Lets an assistant work with Divblox projects to define requirements, plan tickets and tasks, and track delivery.
- What it does
- Divblox MCP connects an assistant to Divblox projects so it can help define requirements, plan tickets and tasks, and track delivery. It is offered as a remote streamable HTTP endpoint, so the assistant talks to the hosted service rather than a local process. The manifest lists no tools, so the exact operations available are not documented here.
- When to use it
- Worth considering if your team already runs projects in Divblox and you want an assistant to help shape requirements, break work into tickets and tasks, and follow delivery progress. It is less relevant if you do not use Divblox.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the hosted endpoint. The manifest declares no packages, environment variables, headers, or authentication, so no local runtime or credentials are documented.
Before you install
The manifest declares no authentication, so it is unclear how access to your Divblox project data is controlled or who can reach it. Planning and tracking work may create or change tickets, tasks, and requirements in your projects. Confirm the provider's access and permission model before connecting real project data.
Installation
In SourceWeft
- Open Divblox MCP in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"divblox-mcp": {
"type": "http",
"url": "https://mcp.divblox.app/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v0.1.0LatestOct 1, 2026

