io.github.CloudCorpRecords/issueport is an MCP server that linear teams, projects, issues and comments via GraphQL, as MCP tools. Its tool list has not been published yet over stdio, requires no API key, and scores 55/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"issueport": {
"env": {
"LINEAR_API_KEY": "lin_api_..."
},
"args": [
"-y",
"@reneturcios/issueport",
"mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Linear teams, projects, issues and comments via GraphQL, as MCP tools.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@reneturcios/issueport' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @reneturcios/issueport against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
deja-vu: local memory over the session histories of forty-three coding agents.
MCP WordPress Remote proxy server
专门为 agent 打造的 agent 搜索工具,具备多语言搜索能力,覆盖中文/英文/学术/代码/购物/金融/新闻/百科。
Searchable football data provider documentation for AI coding agents. Like Context7 for football data.
MCP Security Weekly
Get CVE alerts and security updates for io.github.CloudCorpRecords/issueport and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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.
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.
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.
{
"mcpServers": {
"issueport": {
"command": "npx",
"args": ["-y", "@reneturcios/issueport", "mcp"],
"env": { "LINEAR_API_KEY": "lin_api_..." }
}
}
}
docker run -i -e LINEAR_API_KEY ghcr.io/cloudcorprecords/issueport
npm install
npm run build
npm test
MIT