Abscissa vs Harvest MCP Server
A side-by-side look at the Abscissa and Harvest MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Abscissa for workplace & productivity work as a local process; choose Harvest MCP Server for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Abscissa when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
LINEAR_API_KEY. - You want tools like
get_current_user, create_issue, update_issue.
Choose Harvest MCP Server when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
HARVEST_ACCESS_TOKEN, HARVEST_ACCOUNT_ID.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 53/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | LINEAR_API_KEY | HARVEST_ACCESS_TOKENHARVEST_ACCOUNT_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 8 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 42 | Not listed |
| Full listing | View Abscissa | View Harvest MCP Server |
Tools & capabilities
Abscissa tools 42
get_current_userReturn the authenticated Linear user behind the configured API key.create_issueCreate a new Linear issue. team_id accepts a team UUID or key (for example, ART). Priority is 0=none, 1=urgent, 2=high, 3=normal, or 4=low.update_issueUpdate an existing Linear issue. Use a UUID or identifier such as ART-5.set_issue_projectAdd an issue to a Linear project. Args: issue_id: Issue UUID or identifier such as ABS-1. project_id: Project UUID.remove_issue_from_projectRemove an issue from its current Linear project.search_issuesSearch Linear issues with filters. Pass next_cursor as cursor for the next page.get_user_issuesGet a user's assigned issues; omit user_id to retrieve the authenticated user's issues.add_commentAdd a markdown comment to a Linear issue.assign_issueAssign a user to an issue.get_issueGet full issue details, including comments, labels, assignee, and dates.delete_issueDelete an issue permanently. Set confirm=true only after explicit user confirmation.archive_issueArchive an issue. Set confirm=true only after explicit user confirmation.- +30 more on the listing page
Harvest MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Abscissa
{
"mcpServers": {
"abscissa": {
"command": "uvx",
"args": [
"abscissa"
],
"env": {
"LINEAR_API_KEY": "YOUR_LINEAR_API_KEY_HERE"
}
}
}
}
Harvest MCP Server
{
"mcpServers": {
"ianaleck-harvest-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ianaleck/harvest-mcp-server"
],
"env": {
"HARVEST_ACCESS_TOKEN": "YOUR_HARVEST_ACCESS_TOKEN_HERE",
"HARVEST_ACCOUNT_ID": "YOUR_HARVEST_ACCOUNT_ID_HERE"
}
}
}
}
Frequently asked questions
Abscissa is categorized under Workplace & Productivity and uses a local stdio subprocess. Harvest MCP Server belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Abscissa for workplace & productivity work and Harvest MCP Server for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Abscissa has no declared pricing — check the project's own site. Harvest MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add abscissa and ianaleck-harvest-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Abscissa has a quality signal of 53/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Harvest MCP Server has 52/100 (Good) with 4 views, 0 installs and 8 GitHub stars.