An MCP server for issue trackers · v0.4

Ask your issue tracker in plain language.

Toolport is an MCP server for your issue tracker. Your agent turns a plain request into one tool call, and you see exactly what came back.

Toolport is an MCP server for your issue tracker. Your agent turns a plain request into one tool call, and you see exactly what came back.

Install, in your agent

Install prompt

Add the Toolport MCP server to Claude Code with claude mcp add toolport -- npx -y @toolport/mcp, then run /mcp to check its four tools are listed and ask me for my issue tracker token.

Paste it into Claude Code

or run it in your terminal

claude mcp add toolport -- npx -y @toolport/mcp

read-only · repo:read · ≤ 50

Demo values. Swap in your own package and token.

All install guides

Works with any MCP client

Works with any MCP client

Toolport returns issue results inside an MCP client.
Toolport returns issue results inside an MCP client.

Toolport answering inside Codex. The same server works in Claude Code, Cursor and Antigravity.

Toolport answering inside Codex. The same server works in Claude Code, Cursor and Antigravity.

One request, one call,
one result.

Toolport exposes four read-only tools. The agent picks one, fills in the parameters and gets the matching records back. Nothing is written to your tracker.

Toolport exposes four read-only tools. The agent picks one, fills in the parameters and gets the matching records back. Nothing is written to your tracker.

You asked

“Find open bugs in the SDK”

“Find open bugs in the SDK”

¹

Toolport answered · 7 open issues

Toolport answered · 7 open issues

opened

opened

#412

Retry loop continues after cancellation

2d

#412

Retry loop continues after cancellation

2d

#409

Timeout option is ignored during reconnect

4d

#409

Timeout option is ignored during reconnect

4d

#405

Empty response throws a parsing error

6d

#405

Empty response throws a parsing error

6d

#398

Request headers are lost after a redirect

9d

#398

Request headers are lost after a redirect

9d

and 3 more. Read-only: nothing was changed.

¹ the call

search_issues
  repo   "acme/sdk"
  state  "open"
  label  "bug"
  limit  50

scope repo:read · 7 returned

Four tools, all read-only.

search_issues

Find issues by state, label or milestone.

repo, state, label, milestone, limit

search_issues

Find issues by state, label or milestone.

repo, state, label, milestone, limit

get_issue

Read one issue in full: description, labels and milestone.

repo, issue_number

get_issue

Read one issue in full: description, labels and milestone.

repo, issue_number

list_labels

List the labels a repository uses.

repo, limit

list_labels

List the labels a repository uses.

repo, limit

list_milestones

List milestones and whether they’re open.

repo, state, limit

list_milestones

List milestones and whether they’re open.

repo, state, limit

Permissions

Permissions

It reads. It never writes.

Every tool runs under one scope, repo:read. Toolport can search and read issues, labels and milestones in the repositories you authorize. It can’t create, edit, comment on or close anything, so the worst a bad prompt can do is read.

Every tool runs under one scope, repo:read. Toolport can search and read issues, labels and milestones in the repositories you authorize. It can’t create, edit, comment on or close anything, so the worst a bad prompt can do is read.

repo:read is the only scope requested

≤ 50 results per call

No comments, attachments or history are returned

Revoke the token and access stops immediately

Toolport asks for read-only access to one repository.
Toolport asks for read-only access to one repository.

Run it your way

On your machine, or ours.

On your machine, or ours.

Run Toolport next to your client over stdio. Your token never leaves your machine, and you choose when to update.

Run Toolport next to your client over stdio. Your token never leaves your machine, and you choose when to update.

npx -y @toolport/mcp

MIT licence · stdio

Toolport starts locally over stdio and exposes four tools.

Hosted

Point your client at our endpoint and sign in once. We run it, update it and keep it up. It’s free while in beta.

Point your client at our endpoint and sign in once. We run it, update it and keep it up. It’s free while in beta.

https://mcp.toolport.example/mcp

streamable HTTP · OAuth sign-in

Toolport connects to a hosted MCP endpoint.

★ 2.4k stars

★ 2.4k stars

38 contributors

38 contributors

MIT licence

MIT licence

Questions

Before you install

Before you install

No. All four tools are read-only and run under repo:read. It can’t create, edit, comment on or close anything.

Issue summaries and descriptions, labels and milestones from the repositories your token can access. You choose which repositories to connect.

Search returns 20 results by default. You can raise limit to 50, or narrow the request by state, label or milestone. A truncated flag tells you when more results exist.

With self-hosting, your token stays on your machine. With the hosted server, Toolport uses it to access the repositories you authorize.

Claude Code, Codex, Cursor, Antigravity, Claude Desktop and VS Code. You can also connect an MCP-compatible client manually.

Start with one request.

Install Toolport, then ask your agent

“Find open bugs in the SDK.”

Create a free website with Framer, the website builder loved by startups, designers and agencies.