Claude Connector Documentation

What this MCP server does

Agentic Memory gives Claude a private, persistent memory layer for saved research, prior conversations, and project context. Claude can search what the user has intentionally stored, recover surrounding conversation context, inspect indexed project knowledge, and save explicit notes or research findings back into the user's Agentic Memory workspace.

The hosted Claude connector is intentionally bounded: it does not browse the live web, send messages, make purchases, operate calendar or payment systems, or expose admin/indexing tools through the public MCP surface.

Claude setup

Use this endpoint when adding Agentic Memory as a Claude remote MCP connector: https://mcp.agentmemorylabs.com/mcp-claude

Open Claude's remote MCP connector or custom connector setup flow.
Enter the MCP server URL exactly as shown above.
Complete the OAuth sign-in flow for the Agent Memory Labs account or reviewer/demo account.
After connection, refresh tool metadata and confirm the connector shows the 10 public tools listed below.
Start with a broad memory search prompt, then drill into saved research or conversation context as needed.

Connection requirements

Users need an Agent Memory Labs account or workspace with OAuth access enabled.
For review, Agent Memory Labs provides a dedicated reviewer/demo account with pre-seeded sample memory.
The connector uses OAuth 2.0 authorization code flow with PKCE and dynamic client registration.
Default OAuth scope: mcp:tools.
OAuth discovery is available at /.well-known/oauth-authorization-server on this host.
Protected-resource metadata is available at /mcp-claude/.well-known/oauth-protected-resource.
No local server, database, or custom instance URL is required for the hosted connector.

Supported Claude surfaces

Claude.ai remote connector use is supported through the hosted endpoint above.
Claude Desktop custom connector use is supported through the same hosted endpoint.
Claude Code support should be claimed only when the final deployed smoke check still matches archived direct OAuth and retrieval evidence.

Available tools

The public connector exposes 10 reviewed tools. Admin, indexing, and maintenance tools are not part of this public surface.

Read tools

search_codebase
get_file_dependencies
trace_execution_path
search_all_memory
list_project_and_repo_ids
search_web_memory
search_conversations
get_conversation_context

Write tools

memory_ingest_research
add_message

Example prompts

What have we already decided about this product launch, and what are the open questions?
Search my saved research for pricing, competitor, and market insights, then summarize the most relevant findings.
What did I last work on for the MCP connector submission, and what should I do next?
Save this finding to memory: our public MCP connector uses OAuth, exposes 10 reviewed tools, and passed the latest smoke checks.
Find anything I have already researched about MCP connector approval requirements and give me the top 3 next steps.

Data handling

Agentic Memory stores memory intentionally; persistent memory is the product.
Stored memory can include saved research, conversation notes, and project context that users explicitly ask the connector to save or search.
Transport is encrypted over HTTPS/TLS on the hosted public endpoint.
The connector does not provide live web browsing. Research search operates over previously saved research memory.
The connector is not intended for users to access, view, or share personal health data.

Self-serve debugging

Use https://mcp.agentmemorylabs.com/health to confirm the hosted service is reachable.
If Claude cannot connect, confirm the URL is https://mcp.agentmemorylabs.com/mcp-claude and includes no extra path segments.
If OAuth fails, disconnect and reconnect the connector so Claude can register a fresh OAuth client.
If a reviewer/demo account cannot see expected sample data, verify the reviewer is signed into the provided account and not a personal workspace.
If Claude lists fewer than 10 tools, refresh connector metadata before retrying the task.
If a memory search returns no useful results, ask Claude to call list_project_and_repo_ids first, then retry with the discovered project or repository identifier.

Troubleshooting

If OAuth fails, disconnect and reconnect the connector so the client can register or refresh its OAuth client.
If tools are missing, refresh the connector metadata and confirm the server URL matches the platform-specific URL on this page.
If search returns no relevant memory, try a broad prompt first with search_all_memory, then drill down with saved research or conversation search.
If the service reports a temporal retrieval error, retry after backend health recovers; public research and conversation retrieval fail closed rather than silently returning dense-only results.
Do not paste API keys, passwords, or private repository contents into public support issues.