Attention

Attention documents 68 tools across 15 groups; Anthropic's directory lists 10. The directory snapshot matches Attention's own v1.0.0 release, and seven versions have shipped since. Attention states every release is additive and no tool has been removed, so the 58 undocumented-in-the-directory tools are additions the listing has not caught up with.

No. Attention states every tool runs under your authenticated identity and its permission model is enforced server-side, so a call, scorecard, team or user you cannot open in the app is not returned through MCP. Note the default is broader than one rep: Attention's docs say sales reps already see their team's calls.

Yes. Attention documents it as returning the full transcript, scorecard results, AI-extracted insights, participants and CRM linkage for one call. A `detailed_transcript` flag adds speaker names and timestamps. This is verbatim customer speech reaching a model, not a derived summary, which makes it the most sensitive read on the connector.

No, and the directory's Read and write label is correct. Attention's server declares `mcp:read mcp:write` in its own authentication challenge and both OAuth descriptors. Attention documents 47 write-scoped tools including 11 it flags as destructive, among them permanent user deletion, API key revocation and CRM account disconnection.

It runs AI analysis across up to 25 calls in one request and returns a written answer. Attention scopes it `mcp:read`, so it reads rather than writes. It is a bounded analysis tool, not an open dispatcher — you hand it call IDs or a deal ID, and it reasons only over those conversations.

Potentially yes. Snippet creation takes an `internal` flag that decides whether the clip is internal-only or shareable externally. In the Attention app the share dialog's Require login box is unchecked by default, meaning anyone holding the link can watch the clip of a real customer call without an Attention account.

Yes, on Team and Enterprise plans. Attention states an organization Owner must add the connector in Organization Settings before individual users can connect, so the org gate comes first. On smaller plans no equivalent admin toggle is documented, and revocation is per-user through the client's Connectors screen.