Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
UseMyContext.ai is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Personal context for AI, written by you and never scraped: your profile and files, any MCP client.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usemycontext-ai-mcp https://mcp.usemycontext.ai/mcp
# 2 — ask your agent for something these tools do
# profile, list_profiles, info and 10 more
UseMyContext.ai costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usemycontext-ai-mcp https://mcp.usemycontext.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Return the user's compiled personal context - a compact structured summary of who they are, synthesized from their accepted facts. Call it at the start of any conversation that involves the user personally, to ground who they are. This is ALSO the tool that sets a user up with UseMyContext: call it when they say 'set me up with UseMyContext', 'get me started', 'get to know me', 'onboard me', or ot
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Optional: which of the user's profiles (projects) to read - a projectId from list_profiles. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this. |
| handle | string | no | Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given |
List the user's own profiles (their projects). Returns metadata only for each profile: its projectId, its name, its public @handle, its privacy status (private, shared, network, public, or org), and whether it is the one THIS connection reads by default. Use it when the user asks how many profiles they have, what their profiles are called, or which profile you are connected to - and whenever anoth
No parameter schema on file.
Explain what UseMyContext is, what this connection can and cannot do, and where the user goes to manage their account. Call this when the user asks what UseMyContext is, what you (the AI) can do with this connection, or where to find pricing, plans, billing, teams, or settings. IMPORTANT: this connection is READ-ONLY - you cannot create/rename/delete a profile, change privacy, manage the plan or b
No parameter schema on file.
Report the user's current plan and usage: their tier (Free or Premium), how many projects and how much storage they are using against their limits, their subscription status if any, and where they manage their plan. Use this when the user asks what plan they are on, how much storage or how many projects they have used, or whether they are near a limit. Metadata only - no files, facts, or profile c
No parameter schema on file.
List the user's files (metadata only: id, name, size, content-type, modified, status). Each file's status shows its readiness: 'available' means get_file can read it right now, and a just-processed file can take up to about a minute more to become searchable via ask_docs (queueEtaSeconds, when present, estimates the remaining wait). Read-only; nothing is written, so it is safe to call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Optional: which of the user's projects to list files from - a projectId from list_profiles. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this. |
| handle | string | no | Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given |
Search the user's files by filename. Returns matching file metadata (including each file's processing status), ranked by name match. Read-only; nothing is written, so it is safe to call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Filename query to match. |
| projectId | string | no | Optional: which of the user's projects to search - a projectId from list_profiles. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this. |
| handle | string | no | Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given |
Search the user's files by filename and return matching documents in the deep-research result shape. ALIAS: this is the SAME search as search_files (same data, same permissions) - use it when your client requires the id/title/url search contract (ChatGPT deep research); otherwise prefer search_files for richer file metadata. Each result's id can be passed to fetch (or get_file) to read that docume
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Filename query to match. |
| projectId | string | no | Optional: which of the user's projects to search - a projectId from list_profiles. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this. |
| handle | string | no | Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given |
Get the full text content of one file by id (large files are truncated; use ask_docs for targeted passages). An image returns the picture itself (plus any text read from it at upload); other binary files return a short-lived download link instead. Audited.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fileId | string | yes | The id of the file to fetch. |
| projectId | string | no | Optional: which of the user's projects holds the file. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this. |
| handle | string | no | Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given |
Fetch one document's full extracted text by id (a file id from search / search_files / list_files), in the deep-research result shape. ALIAS: this is the SAME read as get_file (same data, same permissions, same audit, same size guard - large files are truncated) - use it when your client requires the id/title/text/url fetch contract (ChatGPT deep research); otherwise prefer get_file, which also se
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The document id - a file id from search, search_files, or list_files. |
| projectId | string | no | Optional: which of the user's projects holds the file. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this. |
| handle | string | no | Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given |
Search the user's connected documents by MEANING and return the most relevant passages (the actual text), each cited with its source file, for you to read and quote. Use this to ANSWER a question from the user's documents - it returns grounded source content, not a file link, not a filename list, and not a pre-written answer (you do the reasoning). Before telling the user you do not know something
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to find in the user's documents (a question or topic). |
| k | integer | no | How many passages to return (default 12, max 50). |
| projectId | string | no | Optional: which of the user's projects to search - a projectId from list_profiles. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this. |
| handle | string | no | Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given |
Run an EXACT, deterministic query over ONE tabular file (a CSV, or the first table of a spreadsheet/PDF/Word document). Use this instead of ask_docs whenever the question needs COUNTING, SUMMING, AVERAGING, MIN/MAX, FILTERING, or exact row lookups over structured data ('how many rows...', 'total amount by region', 'list orders where status is failed') - semantic search undercounts tables, while th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fileId | string | yes | The id of the file to query (from list_files / search_files - the same id get_file takes). |
| projectId | string | no | Optional: which of the user's projects holds the file. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this. |
| handle | string | no | Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given |
| query | object | yes | The constrained query object (grammar in the tool description): select?, where?, groupBy?, aggregates?, limit?. |
Suggest an update to the user's saved context (something you learned about them). It is saved as a PENDING suggestion for the user to review and accept or ignore - it does NOT directly change their profile, and nothing is ever written to their files. When a conversation has surfaced something new and durable about the user and is wrapping up (the user says thanks, goodbye, or that's all, or the ta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| suggestion | string | yes | The proposed fact or update about the user, in one short sentence. |
| projectId | string | no | Which of the user's profiles the suggestion belongs to - a projectId from list_profiles. Optional: on an account-wide connection, omitting it files the suggestion into the user's active profile (the r |
| handle | string | no | Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given |
List and read curated personal context shared with you. With no arguments, lists who shared what (names + ids only, no content). With a from selector (a grantId from that list), returns that person's shared profile text. SAVED BY NAME: if the user has saved a context under a short name, pass saved (that exact name) to pull it - the service resolves the name to the real source (a share, a teamm
| Parameter | Type | Required | Notes |
|---|---|---|---|
| saved | string | no | SAVED-BY-NAME read: the exact short name the user gave a saved context. The service resolves the name to its real source and re-validates access live; if the access is gone it returns a calm "no longe |
| from | string | no | The grantId of a share to READ (take it from the list this tool returns with no arguments). Omit to LIST the available shares. |
| handle | string | no | NETWORK read: a UseMyContext project's public @handle (with or without the leading @) whose context you want to pull. Each @handle addresses ONE specific project, so the handle alone identifies what t |
| org | string | no | ORGANISATION read: the id of an organisation you and the target are BOTH members of (on an active team plan). Use together with member. The service re-checks your shared membership and the team plan |
| member | string | no | ORGANISATION read: the member id of the teammate whose live composite you want to read. Only used alongside org. You can read only a fellow member of an organisation you also belong to. |
| orgProject | string | no | ORGANISATION read: which of that teammate's projects to read (defaults to their primary project). Only used alongside org + member. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install UseMyContext.ai or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish UseMyContext.ai can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.