Niches · Work & productivity

File a new issue from a conversation or report

Two or three companies' docs show a full fit.

2companies, full fit
1companies, fit with a limit
7companies carry the tag
10share of the category's work
3first-hand accounts

What counts as done

One issue per item created in the right team or project with title, description, labels and assignee set, returned with its key and URL.

Measured, for our own tests: one call per issue or one bulk call. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: file a bug for this, create a ticket from what we just discussed, log this in Linear, open an issue for each of these

Does the job 2

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Linear MCP C
Linear Orbit, Inc.
The MCP creates issues in a team, and acc-08 and acc-10 file issues from a conversation through it. Standard remote MCP with OAuth lets any compliant client connect, and the readonly endpoint shows write is a separate grant. source
Notion MCP B
Notion Labs, Inc.
notion-create-pages creates one or more pages in a data source with properties in one call and returns the saved properties, with warnings when a property key is repaired. source

Does the job, with a limit 1

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Atlassian Rovo MCP Server C
Atlassian Pty Ltd
createJiraIssue files one issue per call, which the success criterion allows. The default tool list costs 27,650 tokens (acc-31), the named blocker for small models, and acc-28 saw every Jira tool return 401 with a scoped API token. source

Doesn't do this job 5

Listings in the category that do something else, with the reason.

ListingWhy
Mattermost C
Mattermost, Inc.
No issue or ticket endpoint exists in the API; filing would go to another tracker. source
Microsoft Teams (Microsoft Graph) D
Microsoft Corporation
No issue or ticket resource exists in the Teams API. source
Outline D
General Outline, Inc.
No issue or ticket resource exists in the API. source
Slack MCP Server (official) B
Slack Technologies, LLC (a Salesforce company)
No issue tracker is exposed; filing would go to another tool, though Slack lists can hold rows. source
Zulip C
Kandra Labs, Inc.
No issue or ticket resource exists in the API. source

What stops agents finishing

  • MCP client not on the vendor's allowlist
  • tool list too large for a small model's context

Around it

Before: productivity.read-channel, support.read-ticket. After: productivity.post-message, productivity.work-issue.

Where this comes from

Weight 10 of 100 in Work & productivity: 3 of 36 accounts (a bug-report tool on the Linear MCP, Codex writing Linear issues, bulk creation on Jira)

The same as data: /api/v1/use-cases/productivity.file-issue.json, or the MCP tool get_use_case with id productivity.file-issue. Other jobs in this category: /api/v1/niches?category=productivity.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.