usemycontext.ai

UseMyContext.ai serves the connected user's own personal context: a compiled profile, their uploaded files, and contexts other people shared with them. Call `profile` first to ground who the user is. Call `list_profiles` when the user asks what profiles they have: it lists their own profiles (projects) with each one's name, @handle, and privacy status, and marks which one this connection reads by default (metadata only, no file content). Use `list_files` or `search_files` to find a file by name, `get_file` to read one file's full text, `ask_docs` to retrieve cited passages that answer a question from the user's documents, and `query_table` for exact counts, sums, filters, or group-bys over one tabular file. For clients that require the deep-research search/fetch contract, `search` and `fetch` are read-only aliases of `search_files` and `get_file` returning the same data in that shape. Use `shared_context` to list and read contexts shared with the user. When you learn something durable about the user, propose it with `suggest_update` (on an account-wide connection, pass an explicit projectId from `list_profiles`); it is saved as a pending suggestion the user reviews, and nothing here can modify the user's files. If `profile` returns an empty-profile note, the account is brand new: follow that note, offer a short interview, and file what you learn with `suggest_update`. This connection is READ-ONLY: it cannot create, rename, or delete a profile, change a profile's privacy, manage the plan or billing, set up a team, invite teammates, or connect Google Drive, Notion, or kDrive - the user does those at usemycontext.ai. Call `info` for what UseMyContext is, what you can do here, and where to manage the account; call `account` for the user's current plan and storage usage.