Back to Browse

Issueport MCP Server

Developer ToolsModerate5.6MCP RegistryLocal
Free

Server data from the Official MCP Registry

Linear teams, projects, issues and comments via GraphQL, as MCP tools.

About

Linear teams, projects, issues and comments via GraphQL, as MCP tools.

Security Report

5.6
Moderate5.6Moderate Risk

issueport is a small, clean Linear GraphQL client whose 12 tools match its stated purpose. It reads the API key from LINEAR_API_KEY, validates tool arguments with zod, and makes no network calls other than to the Linear API. The main concerns are minor: LINEAR_API_URL can redirect the API key to any host, and the package's npm scope and GitHub owner differ, so provenance should be verified. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

LINEAR_API_KEYRequired

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-issueport": {
      "env": {
        "LINEAR_API_KEY": "your-linear-api-key-here"
      },
      "args": [
        "-y",
        "@reneturcios/issueport"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

issueport

Linear teams, projects, issues and comments as MCP tools, talking to the Linear GraphQL API. issueport is a clean-room rebuild of the core subset of the Linear MCP surface, under a new name: fresh code written from Linear's public API documentation, no copied branding. The original Linear server is hosted/remote with OAuth; this rebuild is a GraphQL client for the same upstream API using an API key, and does not reproduce the hosted OAuth surface.

Tools (core subset, 12)

list_issues, get_issue, create_issue, update_issue, search_issues, list_teams, get_team, list_projects, create_project, list_comments, create_comment, archive_issue.

Not in this subset: cycles, documents, file uploads, webhooks, OAuth apps, time tracking, triage/custom workflows admin, project milestones/labels management, attachments, notifications.

Each tool is one GraphQL operation (query or mutation) posted as {query, variables}; a GraphQL errors array fails the call with the first error's message.

Setup

export LINEAR_API_KEY=lin_api_...

Note: Linear API keys are sent raw as the Authorization header value — not as a Bearer token. Optionally override the endpoint with LINEAR_API_URL (default https://api.linear.app/graphql). Without the key, every tool call fails with an error naming the missing variable.

CLI

npx @reneturcios/issueport get_issue '{"issue_id":"..."}'
npx @reneturcios/issueport mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "issueport": {
      "command": "npx",
      "args": ["-y", "@reneturcios/issueport", "mcp"],
      "env": { "LINEAR_API_KEY": "lin_api_..." }
    }
  }
}

Docker

docker run -i -e LINEAR_API_KEY ghcr.io/cloudcorprecords/issueport

Development

npm install
npm run build
npm test

License

MIT

Reviews

No reviews yet

Be the first to review this server!