In-depth architectural comparison of the Unwritten and Gk Cli MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Unwritten
Version Control · Local stdio
Quality: 35/100 (Fair) | Auth: No auth required
Gk Cli
Version Control · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
Verdict Summary: Choose Unwritten if you need specialized Version Control tools running via a local process. Choose Gk Cli if your workspace requires Version Control integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Unwritten when:
You need dedicated capabilities in the Version Control domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Git-history hole detector: flags files and C# members that co-change with your edit but are absent
A CLI for interacting with GitKraken APIs. Includes an MCP server via gk mcp that not only wraps GitKraken APIs, but also Jira, GitHub, GitLab, and more. Works with local tools and remote services.
Unwritten is categorized under Version Control and uses a local stdio subprocess. In contrast, Gk Cli belongs to Version Control using local stdio subprocess. Select Unwritten when you need capabilities focused on version control and Gk Cli when you require tools for version control.