Abscissa vs Wizideo
A side-by-side look at the Abscissa and Wizideo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WizideoDeveloper Tools · Remote HTTP/SSESearch meeting transcripts, summaries and topics, and create follow-up tasks in Wizideo.17EmergingAuth: not declaredVerdict: choose Abscissa for workplace & productivity work as a local process; choose Wizideo for developer tools over a hosted endpoint. 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.
WChoose Wizideo when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Wizideo | |
|---|---|---|
| Category | Workplace & Productivity | Developer Tools |
| Quality signal | 35/100 · Fair | 17/100 · Emerging |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | LINEAR_API_KEY | None listed |
| Verified owner | Community listing |
Tools & capabilities
Abscissa tools
No tool names declared yet. Check the project README from the listing page.
Wizideo 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"
}
}
}
}
Wizideo
{
"mcpServers": {
"wizideo": {
"url": "https://wizideo.ai/en/integrations/mcp"
}
}
}
Frequently asked questions
Abscissa is categorized under Workplace & Productivity and uses a local stdio subprocess. Wizideo belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Abscissa for workplace & productivity work and Wizideo for developer tools.
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. Wizideo has no declared pricing — check the project's own site. 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 wizideo 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 35/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Wizideo has 17/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars.
