# Answer a question from the team's chat, wiki and tracker

> Answer a question from the team's chat, wiki and tracker: 0 companies fully do it, 8 with a limit, 27 carry the tag. Every listing in Work & productivity with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/productivity.find-context/
- Markdown: https://www.anchorterminal.com/niches/productivity.find-context/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/productivity.find-context/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/productivity.find-context/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 8 | 27 | 23 | 7 |

## What counts as done

An answer citing at least one linked source page, thread or issue the user can open, built from a full-text search, with no content from spaces the user cannot see.

Measured, for our own tests: at most five reads.

How agents ask for it: what did we decide about the launch; where is the onboarding doc; summarise the status of project X; what does the wiki say about deploys

## Does the job, with a limit

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.

- **Atlassian Rovo MCP Server (Atlassian Pty Ltd)**: searchConfluence (CQL), searchJiraIssuesUsingJql and a Beta Rovo search cover Jira, Confluence and connected apps under the user's own permissions. Cloud only: acc-19 used a third-party server for Data Center, and acc-31 measured 27,650 tokens of tools before the first call.
- **Linear MCP (Linear Orbit, Inc.)**: The MCP finds issues, projects, comments and documents, and Linear search covers titles, descriptions and comments; it reaches only the tracker, not chat. The tool list isn't published, and acc-07 left the MCP for a CLI over token use.
- **Mattermost (Mattermost, Inc.)**: POST /api/v4/posts/search runs a full-text search over posts the token's user can see, and GET /posts/{id}/thread reads a thread. It covers chat only, with no wiki or tracker, so answers drawn from docs or tickets need another tool.
- **Microsoft Teams (Microsoft Graph) (Microsoft Corporation)**: The Microsoft Search API queries chatMessage bodies for the signed-in user, and messages carry a webUrl to cite. The listing is Teams chat only, so wiki or tracker answers need other Graph resources, and acc-23 never got the admin consent Graph needed.
- **Notion MCP (Notion Labs, Inc.)**: notion-search runs content searches over pages and databases with filters, up to 50 results, and acc-13 found it full-text where the public API is title-only. Slack and Drive need paid AI plans, acc-12's legal team blocked it for lack of narrowing, and acc-33 got only a schema from fetch.
- **Outline (General Outline, Inc.)**: documents.search searches document text with keywords and filters, limited to what the token can access, separate from documents.search_titles, and documents.info returns the Markdown body and url. It covers the wiki only, not chat or tickets.
- **Slack MCP Server (official) (Slack Technologies, LLC (a Salesforce company))**: The server searches messages and files, reads channels, threads and canvases, with private search on separate user-token scopes; acc-04 found answers good and faster than Glean. Only Marketplace or internal apps may connect (acc-06), and acc-01's standard connection exposed private messages.
- **Zulip (Kandra Labs, Inc.)**: GET /messages with a narrow carrying search keywords, channel and topic operators runs a full-text search over messages the account can see. Zulip is chat only, so wiki or tracker answers need another tool.

## What stops agents finishing

- public API searches titles only
- the deployment is Data Center or self-hosted and the hosted MCP does not reach it
- connection exposes private content an organisation forbids

## Around it

Before: chat.user-question. After: productivity.write-doc, productivity.post-message.

## Where this comes from

Weight 23 of 100 in Work & productivity: 7 of 36 accounts: Slack, Jira and Docs MCPs for status, Cursor beating Glean, Confluence Data Center search, Notion full-text search, a Notion wiki page whose body vanished

As data: https://www.anchorterminal.com/api/v1/use-cases/productivity.find-context.json, or the MCP tool get_use_case with id productivity.find-context. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
