How to Use the GitScrum Sprints MCP in Cline

Q: Can Cline automatically close tasks in GitScrum Sprints when I commit code?

Yes, Cline can read your git logs and use updatesprint or task-filtering tools to update the status in GitScrum. It matches your code changes to your active sprint board without manual input.

Q: How do I inspect specific issues in Cline?

Ask Cline to inspect a task, and it will run gettask using the UUID to pull the description and status. You get full context on any ticket without leaving your editor.

Let Cline manage your GitScrum Sprints directly inside VS Code, updating tasks and analyzing burndown charts while you write code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GitScrum Sprints MCP to Cline

Create your Vinkius account to connect GitScrum Sprints to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup GitScrum Sprints with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

End-to-End Backlog Grooming with Cline

The `list_user_stories` tool gives Cline immediate visibility into your current product backlog inside VS Code. The agent reads this list, compares it to your local files, and determines which requirements are already implemented. To keep your board fresh, Cline invokes `create_user_story` to add missing features based on your code diffs. You don't have to context-switch to a project management app just to document what you built.

Automated Sprint Status Checks via MCP Server

The `sprint_progress` tool lets Cline check the real-time completion rate of your active iteration. The agent queries this endpoint to see if pending pull requests align with your sprint goals. If Cline detects open tasks, it runs `list_tasks` with status filters to identify the exact files holding up the release. You get an actionable list of blockers right in your sidebar.

Instant Velocity Reports in VS Code

The `sprint_metrics` tool delivers deep analytical data directly to your Cline agent. Cline parses these metrics to show you the team's historical velocity and average completion times. By calling `sprint_stats`, Cline evaluates whether your current workload matches past performance. It keeps your planning honest by flagging over-committed sprints before they start.

Setup guide

Set up GitScrum Sprints MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type gitscrum-sprints-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest GitScrum Sprints refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "gitscrum-sprints-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GitScrum. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect GitScrum Sprints now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about GitScrum Sprints MCP in Cline

Open the Cline sidebar, click the MCP Servers icon, and add the server via the Marketplace tab. You can also edit your `cline_mcp_settings.json` file directly to configure the endpoint.

Yes, Cline can read your git logs and use `update_sprint` or task-filtering tools to update the status in GitScrum. It matches your code changes to your active sprint board without manual input.

No, the server runs in the Vinkius cloud sandbox to protect your local system resources. Cline connects to the secure endpoint, keeping your VS Code environment fast and lightweight.

Ask Cline to inspect a task, and it will run `get_task` using the UUID to pull the description and status. You get full context on any ticket without leaving your editor.

Vinkius uses ephemeral V8 sandboxes to isolate every single API call, meaning your task descriptions and user stories are never stored. Your GitScrum credentials are encrypted and passed directly to the API, maintaining a strict zero-trust boundary.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript