Home / Compare / Agent Memory
Hosted vs self-runAgent Memory

Hosted vs self-run: Agent Memory

This page compares a hosting model, not a tool-for-tool match: WingMan's own hosted Agent Memory tools (called over one shared MCP endpoint, metered per call) against third-party MCP servers in the same category that you install and run yourself. No server here is claimed to be equivalent to a specific WingMan tool - the comparison is setup and hosting model, drawn straight from each side's registry entry.

WingMan hosted

ToolPriceCategory
Forget MemoriesMetered - see /pricingmemory
Ingest CorpusMetered - see /pricingmemory
List MemoryMetered - see /pricingmemory
Memory StatsMetered - see /pricingmemory
Query CorpusMetered - see /pricingmemory
Read Memory ChangesMetered - see /pricingmemory
Recall MemoriesMetered - see /pricingmemory
Search MemoryMetered - see /pricingmemory
Search Memory FactsMetered - see /pricingmemory
Share MemoryMetered - see /pricingmemory

+3 more in this category - see the full hosted tools hub.

Self-run (third-party)

ServerTransportWhat running it meansInstall method
GitHitshttpRuns on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.Remote endpoint (mcp-remote bridge for older clients)
com.googleapis.memorystore/mcphttpRuns on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.Remote endpoint (mcp-remote bridge for older clients)
Microsoft Learn MCPhttpRuns on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.Remote endpoint (mcp-remote bridge for older clients)
br.com.signdocs/mcp-serverhttpRuns on the vendor's own servers - nothing installs locally, but you manage a separate account and auth with them.Remote endpoint (mcp-remote bridge for older clients)

When to choose which

Choose the WingMan hosted tool(s) when

Choose a self-run server when