Developer · Remote MCP server
Memwyre
Universal persistent memory and knowledge retrieval layer for AI agents and LLMs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.memwyreai/memwyre- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-03
- Updated
- 2026-09-03
- Publisher
- memwyreai (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/memwyreai) · how
- Repository
- github.com/memwyreai/Memwyre
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://server.memwyre.tech/mcp/ | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- No - could not connect (DNS or connection failure)
- Handshake
- -
- Checked on
- 2026-10-05
How to connect Memwyre
Memwyre is a remote MCP server: there is nothing to install. Its endpoint is https://server.memwyre.tech/mcp/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| MemoryRouterPersistent AI memory shared across Claude, ChatGPT, coding agents, and compatible MCP clients. | Remote · HTTPLive check: ✓ handshake |
| MemorySync DocumentationSearch and read the current MemorySync documentation while writing integration code. | Remote · HTTPLive check: ✓ handshake |
| Memshelf MCPWorking memory for AI agents: digest-indexed episodes on a git shelf, recalled a section at a time. | Local · stdio |
| MemtomemMarkdown-first long-term memory for AI agents. Hybrid BM25 + vector search, runs locally. | Local · stdio |
| mendapiDetect API breaking changes, scan your codebase for impact, and draft the fix. Runs locally. | Local · stdio |
| Mengi CloudManage Kubernetes clusters, deployments, databases, secrets and observability on Mengi Cloud. | Remote · HTTPLive check: sign-in required |
| Meok MCP Injection Scan MCPMCP injection / prompt-poisoning / SSRF scanner. 30+ canonical rules covering the April 2026. | Local · stdio |
| meok-eu-cra-mcpEU Cyber Resilience Act (CRA, Regulation (EU) 2024/2847) compliance MCP server. 4 tools, 11 tests. A. | Local · stdio |