## Source

`TODO`: "Settings should show MCP connections and potentially allow setting permissions, tied into OAuth flow???"

## Current state

Audience decision: MCP is for agents and power users, not a public third-party API.

Account settings has an "AI agents (MCP)" section that shows the endpoint and opens the setup guide, but it does not list connected clients or grants. The OAuth server stores grant state in D1 (`oauth_server`, `oauth_client_assertion`), and the MCP server already distinguishes `project:read` from `project:write`.

## Acceptance

- [ ] The account page lists the MCP clients/grants for the signed-in account, with client identity, granted scope, creation time and last use.
- [ ] A user can revoke a grant. The chosen policy for already-issued access/refresh tokens is documented and enforced.
- [ ] The OAuth consent screen lets the user choose read-only or read/write access where the client requests it.
- [ ] The server enforces the chosen scope on every tool call, with a clear typed failure for a read-only token.
- [x] Decision: per-project grants are chosen by the user at consent time.
- [ ] The consent screen lets the user pick which projects a client may access.
- [x] Decision: agent edits are part of the project's change history, and every change records the acting entity (user or agent).
- [ ] Extend the change history to identify the actor and expose it in the project activity.
- [ ] One account cannot see or revoke another account's grants; tests cover isolation.
- [ ] The in-app MCP setup guide and README/AGENTS describe the connection list and permission model.
- [ ] No separate account system or credential store is introduced.


<sub>Generated on _MrBeast_ using _opencode/deepseek-v4.1-flash_ in _ses_e8326e581ffeJviTmSkomwnKES_</sub>