Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Configure Memory 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.
9
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Bring your saved preferences, project decisions, and useful context into your next AI conversation.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http configure-memory-mcp https://mcp.configure.dev/
# 2 — ask your agent for something these tools do
# configure_connect, configure_profile_read, configure_profile_search and 6 more
Configure Memory costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CDAll 1 server
configure-dev1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 configure-memory-mcp https://mcp.configure.dev/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
9 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.
Mints the Configure link that fixes access for the current user — sign-in, app connect, or permission grant. This is the tool for two situations: a Configure tool result says authorization_required (the user is not signed in), or the user asks to sign in or connect an app. The user's data exists behind sign-in, so "I have nothing on you" would be inaccurate in that state; what serves the user is k
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client | string | no | Legacy fallback handle for an unauthenticated headless client whose transport supplies no identity. Never overrides an authenticated agent. |
| client_name | string | no | Legacy display hint for an unauthenticated headless client. Never overrides registered agent metadata. |
| app | string | no | Optional app to connect or reconnect for an already signed-in user. This is for third-party apps only; it does not bring memories in from other assistants (that is not a connect action — see configure |
| capability | string | no | Optional specific permission to request when the user has an app connected but not this capability (the profile read's integrations map shows which capabilities each connector has). For example, when |
| purpose | string | no | Optional one-line reason shown to the user on the permission page, such as "so I can send the follow-ups you approve". Used with capability. |
Read the current user's approved profile. Use the no-argument overview only when the user explicitly asks to review their profile or get a profile overview. For personalized help or a specific fact, use configure_profile_search with a concrete query about the current task; no overview is needed first. Read a known category or project box when the user asks to review it or resume that project. Thre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sections | array | no | Strict page filter on the composed profile document: the response contains exactly the pages named here, nothing else. Omit for the profile overview (facts, boxes, sources, docs), only on an explicit |
| page | number | no | Optional 1-based page for a box open. Each box open returns page_size facts and a total; pass page: 2 to continue a long box (project threads, big namespaces). Ignored without box. |
| since | string | no | Optional delta cursor for a box open ("YYYY-MM-DD" or an ISO timestamp): return only notes newer than this. Every box open returns latest (the newest note timestamp); store it and pass it back as sinc |
| detail | string | no | Optional box-open verbosity. Default compact truncates long notes and marks them truncated: true; pass "full" to read whole notes. Ignored without box. |
| box | string | no | Optional box id from a previous read's table of contents. A category name like "work" opens the settled facts in that category, ranked by value, across all sources. "agents/<name>" or "imports/<provid |
Search or list permitted attributed profile memories/facts for the current user. Use this for personalized help, targeted retrieval, source-specific questions, or exact memory/fact lookup. For personalized help, pass a concrete query about the current task and relevant filters when known; no overview is needed first. Omit query or pass "*" only when the user asks to list saved memories, narrowing
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional search query. Omit or use "*" to list bounded permitted attributed profile results, for example with a source filter. |
| source | string | no | Optional explicit source handle filter, such as "tempo", "chatgpt", or "import:chatgpt". Source-box ids from configure_profile_read's table of contents ("agents/<name>", "imports/<provider>") are also |
| box | string | no | Optional category box id from configure_profile_read's table of contents, such as "work". Filters to the settled facts in that box and composes with query; unknown or empty boxes return empty results, |
| from | string | no | Optional inclusive start date filter in YYYY-MM-DD format for date-attributed results. |
| to | string | no | Optional inclusive end date filter in YYYY-MM-DD format for date-attributed results. |
| limit | number | no | Optional maximum result count. The backend enforces a default and hard cap. |
| detail | string | no | Optional result detail. Defaults to compact, which truncates long memory text. Full returns the complete text plus markers. Every result at either detail carries id, source, written_by, and saved_on ( |
Save one explicit, durable fact the user stated about themselves so any Configure-connected agent the user allows can use it in future conversations. Use it when the user asks you to remember something or clearly signals a fact is for keeps (a stable preference stated for future use, an ongoing goal); a detail mentioned in passing is not a request to persist it — when intent is unclear, ask before
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fact | string | yes | Required. The single durable fact to store, phrased as a concise standalone statement about the user (for example "Prefers vegetarian restaurants"). One fact per call; do not batch multiple facts or p |
| box | string | no | Optional. The namespace box (shelf) to file this under. TWO KINDS. (1) A topic box, for facts about the user: "work", "contacts", "health". (2) "projects/<slug>", the shared handoff shelf, for notes w |
| kind | string | no | What kind of note this is, for "projects/<slug>" notes. Set it whenever you are stuck or need something back from another agent: "blocker" (you cannot proceed) and "question" (you need an answer) are |
| reply_to | string | no | Optional. Memory id ("mem_...") of a note in the SAME box this one answers. Ids appear on notes when you open a project box. |
| resolves | string | no | Optional. Memory id ("mem_...") of a question or blocker in the SAME box that this note closes, which is what stops it being reported as open. |
Use this when the user asks to save several facts at once, or approves a list of facts you proposed. Saves each entry as a separate memory in the user's Configure profile, in one call. Send only facts the user asked to save or approved, each a short standalone statement about the user. If the user asks to review first, show the list and wait for their approval before calling. Use configure_profile
| Parameter | Type | Required | Notes |
|---|---|---|---|
| facts | array | yes | Short standalone facts the user asked to save or approved. At most 20,000 fact characters in total. |
Delete the user's memories that YOU saved or imported. WHICH to delete: if you hold an id, pass id ("mem_..."); if you do NOT have an id and the user names a topic, pass match with a word the memory contains (match: "nursing") and forget finds and deletes your matching memories itself, no search first. HOW: pass reason "user_request" whenever the user wants it gone for good or says never mention i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | no | One memory to delete, by the id returned when it was saved (format "mem_...", also shown on entries in your own source box). Use exactly one selector: id, import_id, or scope. |
| date | string | no | Optional. The memory's date ("YYYY-MM-DD") if known, from the saved path or entry; providing it makes the delete a direct lookup instead of a namespace scan. |
| scope | string | no | Delete everything of yours in one call, instead of one id at a time. "imports": every memory you brought in through configure_profile_import, including older imports that predate import ids. "saved": |
| match | string | no | Selector. Words a memory contains, e.g. "nursing" or "coffee". Finds YOUR OWN matching memories and deletes them, so you do not need a separate search to get ids first. A match WITHOUT confirm:true re |
| confirm | boolean | no | Only with match. Omit or false to preview (count + the memories that match, deletes nothing). Set true to delete the matched memories. Preview first unless the user was unambiguous. |
| import_id | string | no | Optional, and used instead of id. The import_id returned by configure_profile_import: retracts every memory that import created, in one call, instead of one delete per memory. Only entries from an imp |
| reason | string | no | Optional, default "correction". Use "user_request" ONLY when the user explicitly asked you to remove this and not bring it back (for example "delete that" or "never call me that again") — it additiona |
Close out a Configure-profile-backed turn by submitting bounded turn evidence and, optionally, durable memories worth keeping. Error -32009 (commit_required) from any configure tool is resolved ONLY by this call: commit, then retry the blocked call — never configure_connect, which is for sign-in. Call it at turn end even when you learned nothing durable: reads and searches created obligations rega
| Parameter | Type | Required | Notes |
|---|---|---|---|
| memories | array | no | Optional durable memory candidates to save, one clear fact per entry. Only include durable user facts, preferences, or intentions; do not summarize provenance, the conversation, or assistant replies. |
| messages | array | no | Optional minimal evidence to clear read-backed commit obligations: at most the one or two user statements that directly support each saved memory. Never send conversation history or any messages beyon |
| toolResults | array | no | Optional bounded tool result evidence, each with toolName and content, used as evidence to clear read-backed commit obligations. |
| read_id | string | no | Optional read id returned by a prior configure_profile_read or configure_profile_search obligation; pass it to tie this commit to that specific read. |
Share one Configure project without making a copy. Four modes with different stakes — action "list" only inspects (grants and open counts, changes nothing); every other mode changes access outside this conversation and needs the user's explicit go-ahead for that specific change. action "share" grants a named person (email or phone) read access, write only when the user explicitly grants it; "share
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | The sharing action to perform. |
| project | string | yes | Project slug, such as "billing-migration" or box id "projects/billing-migration". |
| with | string | no | Email address or E.164 phone number for a private member share. |
| mode | string | no | Use "link" to mint a public read-only link. Links can never write. |
| can_write | boolean | no | For a member share, allow the member to append notes. Omit or false for read-only membership. |
| expires_in_days | number | no | Optional whole-number lifetime for this grant, from 1 to 3650 days. |
| grant_id | string | no | Grant id from a prior list result. Omit it with action "revoke" to unshare the whole project. |
Import brings memories INTO the profile from outside — it never exports, lists, or shows what is already saved (use configure_profile_read or configure_profile_search for that, even when the user says "export" or "show me"). Two shapes go in here. A structured memory export, the ---SECTION:Name--- format with one dated entry per line that assistants produce when asked to export everything they kno
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | Required. The content the user explicitly asked to keep — a memory export from another assistant, material they provided, or the discussion they asked to save. Include only what the user asked to impo |
| kind | string | no | Which of the two PROCESSING shapes this text is, because they are stored differently (a different argument from configure_profile_remember's kind, which classifies a single project note). "memories": |
| box | string | no | Optional, and only used for kind "context". The namespace box (shelf) to file the note under: reuse an existing box id from the profile table of contents, or a short new lowercase name to create one. |
Free
$0 forever
- 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 Configure Memory or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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. 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 3.0.0.
3.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Configure Memory can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.