Polypack Memory

MCP server exposing Polypack as persistent adaptive memory

Connector by imattau · GitHub account verified by the MCP Registry

IndexedLicense unknownLocal (stdio)

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/imattau-polypack-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

MCP server exposing Polypack as persistent adaptive memory

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools: 5 read · 6 write · 2 delete · 5 not yet classified
Secrets: None asked for
Install scripts: Not scanned yet
Runs as: Python package

Tools by what they do 18

Read from the source code; the running server may list different tools.

Read 5 · Look things up without changing anything.

graph_query
memory_context
memory_get
memory_list_contexts
memory_recall

Write 6 · Create, change, send or run things.

memory_feedback
memory_store
memory_store_batch
memory_store_with_link
memory_supersede
memory_update

Delete 2 · Delete, drop, revoke or wipe things.

memory_delete
memory_unlink

Not yet classified 5 · We could not tell from the name and description.

memory_consolidate
memory_link
memory_link_batch
memory_suppress
memory_thread

Files it touches

Any path the agent passes to its tools

Tools (18)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

graph_query
Inspect graph neighbors/schema or perform an advanced edge operation. Prefer memory_link for normal memory relationships. Supported operations are neighbors, add_edge, schema, and relationship_diagnostics. RESPONDS_TO graph edges are authoritative; diagnostics identifies legacy provenance-only relationships.
memory_consolidate
Consolidate source memories into one durable higher-level memory.
memory_context
Return a working-memory set selected by activation and estimated-token budget. token_budget is an estimated-token budget. Each returned memory fits wholly within the remaining budget; budgets must be greater than zero.
memory_delete
Permanently delete one memory and its graph edges. This destructive operation requires confirm=true. Prefer memory_suppress when retaining history is useful.
memory_feedback
Record whether a retrieved memory helped this task. Call this after using a recalled memory when it was useful or misleading.
memory_get
Fetch one memory by exact ID, including its current state and revision.
memory_link
Connect two memories with an explicit graph relationship. Use RESPONDS_TO when a new handoff, verification, or fix addresses an earlier memory. Use memory_recall(include_neighbors=true) to retrieve linked memories with relationship metadata.
memory_link_batch
Connect multiple pairs of memories with explicit graph relationships in a single batch. Each item in the list should be a dict with 'source_memory_id', 'target_memory_id', and optional 'relationship' (defaults to 'RESPONDS_TO') keys.
memory_list_contexts
List context namespaces and the number of memories in each.
memory_recall
Search memories by text, context, activation, and confidence. Use this for a targeted question. Use memory_context to assemble working context. Context is soft by default; use strict_context=true for isolation. With include_neighbors=true, bounded graph neighbors are hydrated into the result. Filter relationships with edge_types such as RESPONDS_TO. The neighbor_limit bounds hydrated neighbors; limit remains the total result count. depth is silently clamped to at most 3 hops regardless of the value passed; metadata reports the depth actually applied. Metadata also reports when additional neig…
memory_store
Store durable project memory. Use procedural for preferences, conventions, and decisions; semantic for stable facts; episodic for events or task outcomes; and entity for named people, projects, or objects. Use a stable context for project memory.
memory_store_batch
Store multiple durable project memories in a single batch. Each item in the list should be a dict with 'content' and optional 'memory_class', 'context', 'confidence', 'provenance', and 'metadata' keys.
memory_store_with_link
Store a new memory and link it to an existing memory in one call. Combines memory_store and memory_link for the common case of storing a reply, verification, or fix that responds to an earlier memory. By default the new memory is the link source (new -relationship-> target); set reverse=true to make the new memory the link target instead.
memory_supersede
Replace an outdated fact while retaining its history.
memory_suppress
Inhibit a stale or unhelpful memory without deleting it.

Show 3 more tools

memory_thread
Walk the RESPONDS_TO chain from a starting memory ID and return the thread. Retrieves connected memories in both directions along RESPONDS_TO edges, returning them sorted chronologically.
memory_unlink
Remove graph edges between two memories. If relationship is omitted, all directed edges from source to target are removed.
memory_update
Update mutable memory fields without changing its content. Supported fields are context, confidence, provenance, and metadata. Use memory_supersede when the memory content itself needs to change. expected_revision prevents overwriting a concurrent update.

Signals

Stars: 0
Forks: 0
Open issues: 0
Weekly downloads: 100
Last commit: Sep 6, 2026 (1 month ago)
Last release: Sep 6, 2026 (1 month ago)
Last package publish: Sep 6, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name: io.github.imattau/polypack-mcp
Version: 0.1.31
Auth: No auth
Packages: pypi polypack-mcp
License: License unknown
Repository: github.com/imattau/polypack-mcp
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: Official MCP Registry github-graphql