Connect any MCP client
A vendor-neutral guide to wiring any MCP-capable agent to Agentage Memory. The same endpoint and OAuth flow work everywhere - no API key.
What you need
Any client that speaks the Model Context Protocol over Streamable HTTP can connect. Three facts are all it takes:
- Endpoint -
https://memory.agentage.io/mcp - Transport - Streamable HTTP
- Auth - OAuth 2.1 (PKCE + dynamic client registration); sign in once in the browser, no API key.
Connect in four steps
- 1
Add an HTTP MCP server
In your client, add a new MCP server of type http pointing at the endpoint:
texthttps://memory.agentage.io/mcp - 2
Let it register
On first connect the client runs Dynamic Client Registration automatically - nothing to pre-create or paste.
- 3
Sign in
The client opens a browser to auth.agentage.io. Approve access (magic-link, or GitHub / Google / Microsoft). No token ever touches the client config.
- 4
Verify
Ask the agent to write a note and read it back (
memory__writethenmemory__read). The same account in every client shares one memory.
Generic config
Most clients accept a JSON MCP config. The shape is the same everywhere - only the top-level key differs (mcpServers for most clients, servers for VS Code):
{
"mcpServers": {
"agentage-memory": {
"type": "http",
"url": "https://memory.agentage.io/mcp"
}
}
}No API key field
There is no key or token to set. Auth is interactive OAuth on first use; the client obtains and stores its own short-lived token.
One-click for known clients
Using one of these? The dedicated page has a one-click install plus the exact config:
Tools & limits
Once connected, every agent gets the same six memory__* tools (search / read / list / write / edit / delete). See the MCP server page for the full tool reference and limitations.