Skip to content

Configure Memory MCP server

io.github.configure-dev/configure-memoryconfigure-devstreamable-httpv3.0.0Scanned

Bring your saved preferences, project decisions, and useful context into your next AI conversation.

9 tools: 2 can delete or cancel things, 5 change things and 2 only read.

Tools: 2 delete, 0 irreversible, 5 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 4 findings, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Configure Memory MCP server can do

The Configure Memory MCP server is published by the GitHub account configure-dev. It has 9 tools. It can delete or cancel things (2 tools: configure_profile_forget and configure_project_share) and create or change data (5 tools: configure_connect, configure_profile_remember, configure_profile_remember_many, configure_profile_commit and 1 more). 2 tools only read.

2 tools bring in text other people can write (configure_connect and configure_project_share).

The fixed checks matched 4 findings, 1 of them high severity (long-description and model-directed-text). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 3.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 2Claude Code: deny
  • configure_profile_forgetDelete the user's memories that YOU saved or imported.1 finding

    Why it is in this group

    • The description's first verb is "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • High

      The description contains "never mention it", an instruction to keep something from the user.

      Matched text

      description: "...the user wants it gone for good or says never mention it again (this suppresses the content from..."

      What this check looks for
    Description, as the server wrote it
    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 it again (this suppresses the content from re-saving and re-importing); use the default correction only for fixing your own mistake. A match previews first: it returns a count and the matching memories and deletes NOTHING until you call again with confirm: true, so review and confirm only what the user meant. import_id (from configure_profile_import) retracts one whole import; scope ("imports", "saved", "all") clears everything of yours at once. Pass exactly one selector. Reach is your own writes only: never another agent's memories, never an import the user ran themselves, never the profile's settled facts, and this deletes memories only, never the Configure account. An id outside your reach returns a clean not-found, not an error. Deletion is permanent for your copy. Returns the deleted memory id and which source it lived under.

    Annotations the server declares

    • title: Delete a memory
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • configure_project_shareShare one Configure project without making a copy.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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" with mode "link" mints a public read-only link — confirm the user wants it public; "revoke" with grant_id removes one grant, and "revoke" WITHOUT grant_id unshares the whole project — confirm which of the two the user means before calling. Link tokens are shown once and never appear in grant listings.

    Annotations the server declares

    • title: Share a project
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
Changes things 5Claude Code: ask
  • configure_connectMints the Configure link that fixes access for the current user — sign-in, app connect, or permission grant.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 knowing sign-in is the blocker and having the returned link, on its own line where it is easy to click. Retrying the failed call returns the same result until the user has signed in. Links exist only as this tool mints them — a hand-built link fails — and when a tool result already carries a link, that link is the one the user needs (minting another creates a second, competing session). Not the first call of a conversation (that is configure_profile_read), and not the fix for error -32009 (that is configure_profile_commit). For a signed-in user: app (gmail, calendar, drive, notion, sheets) connects or reconnects that app — returns status connect_app, a link, and whether it is already connected — and capability (like gmail:send) covers a single missing permission (status permission_needed). Bringing memories in from another assistant is NOT a connect action: this tool does not do it, and a bare "connect Configure" from a signed-in user needs no argument at all — omit app unless the user names a specific app to connect. Configure derives the requester from authenticated agent metadata or MCP transport metadata; the client field is a legacy fallback hint for an unauthenticated headless client only.

    Annotations the server declares

    • title: Connect Configure
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • configure_profile_commitClose out a Configure-profile-backed turn by submitting bounded turn evidence and, optionally, durable memories worth keeping.No findings

    Why it is in this group

    • The name "configure_profile_commit" says "commit": a word for a change.
    Description, as the server wrote it
    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 regardless, and an empty commit with a one-line summary clears them. The runtime usually calls this for you after a profile read; call it yourself only when your host requires manual write-back. Prefer configure_profile_remember for a single fact the user explicitly stated; use commit to clear the obligation created by a configure_profile_read or configure_profile_search and to save memories drawn from the whole turn. Evidence is minimal: at most the specific user statements that support each memory, plus toolResults — never conversation history; memories are durable user facts, preferences, or intentions rather than provenance or assistant replies. Returns the obligations it cleared and any memories written (id, source, marker). Additive: it only records what this turn learned. It never deletes or overwrites existing memories, and never emails, posts, or publishes anything on the user's behalf.

    Annotations the server declares

    • title: Save turn memories
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • configure_profile_importImport 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, eve…1 finding

    Why it is in this group

    • The name "configure_profile_import" says "import": a word for a change.

    Findings

    • Info

      The description is 2,142 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...er has already turned the material into a list of separate facts and approved it."

      What this check looks for
    Description, as the server wrote it
    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 know about the user, is split into individual profile facts and filed by category, which is how a first-time backfill from another assistant lands. Anything else is treated as one chunk of context: bulk-file it into your namespace when there is too much to save as a single fact — a long note, meeting notes, a multi-topic dump, or the current discussion when the user asks to save it. Configure distills it into a short context note (a stream, kept as-is in your namespace, not promoted to shared profile facts) and files it into a box automatically. Use configure_profile_remember instead for one clear fact the user stated; use configure_profile_commit to close out a turn after a profile read. Reach for import the moment the user provides material and says things like "keep all of this" or "import these notes", and when the user asks to save the current conversation ("save this whole conversation") — that explicit request is both the designation and the consent, so import is the right call, not a refusal. Send only what the user asked to keep, and never import anything on your own initiative. Optionally pass box to force the shelf: reuse an existing box id from the profile table of contents, or a short new lowercase name to create one; omit it to let Configure pick the box. Writes under your own agent namespace (resolved from the authenticated session, not arguments) and returns the chosen box and stored memory id. Additive: it only files context the user asked to keep. It never deletes or overwrites existing memories, and never emails, posts, or publishes anything on the user's behalf. Use configure_profile_remember_many instead when the user has already turned the material into a list of separate facts and approved it.

    Annotations the server declares

    • title: Import context
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • configure_profile_rememberKeeps Configure, the user's long-term memory across all their assistants, current.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description is 2,353 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ng memories, and never emails, posts, or publishes anything on the user's behalf."

      What this check looks for
    Description, as the server wrote it
    Keeps Configure, the user's long-term memory across all their assistants, current. Check configure_profile_search on the topic first, in an earlier step, and read its result before this call: when the result already lists the fact, in any wording, skip the save; when it is missing, or Configure holds an older version (moved cities, changed jobs), save the new fact here. Saving without that search risks a duplicate. Call it as soon as the user mentions a lasting fact about themselves, whether or not they ask you to remember it (an explicit "remember that" still gets the search first), even in passing inside another request: a preference, a diet, a habit, a relationship, an ongoing goal (training for a marathon), or a change in their life. "By the way, I like Chinese food" and "Where should I get dinner Friday? I really like Chinese food" both mean searching for Chinese food, saving "Likes Chinese food" if it is new, then answering. What the user is doing or asking about right now is not a fact about them: one-off task details ("needs a table for four on Friday"), temporary plans ("in Chicago for a conference this weekend"), the bug or error they want fixed. These, what you infer from them ("is a React developer"), your own guesses, and passwords, payment, health or government identifiers are not durable facts and stay out unless the user asks. Save one clear fact per call, quietly, with no need to ask first unless the user has asked not to save; several facts mentioned together get one call each. Bulk pasted material and exports go to configure_profile_import. Your own work is not a fact about the user: what you built, shipped, debugged, or are tracking belongs on the shared project shelf, so file it with box "projects/<slug>" for the next agent to read back, or leave it out. Optionally file the fact into a box (a shelf within your namespace) with the box argument: reuse an existing box id from the profile table of contents when one fits, otherwise pass a short new lowercase name and it is created on the spot. Writes under your own server-resolved agent namespace (identity is resolved from the authenticated session rather than from arguments) and returns the stored memory id and source. Additive: it never deletes or overwrites existing memories, and never emails, posts, or publishes anything on the user's behalf.

    Annotations the server declares

    • title: Save a fact
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • configure_profile_remember_manyUse this when the user asks to save several facts at once, or approves a list of facts you proposed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_remember for a single fact. Accepts 1 to 100 facts per call, up to 1,000 characters each and 20,000 in total; send a longer approved list as several calls. It is not for passwords, keys, payment or health details, government identifiers, identity documents, sensitive personal attributes (race, religion, politics, sexuality, biometrics or genetics), or other people's personal data; the server's pattern checks are a backstop, not a complete filter, so these are left out before calling. Optional box files a fact under a category. Additive: it never changes or deletes existing memories. Returns a result for each entry and counts of saved, already_saved, refused and failed. Report those counts accurately, retry only failed entries, and never say the whole list was saved when some entries were refused or failed. Use configure_profile_import instead when the user supplies raw material rather than a list of facts: a note, a document, or an export from another assistant.

    Annotations the server declares

    • title: Save selected memories
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • configure_profile_readRead the current user's approved profile.1 finding

    Why it is in this group

    • The name "configure_profile_read" says "read": a word for reading.

    Findings

    • Info

      The description is 2,435 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...r is not signed in; configure_connect supplies the sign-in link that resolves it."

      What this check looks for
    Description, as the server wrote it
    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. Look here before you save, too: when the user states a durable fact about themselves, check with configure_profile_search on that topic (or the overview, if it is already in context) whether Configure already has it or holds an older version, then save only what is new or changed with configure_profile_remember. Read a known category or project box when the user asks to review it or resume that project. Three ways in. (1) No arguments: the profile overview. Returns composed context, not raw files: identity, the synthesized narrative and preference docs, key facts each tagged with their box like "[work] …", changesSince (memories newer than the synthesized summary), and a table of contents of boxes. Category boxes ("work", "preferences-and-taste", …) hold Configure's settled facts; source boxes ("agents/atlas", "imports/chatgpt") hold one agent's or import's own notes; project boxes ("projects/<slug>") are shared tags across agents. The overview is budget-bounded; when something is cut it sets truncated and names the box ids holding the rest — open those instead of re-reading. (2) sections: strict pages of the composed document, and ONLY those pages — sections: ["imports"] is the imports overview (each provider's summary and count), ["soul"] is the full soul document (voice and personality) and ["context"] the full context document (current focus), each the untruncated version of what the overview cut, ["agents"] is the connected-agent map. Use a section when you want one page cheaply. (3) box: open one shelf of STORED memories by id from the table of contents; unknown or empty boxes return a clean empty result naming the boxes that exist. A box open returns ONE PAGE: the response carries total, and when total is larger than the notes you received, call read again with page: 2, then 3, until you have them all — answering from page 1 alone silently drops the rest. For point lookups (one fact, date ranges, source attribution) or filtering by author, use configure_profile_search. An authorization challenge means the user is not signed in; configure_connect supplies the sign-in link that resolves it.

    Annotations the server declares

    • title: Read profile
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:03 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.configure.dev/.well-known/oauth-protected-resource
Authorization servers
https://mcp.configure.dev
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (2 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.configure.dev/: tools/list returned 9 tools to an anonymous client, including configure_profile_forget (destructive), configure_project_share (destructive), configure_connect (write), configure_profile_remember (write), configure_profile_remember_many (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 high3 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 3.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http configure-memory https://mcp.configure.dev/
claude mcp add --transport http configure-memory https://mcp.configure.dev/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__configure-memory__configure_profile_read",
      "mcp__configure-memory__configure_profile_search"
    ],
    "ask": [
      "mcp__configure-memory__configure_connect",
      "mcp__configure-memory__configure_profile_remember",
      "mcp__configure-memory__configure_profile_remember_many",
      "mcp__configure-memory__configure_profile_commit",
      "mcp__configure-memory__configure_profile_import"
    ],
    "deny": [
      "mcp__configure-memory__configure_profile_forget",
      "mcp__configure-memory__configure_project_share"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as configure-memory. Review it before you use it.

Capability tags behind 2 rules
  • mcp__configure-memory__configure_connect untrusted-input
  • mcp__configure-memory__configure_project_share untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.configure-dev/configure-memory/verify?hash=547fdfbbc75a10de6e80cf7733a35010fc1e9ca6d12951c73d18a823d5862eb1" | jq -e '.changed == false'

Pinned hash 547fdfbbc75a, from Nov 16, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.configure-dev/configure-memory/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.configure-dev/configure-memory
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.configure-dev/configure-memory.svg)](https://radar.anlyon.com/servers/io.github.configure-dev/configure-memory)

Source: MCP Registry. Synced Oct 21, 2026, 18:28 UTC.

Configure Memory MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Configure Memory MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 7 of which can change, send or delete something, and 4 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Configure Memory MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: configure_profile_forget and configure_project_share.

Can the Configure Memory MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Configure Memory MCP server have?

9 tools: 2 destructive, 5 write, 2 read. configure_profile_forget, configure_project_share, configure_connect, configure_profile_remember, configure_profile_remember_many, configure_profile_commit, configure_profile_import, configure_profile_read and 1 more.

Does the Configure Memory MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Configure Memory MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Configure Memory MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.