Secure project authorization

Connect ChatGPT or LocalEndpoints to MemoryEndpoints.com

Connect either app to one MemoryEndpoints project. When the connected app opens MemoryEndpoints, sign in on MemoryEndpoints, choose the project, and approve read access with optional write access. Your password stays on MemoryEndpoints. This setup page is credential-free; do not enter credentials here.

Before connecting: You need an existing MemoryEndpoints human account with an active, entitled account, company, workspace, and project. If any part is missing or inactive, ask your MemoryEndpoints administrator to provision or restore it before reconnecting.

The connected app requests the permissions. The consent page approves every listed permission or cancels; it does not add or remove individual permissions. For a read-only demonstration, continue only when the request lists memory:read without memory:write.

Demo privacy: workspace_status shows human-facing account, company, workspace, and project labels, and memory_search returns bounded memory summaries. During screen sharing, use a dedicated project whose labels and memory are non-sensitive.

The site's interactive tour uses session-only mock data. It does not test this real OAuth connection, consent flow, or MCP tools.

ChatGPT

1. In ChatGPT developer mode, create a custom app and enter https://memoryendpoints.com/mcp.
2. Choose OAuth, scan tools, sign in with a normal human account, select one account/company/workspace/project, and approve the requested permissions.
3. Confirm that ChatGPT lists exactly workspace_status, memory_search, and memory_remember.

Standard initialize, tools/list, and workspace_status provide only a basic ChatGPT transport/status proof; they do not complete functional read acceptance.

LocalEndpoints Connect

1. Install a qualified LocalEndpoints Connect build.
2. Choose MemoryEndpoints and approve the same exact project-scoped permissions.
3. Complete discovery, status, search, optional save, refresh rotation, and disconnect verification.

server/discover, tools/list, and workspace_status provide only a basic LocalEndpoints transport/status proof with MCP 2026-07-28; they do not complete functional read acceptance.

For either app, complete authenticated human read acceptance with one bounded, non-sensitive memory_search. Use memory_remember only after separate explicit write authorization.

Rooms, meetings, directories, peers, projects, notifications, and coordination operations are never Connect tools.