Inkra MCP vs Harvest MCP Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Inkra MCP vs Harvest MCP Server
In-depth architectural comparison of the Inkra MCP and Harvest MCP Server 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
Inkra MCP
Workplace & Productivity · Local stdio
Quality: 40/100 (Fair) | Auth: API Key required
Harvest MCP Server
Workplace & Productivity · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Verdict Summary: Choose Inkra MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Harvest MCP Server if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Inkra MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Paid Service).
You have access to required keys: INKRA_PORT, INKRA_TOKEN.
Primary tools included: 18 MCP tools for document content, lifecycle, navigation, folder, metadata, view, and state, Live synchronization with Inkra app's document state and undo stack, Supports KaTeX and Mermaid live preview rendering.
MCP bridge for Inkra — native macOS Markdown editor (SwiftUI + AppKit, not Electron) with live KaTeX/Mermaid preview. 18 MCP tools for document editing, outline navigation, folder browsing, bookmarks, and view modes.
Harvest time tracking integration with 40+ tools for managing time entries, projects, clients, tasks, and generating time reports via the Harvest API v2
Category & Scope
Tools & Capabilities Breakdown
Inkra MCP Tools (5)
18 MCP tools for document content, lifecycle, navigation, folder, metadata, view, and state
Live synchronization with Inkra app's document state and undo stack
Supports KaTeX and Mermaid live preview rendering
Native macOS performance with SwiftUI and AppKit
Bearer token authentication for secure local HTTP communication
Harvest MCP Server Tools (5)
Complete Harvest API v2 coverage with 40+ tools
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Inkra MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Harvest MCP Server belongs to Workplace & Productivity using local stdio subprocess. Select Inkra MCP when you need capabilities focused on workplace & productivity and Harvest MCP Server when you require tools for workplace & productivity.
You have access to required keys: HARVEST_ACCESS_TOKEN, HARVEST_ACCOUNT_ID.
Primary tools included: Complete Harvest API v2 coverage with 40+ tools, Type-safe with TypeScript and Zod validation, Async/await with rate limiting and auto-retry.