get_context and ask_question are the standard retrieval pair. What is less common is memory addressed by namespace — a place to put a fact under a label and read the label back later, which is how memory stays useful across projects rather than becoming one growing pile. Note the tools declare context:read as their scope while save_memory writes; the linking flow is where actual permission is granted.
Context Link's endpoint, which listed four tools to an unauthenticated probe — server version 0.0.7. Account linking happens in the browser through a magic link on first tool use, and each tool declares an OAuth2 scope of context:read in the listing itself.
- get_context — context drawn from the workspaces and websites you have connected
- ask_question — the same sources, answered concisely rather than returned raw
- save_memory — write content under a namespace for later
- get_memory — read a namespace back
Account linking through a magic-link email on first use, so nothing is pasted into a config file.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen