>_ openissues
Anyone can report through your link — no account, no password, just a magic-link email. You work the issues from the web, the REST API, or your AI agent over MCP.
No password, just email — sign in with a magic link
$ man openissues
OpenIssues is a lightweight issue tracker for collecting bugs and feedback from anyone. People submit issues through a shared link — no account required, just magic-link email auth. Owners manage every issue from the web, a REST API, or natively over MCP with AI agents.
>_ why openissues
>_ the problem
Bugs and feedback scatter across email, chat, and DMs, then get lost. The usual fix — a real issue tracker — asks the people reporting to create an account first, so most of them never do. You end up chasing context instead of fixing things.
And when a report still lands in your inbox or Slack? Paste it into your AI agent — it files the issue in OpenIssues over MCP, so nothing slips through.
>_ the loop
Generate a submission link for yourself, an organization, or a single project. Send it, embed it, put it in your docs.
Anyone opens the link, writes a title — description and screenshots optional — and submits. No account, no password.
Triage, comment, and close from the web, the API, or your AI agent over MCP. Reporters follow along by magic link.
>_ their side
A reporter opens your link on their phone, writes what happened, and submits. They add an email only at the end — to follow the issue — and sign in with a magic link. That is the whole flow.
>_ your side
OpenIssues implements the Model Context Protocol directly — no wrapper, no scraping. Point any AI agent with an MCP client at your workspace and it can work your issues end to end: create, read, triage, comment, and close. The API and MCP are the product, not an afterthought.
Connect your agent →# connect once claude mcp add openissues \ --transport http \ https://openissues.app/mcp # then just ask > open an issue: "checkout 500s on Safari" ← created #128 in project “Web”
>_ not another jira
Fixed fields, three statuses — open, closed, and closed as not planned — plus projects to group issues and organizations to share them. No sprints, no boards, no forty custom fields. And because it is API-first, the whole issue workflow is available over the API and MCP too.
>_ who it's for
Freelancers and solo devs collecting reports from clients — and from themselves. One personal link, private projects, and an agent that keeps the backlog tidy while you build.
Organizations that share one workspace — invite members by email, group issues into projects, and control who sees what with per-project access.
>_ faq
Short, straight answers. Anything else — open an issue.
OpenIssues is a lightweight issue and feedback tracker. You share a link and anyone can report a bug or request — no account needed. You manage the issues from the web, a REST API, or your AI agent over MCP.
No. Reporters open your link, write a title — description and attachments are optional — and submit. They only add an email at the end so you can reach them, and they sign in with a magic link, never a password. There is nothing to install and no account to create.
Yes. Descriptions are markdown, so reporters can paste or drag images straight into the text (up to 5 MB each) and attach files up to 10 MB each. Everything is stored privately and served only through access-checked links — never public URLs.
You — the project owner — get an email notification, and the issue lands in the project its link points to. Discussion happens in markdown comments, the status moves through open, closed, or closed as not planned, and the reporter follows along through their private issue link.
OpenIssues speaks the Model Context Protocol natively. Connect any AI agent with an MCP client and it can create, read, triage, comment on, and close issues — the whole issue workflow, end to end. No plugin and no scraping; the agent is a first-class user of your workspace.
Of course. The web app covers the whole workflow — collect, triage, comment, close — and the REST API is there when you want to script it. MCP is a native option for when you want an agent involved, not a requirement.
Jira and GitHub are built for teams that already have accounts. OpenIssues is lightweight, fast, and flexible — built for collecting reports from people who do not: clients, users, yourself, all behind one link. Fixed fields, three statuses, projects. No sprints or boards, and a native API and MCP instead of add-ons.
Yes. Every issue lives behind authentication — only you and the people you invite can see it. Submission links let people add issues without seeing anyone else's. Attachments and pasted images are served through signed, access-checked routes, never public URLs.