Last verified: October 31, 2026
What You Can Now Do
Context Memo now supports OAuth sign-in: you can authorize external applications to access your brand data securely through OAuth and manage those permissions in a new Connected Apps section in Settings. Before this, connecting a third-party tool to your Context Memo MCP meant handing over credentials and hoping the other side handled them well. Now the application authenticates against Context Memo directly, you approve the access explicitly, and the grant is a record you can see and remove. The decision this changes: whether to let an AI assistant, internal agent, or vendor tool read your scan data and memo library at all. You can say yes without issuing a shared secret, and you can reverse it without rotating keys across your stack.
Where It Is in Context Memo
Settings, in the new Connected Apps section of the dashboard. The screen lists every external application that currently holds an authorization against your brand, with a revoke control on each entry. New grants appear here after a user completes the OAuth consent flow from the connecting application. The OAuth capability itself sits on the customer MCP (Model Context Protocol) endpoint, so the applications you see listed are the ones that connect through MCP.
How to Use It
- Open Settings → Connected Apps. You'll see your current authorizations, or an empty list if nothing has been connected yet.
- In the third-party application, choose Context Memo as the connection and start sign-in. The app redirects you to Context Memo's authorization screen.
- Review the access being requested, then approve. Context Memo issues a token to the application. No password, no API key, nothing copied into another vendor's settings field.
- Return to Connected Apps. The application now appears as an active grant tied to your brand.
- Revoke any entry when a tool is retired, a vendor contract ends, or a security review flags it. Access stops at Context Memo, and you don't have to rotate a credential that other systems also use.
- Re-check the list on whatever cadence your access reviews run. The list is the answer to "what has read access to our brand data?"
Why We Built It
Customers told us the same thing in different words: they wanted to connect third-party tools to their brand data without sharing passwords or API keys directly. That constraint had a real cost. Teams either skipped useful integrations entirely, or they pasted a long-lived key into a tool nobody owned after the person who set it up moved teams. Shared secrets are invisible once distributed. You can't see who holds one, you can't remove one selectively, and rotating it breaks every other system using the same key. An explicit grant you can view and revoke replaces guesswork with a list.
That matters more as brand data moves into agent workflows. Your scan results, competitor share of voice, and memo library are competitive intelligence. The access path to them should be auditable by the same people who sign off on every other data connection in your stack.
What It Does Not Do Yet
This release covers OAuth for the customer MCP endpoint. The platform integrations you may already run (HubSpot, Slack, Google Search Console, Bing Webmaster, IndexNow) keep their existing connection flows and are not managed from Connected Apps. If you're auditing access, treat Connected Apps as the record for MCP clients and check those integrations in their own settings areas.
Revocation is a manual action. Grants do not expire on a schedule you set, so if your policy requires time-boxed access for a vendor tool, put the review date in your own calendar and revoke from this screen when it arrives.
Context Memo also isn't your identity provider. It authenticates applications against your brand, not your workforce. Keep SSO and user provisioning where they live today.
