2,500+ MCP servers ready to use
Vinkius

GitScrum Tasks MCP Server for AutoGen 28 tools — connect in under 2 minutes

Built by Vinkius GDPR 28 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add GitScrum Tasks as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="gitscrum_tasks_agent",
            tools=tools,
            system_message=(
                "You help users with GitScrum Tasks. "
                "28 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())
GitScrum Tasks
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About GitScrum Tasks MCP Server

What you can do

  • Full task lifecycle — create, update, delete, and toggle completion on tasks with rich metadata including types, effort levels, and dates
  • Advanced filtering — query tasks by status, sprint, user story, assignee, label, type, effort, workflow column, blocker flag, and date ranges
  • Subtask management — list, link, unlink subtasks and discover related tasks across your project
  • Checklists — add checklist items with sub-items and toggle completion for granular progress tracking
  • Team coordination — assign and unassign members, duplicate tasks, move between projects, and set story points
  • Comments — list, create, update, and delete task comments for rich collaboration context

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use GitScrum Tasks tools. Connect 28 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

The GitScrum Tasks MCP Server exposes 28 tools through the Vinkius. Connect it to AutoGen in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect GitScrum Tasks to AutoGen via MCP

Follow these steps to integrate the GitScrum Tasks MCP Server with AutoGen.

01

Install AutoGen

Run pip install "autogen-ext[mcp]"

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

04

Explore tools

The workbench discovers 28 tools from GitScrum Tasks automatically

Why Use AutoGen with the GitScrum Tasks MCP Server

AutoGen provides unique advantages when paired with GitScrum Tasks through the Model Context Protocol.

01

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use GitScrum Tasks tools to solve complex tasks

02

Role-based architecture lets you assign GitScrum Tasks tool access to specific agents. a data analyst queries while a reviewer validates

03

Human-in-the-loop support: agents can pause for human approval before executing sensitive GitScrum Tasks tool calls

04

Code execution sandbox: AutoGen agents can write and run code that processes GitScrum Tasks tool responses in an isolated environment

GitScrum Tasks + AutoGen Use Cases

Practical scenarios where AutoGen combined with the GitScrum Tasks MCP Server delivers measurable value.

01

Collaborative analysis: one agent queries GitScrum Tasks while another validates results and a third generates the final report

02

Automated review pipelines: a researcher agent fetches data from GitScrum Tasks, a critic agent evaluates quality, and a writer produces the output

03

Interactive planning: agents negotiate task allocation using GitScrum Tasks data to make informed decisions about resource distribution

04

Code generation with live data: an AutoGen coder agent writes scripts that process GitScrum Tasks responses in a sandboxed execution environment

GitScrum Tasks MCP Tools for AutoGen (28)

These 28 tools become available when you connect GitScrum Tasks to AutoGen via MCP:

01

assign_member

Assign a user to a task

02

create_checklist_item

Use parent_id to create sub-items. Add a checklist item to a task

03

create_comment

Supports rich text content. Add a comment to a task

04

create_task

Create a new task

05

create_task_type

g., Chore, Tech Debt) with a hex color code. Create a new task type

06

delete_comment

Delete a comment

07

delete_task

This action cannot be undone. Delete a task permanently

08

duplicate_task

Duplicate a task

09

get_task

Get task details by UUID

10

get_task_by_code

g., WEB-42) instead of UUID. Get task by human-readable code

11

link_subtask

Link an existing task as a subtask

12

list_checklists

List checklists on a task

13

list_comments

Comments support rich text. List comments on a task

14

list_effort_levels

List effort/priority levels

15

list_subtasks

List subtasks of a task

16

list_task_types

) with their colors. List task types in a project

17

list_tasks

Filter by status (todo, in-progress, done), sprint, user_story, users, labels, type, effort, workflow, is_blocker, is_archived, unassigned, created_at (YYYY-MM-DD=YYYY-MM-DD), closed_at, per_page. List tasks with advanced filters

18

move_task_to_project

Move a task to a different project

19

my_tasks

Get all tasks assigned to me

20

my_today_tasks

Get tasks due today

21

related_tasks

Get tasks related to a task

22

set_task_estimate

Set story points / estimate for a task

23

toggle_checklist_item

Toggle a checklist item done/undone

24

toggle_task_done

Toggle task completion status

25

unassign_member

Remove a user from a task

26

unlink_subtask

Unlink a subtask

27

update_comment

Edit an existing comment

28

update_task

Update an existing task

Example Prompts for GitScrum Tasks in AutoGen

Ready-to-use prompts you can give your AutoGen agent to start working with GitScrum Tasks immediately.

01

"Show me all in-progress tasks in the web-app project."

02

"Create a bug task 'Login timeout on slow connections' in web-app and assign it to janedoe."

03

"Add a checklist to task WEB-42 with items for 'Write unit tests', 'Update docs', and 'Deploy to staging'."

Troubleshooting GitScrum Tasks MCP Server with AutoGen

Common issues when connecting GitScrum Tasks to AutoGen through the Vinkius, and how to resolve them.

01

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

GitScrum Tasks + AutoGen FAQ

Common questions about integrating GitScrum Tasks MCP Server with AutoGen.

01

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call GitScrum Tasks tools during their conversation turns.
02

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.
03

Does AutoGen support human approval for tool calls?

Yes. Configure human-in-the-loop mode so agents pause and request approval before executing sensitive MCP tool calls.

Connect GitScrum Tasks to AutoGen

Get your token, paste the configuration, and start using 28 tools in under 2 minutes. No API key management needed.