In-depth architectural comparison of the Backlog 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
Backlog MCP
Workplace & Productivity · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Harvest MCP Server
Workplace & Productivity · Local stdio
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose Backlog 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 Backlog MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
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.
MCP server that gives AI agents structured read/write access to a story-based project backlog. Agents can list stories, read content, update status, and append notes — all backed by plain markdown files versioned in your repository.
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
Backlog MCP Tools (15)
list_stories
List stories, optionally filtered by `epic_id`, `status`, or `story_type
get_story
Get full markdown content and metadata for a story, including `story_type
get_index_summary
High-level epic/story counts by status
create_epic
Create a new epic — assigns next EPIC-NNN ID, writes epic file, registers in index
create_story
Create a new story under an epic — assigns next STORY-NNN ID, registers in index and backlog
set_epic_status
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).
Backlog 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 Backlog MCP when you need capabilities focused on workplace & productivity and Harvest MCP Server when you require tools for workplace & productivity.