How to Use the GitScrum Knowledge MCP in Cursor

Q: How does Cursor use GitScrum Knowledge to write better code?

It reads your live documentation directly. Cursor runs getwikipage to pull down real-time specifications, ensuring the code it generates matches your team's active technical requirements instead of guessing.

Q: How do I search my team discussions inside Cursor using GitScrum Knowledge?

Your agent uses searchchannelmessages or globalsearch to query your workspaces. It finds relevant threads, pulls the text, and uses that context to write code that matches team decisions.

Q: Can Cursor track how my notes or wikis have changed over time?

Yes, the agent can check history. It uses noterevisions and wikirevisions to see what changed, helping you understand how project requirements evolved before you modify any code.

Feed live GitScrum Knowledge docs and agent notes directly into Cursor to write code against actual project specifications.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect GitScrum Knowledge MCP to Cursor

Create your Vinkius account to connect GitScrum Knowledge to Cursor 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 Knowledge with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Write code using live wiki documentation

Cursor's agent mode pulls real specifications directly from your wiki pages. The editor uses `get_wiki_page` and `list_wiki_pages` to read the exact technical requirements your team wrote, rather than relying on outdated training data or static files. When your API design changes, the agent can document the new implementation details immediately. It runs `update_wiki_page` using the MCP tool to keep your team's central docs in sync with the codebase you are actively editing.

Keep coding decisions in Cursor agent memory

Store architectural decisions right next to your code using this MCP Server. Cursor uses `create_note` and `update_note` to document why a specific design pattern was chosen, saving it directly to your GitScrum Knowledge workspace. When you open a new file, the agent uses `list_notes` to pull up previous decisions. This prevents the agent from rewriting working code or suggesting patterns your team already rejected in past discussions.

Search workspace channels from this MCP Server

Stop leaving your editor to check what your team discussed on a feature. Cursor runs `search_channel_messages` and `channel_messages` to find implementation details directly from your team's discussion channels. If the agent needs to share a code snippet or a status update, it uses `send_message` or `reply_to_message` to post directly to the right channel. This keeps your team updated without breaking your focus.

Setup guide

Set up GitScrum Knowledge MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the GitScrum Knowledge MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent GitScrum Knowledge transactions." If the MCP tools are loaded correctly, Cursor will call the GitScrum Knowledge tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "gitscrum-knowledge-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 Knowledge 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 Knowledge MCP in Cursor

It reads your live documentation directly. Cursor runs `get_wiki_page` to pull down real-time specifications, ensuring the code it generates matches your team's active technical requirements instead of guessing.

Yes, you can set it up per project. Just add the MCP configuration to `.cursor/mcp.json` in your repository root, and Cursor will load the server tools only when you are working on that specific codebase.

Your agent uses `search_channel_messages` or `global_search` to query your workspaces. It finds relevant threads, pulls the text, and uses that context to write code that matches team decisions.

Yes, the agent can check history. It uses `note_revisions` and `wiki_revisions` to see what changed, helping you understand how project requirements evolved before you modify any code.

Your credentials and channel messages are handled locally or via Vinkius's zero-trust MCP sandbox. No raw message text or API tokens are cached or exposed to external third parties.

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