Configure Memory
v3.0.0Bring your saved preferences, project decisions, and useful context into your next AI conversation.
Endpoint health
online- Last checked
- 11/20/2026, 4:16:15 AM
- Latency
- 187 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.configure-dev%2Fconfigure-memory
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.configure-dev/configure-memory": {
"url": "https://mcp.configure.dev/"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
9 shown · authentication unknown
configure_connect
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.
Schema valid · SHA-256 2a4882f45089…
View input schema
{ "type": "object", "properties": { "client": { "type": "string", "description": "Legacy fallback handle for an unauthenticated headless client whose transport supplies no identity. Never overrides an authenticated agent." }, "client_name": { "type": "string", "description": "Legacy display hint for an unauthenticated headless client. Never overrides registered agent metadata." }, "app": { "type": "string", "enum": [ "gmail", "calendar", "drive", "notion", "sheets" ], "description": "Optional app to connect or reconnect for an already signed-in user. This is for third-party apps only; it does not bring memories in from other assistants (that is not a connect action — see configure_profile_import)." }, "capability": { "type": "string", "enum": [ "gmail:read", "gmail:send", "calendar:read", "calendar:write" ], "description": "Optional specific permission to request when the user has an app connected but not this capability (the profile read's integrations map shows which capabilities each connector has). For example, when Gmail is connected read-only and you need to send, pass capability \"gmail:send\". Returns status permission_needed with a link that asks the user for exactly that permission and why. Prefer this over app when only a capability (like send) is missing." }, "purpose": { "type": "string", "description": "Optional one-line reason shown to the user on the permission page, such as \"so I can send the follow-ups you approve\". Used with capability." } } }
Connections
streamable-http
https://mcp.configure.dev/