ChatGPT / OpenAI setup
Use this endpoint when configuring the Agentic Memory ChatGPT/OpenAI MCP
server: https://mcp.agentmemorylabs.com/mcp-openai
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 hosted connector uses OAuth 2.0 authorization code flow with PKCE.
- Default OAuth scope:
mcp:tools. - No local infrastructure is required for the hosted ChatGPT app path.
ChatGPT use
- Connect Agentic Memory from ChatGPT developer/app setup using the MCP server URL above.
- After connecting, refresh tool metadata so ChatGPT sees the reviewed public tool contract.
- Use broad memory prompts first, then ask follow-up questions when a specific saved research or conversation result needs drill-down.
Available tools
The public connector exposes 10 reviewed tools. Admin, indexing, and maintenance tools are not part of this public surface.
Read tools
search_codebaseget_file_dependenciestrace_execution_pathsearch_all_memorylist_project_and_repo_idssearch_web_memorysearch_conversationsget_conversation_context
Write tools
memory_ingest_researchadd_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.
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.