Abscissa vs Gitlab Public

A side-by-side look at the Abscissa and Gitlab Public MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Abscissa logoAbscissaWorkplace & Productivity · Local subprocess (stdio)Safety-aware MCP server for Linear issues, projects, cycles, and dependencies.53GoodAuth: not declaredGitlab Public logoGitlab PublicVersion Control · Local subprocess (stdio)GitLab Public MCP — wraps the GitLab REST API v4 (public endpoints, no auth)60GoodAuth: not declared

Verdict: choose Abscissa for workplace & productivity work as a local process; choose Gitlab Public for version control as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Abscissa logoChoose 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.
Explore Abscissa

Gitlab Public logoChoose Gitlab Public when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search_projects, get_project, search_issues.
Explore Gitlab Public

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAbscissa logoAbscissaGitlab Public logoGitlab Public
CategoryWorkplace & ProductivityVersion Control
Quality signal53/100 · Good60/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsLINEAR_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars11
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools423

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

Gitlab Public tools 3

  • search_projectsSearch public GitLab projects by keyword, sorted by popularity. Returns project ID, name, description, star count, fork count, open issues, and web URL.
  • get_projectGet full details for a public GitLab project by numeric ID or "namespace/project" path (e.g., "gitlab-org/gitlab"). Pass the path as written, with a plain slash — do not URL-encode it, the tool handles that internally. Returns name, description, stars, forks, default branch, topics, and last activity date.
  • search_issuesSearch issues across public GitLab projects by keyword. Returns issue title, state, author, labels, project ID, and direct URL.

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "abscissa": {
      "command": "uvx",
      "args": [
        "abscissa"
      ],
      "env": {
        "LINEAR_API_KEY": "YOUR_LINEAR_API_KEY_HERE"
      }
    }
  }
}

Gitlab Public

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gitlab-public": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-gitlab-public"
      ]
    }
  }
}

Frequently asked questions

Abscissa is categorized under Workplace & Productivity and uses a local stdio subprocess. Gitlab Public belongs to Version Control and uses a local stdio subprocess. Pick Abscissa for workplace & productivity work and Gitlab Public for version control.

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. Gitlab Public 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 gitlab-public 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. Gitlab Public has 60/100 (Good) with 3 views, 0 installs and 1 GitHub stars.