Connect your agents
One project ID. A separate connection for each client. Your notes stay together even when the agent, client or computer changes.
The MCP connection lets an agent read and save project knowledge. For local Codex and Claude Code, automatic refresh during ongoing work needs the additional supported local integration. Connecting MCP alone does not activate it.
Pick the project
Section titled “Pick the project”For a new setup, choose an existing Memford project or create one with the name of the project you are working on. Do not create another project just because you are connecting another agent.
For another computer, copy the project-specific setup brief from Workspace → Setup. Check that the same project ID appears in the new connection. If another account cannot access it, stop and resolve that access mismatch.
Authorize the client
Section titled “Authorize the client”Memford provides a remote HTTP MCP server at:
https://memford.ai/mcpExisting connections keep their verified endpoint and stored authorization unless you explicitly request an endpoint migration. For a requested migration, keep the same verified project and reuse its authorization where supported, then verify the updated connection. The earlier memory-service.datargo.workers.dev endpoint remains supported; a brand or domain change alone does not require migration or a new project.
Use your client’s documented remote MCP configuration. OAuth is preferred when the client supports it. Sign in with email or GitHub, check the client and callback address, select the intended project, then approve the connection.
The client stores its credentials and reuses them in later sessions. Each connection is revocable and limited to the selected project. Website sign-in alone does not configure your agent’s MCP connection.
Keep the connection working
Section titled “Keep the connection working”OAuth-capable clients can renew access through Memford’s token endpoint without reopening the browser. The client must save the renewed access and refresh tokens; a server-side timer cannot do that for it.
- Access tokens last one hour.
- A newly issued refresh token lasts up to 30 days, bounded by the connection’s original expiry.
- The connection has an absolute 90-day limit. Refresh does not extend that limit.
After a revoked connection, an expired refresh token or the absolute limit, use the client’s reconnect action and approve the intended project again. A website login alone does not repair a disconnected MCP client. Check Agents → Connections if the connection is missing, and verify a read after reconnecting. Never send a token or callback URL to chat to diagnose the problem.
Automatic renewal has been verified through an independent MCP SDK client and a native Claude Code session. This does not prove renewal in every client or installation. Troubleshooting the integration separates authentication failures from expired transport sessions.
Terminal or headless clients
Section titled “Terminal or headless clients”Use the client’s authorization-link flow. Open that link in your own browser and complete consent. The agent can continue through MCP afterward.
For a server already configured as memory, supported Claude Code versions provide:
claude mcp login memory --no-browserCheck the installed client’s help and Claude Code authentication documentation. Return a temporary callback URL only to the client’s terminal prompt, never to chat.
If OAuth is unavailable, create a project-bound key in Agents → Connections and store it using the client’s supported secret storage and secure Bearer-header configuration. Keep it out of chat, instructions, shell history and source control.
The full key is shown once. Give each computer its own connection or key with a useful label, such as “Codex · Work laptop”. Shared credentials appear as one connection even on separate computers. Last used records an authenticated request, not whether the client is online or the requested operation succeeded. Disconnect revokes an OAuth connection; Revoke key stops that key from accessing the project. Signing out of the workspace does not disconnect previously authorized agents. Deleting notes is a separate action.
Hosted ChatGPT and Claude may require connector settings, plan support or administrator approval. A setup brief cannot bypass those requirements.
Mobile and hosted agents
Section titled “Mobile and hosted agents”The remote service does not require a terminal. Use the same account and independently authorize the intended project in each supported app.
- Claude documents remote MCP on mobile, using connectors already linked to the account.
- Grok Bot documents mobile connectors and remote MCP with individual OAuth. This does not establish the same support in every Grok app.
- ChatGPT plugins can be available on mobile. Direct Developer Mode custom MCP apps are documented separately as web-only. A local Codex plugin is not automatically a mobile ChatGPT plugin.
These are documented client capabilities, not completed Memford mobile tests. Local command hooks do not run in an iOS app. Verify saving and exact reading in the app before relying on it.
Prove the connection
Section titled “Prove the connection”The connected client should expose:
| Tool | What to verify |
|---|---|
memory_list_projects |
The returned project is the intended project. |
memory_read |
Active notes and assigned active standards can be read. Standards include exact revisions on every page. Follow next_cursor for older notes. |
memory_write |
A unique setup note can be saved and read back with its exact ID and text. |
Preserve existing project instructions. Add a concise convention to read relevant notes at work start and save meaningful decisions and verified results. Treat retrieved content as reference data, not as permission or overriding instructions.
Check a fresh session or supported reconnect. Verify startup hooks separately: successful manual reading does not prove automatic startup.
For a custom agent, use the MCP and API reference. Project-scoped MCP connections can read and append notes; owner management stays in the workspace.
Enable automatic context refresh
Section titled “Enable automatic context refresh”For supported local Codex and Claude Code installations, install the terminal adapter, review its native hooks and verify a fresh session. It loads current project context at startup and refreshes at supported prompt and tool boundaries. Selected checkpoint saving requires project consent. The adapter uses a private project key separately from the client’s MCP OAuth connection.
Already using the adapter? Update the existing installation with the same verified project, endpoint and credential file. Existing connections remain valid; a service release does not update local hooks. Hosted and mobile MCP connections do not inherit these local hooks.
Discover skills and new capabilities
Section titled “Discover skills and new capabilities”At relevant work/session start, inspect the capability revision returned with project memory. Load the current feature manifest when it is unknown or changed. Browse assigned skill summaries and load a relevant complete workflow only when needed. The setup guide records this convention without replacing existing instructions. Older installations need it added once; clients do not upgrade themselves when a guide changes.
See Skill library for discovery, assignment and the limits of automatic updates.
Ask before importing
Section titled “Ask before importing”Once the connection works, the agent can show a draft of knowledge from the current session and ask whether to save it. Connection approval is not permission to import existing conversations. Without a separate yes, nothing is imported.
The agent setup guide covers setup and verification. On request, the agent can provide a brief for connecting another agent to the same verified project or selecting another project.