AI connections

Connect authorized archive records to external AI such as ChatGPT or Claude for searching, organizing and writing. Server and PC-local archives use different connection methods.

Server versus PC local

• Server MCP: Connect server personal/organization archives allowed for the signed-in account, using a public HTTPS address and OAuth approval.
• PC-local MCP: Connect the Windows app’s local archive to an AI app on the same PC through stdio or localhost HTTP. Alfred sign-in is not required for local connections.
• Browser local: Browser records are separate from server and PC archives. The web cannot run PC-local MCP, and no bridge connects browser archives to external MCP.

Entering 127.0.0.1 in a Claude web connector or ChatGPT server connection does not connect your PC archive. Configure PC-local access in an AI app on that same PC that supports local MCP.

Before connecting

1. Open the archive containing the materials. For server archives, also check the signed-in account.
2. Check permissions under App menu › Settings › AI access for current archive. Your account must be authorized to manage this setting to change it.
3. Start with the read access you need. Choose writing/editing only when necessary.
4. Check whether the external AI plan, sign-in and organization policy allow custom MCP connections. Alfred cannot enable connections or operations the external service does not offer.

AI can access only authorized archives, within your current role and explicitly approved scopes. It cannot expand its own permissions.

Connect a server archive

Set up and manage server connections under [App menu › Account › External AI connections] in the web app.

1. Finish sign-in verification in the Alfred app.
2. Open App menu › Account › External AI connections and select Connect for the AI service. Copy the MCP address and open the service’s settings.
3. Add a custom MCP server or connector. Use Alfred as its name, the server MCP address below, and OAuth authentication.
4. On Alfred’s approval screen, read the Account to connect, archives and requested read/document edit/organization management/workspace management permissions. Approve only what is needed.
5. Check that connection and tool verification finish in the external service. Copying an address or opening an app is not a completed connection.

MCP address for server archives

Successful copying shows “MCP address copied.” If the browser denies copying or it fails, the address is selected and “Automatic copy failed. Copy the selected address manually.” is shown. Use Ctrl+C or your device’s copy menu.

Add in ChatGPT

1. Select ChatGPT Connect in Alfred or open ChatGPT Plugins.
2. In an account supporting custom MCP servers, select + › Add custom MCP server.
3. Enter Alfred and the HTTPS address above, then authorize Alfred with OAuth. Review the service’s risk warning and requested permissions.
4. Finish creation/installation after tool verification, then select Alfred in a new conversation.

Custom MCP creation and read/write support depend on the ChatGPT plan and organization policy. If a menu is missing or actions are restricted, check account requirements in OpenAI’s official connection guide. Accounts using the previous Apps screen should follow its custom-app procedure.

Add in Claude

1. Select Claude Connect in Alfred or open Claude Customize › Connectors.
2. In an account supporting custom connectors, select + Add › Add custom connector.
3. Enter Alfred and the HTTPS address above. Check detected authentication settings and authorize through OAuth sign-in.
4. If Connect appears after adding, select it to finish account authorization. Enable the connector in the conversation you want.

Organization accounts may require an owner or another service-defined administrator to add the connector first. Follow Claude’s official custom-connector guide. Web connectors and Claude Desktop PC-local MCP are configured separately.

Connect a PC-local archive

Use local MCP (stdio/localhost) in Windows settings. This is separate from copying a server MCP address.

1. Open the PC-local archive you want in the Windows app.
2. Open App menu › Settings › AI access for current archive.
3. Select Read only or Allow reading and editing.
4. Follow a method supported by an AI app on the same PC below.

stdio

1. Expand stdio connection settings.
2. Select Copy stdio configuration.
3. Register the copied content in the MCP settings of an AI app on the same PC supporting local MCP. The AI app runs the installed Node and MCP.
4. Check that the AI app loads the tools and can read the current archive.

Use the executable, arguments and archive path displayed by the app. Do not paste settings from another PC or paths from an internet example unchanged.

localhost HTTP

1. Check the HTTP port. 0 selects automatically; a fixed port must be within 1–65535.
2. Select Start HTTP and confirm the running state and actual address appear.
3. Select Copy HTTP configuration · Includes token and register it in a trusted AI app on the same PC.
4. Select Stop HTTP when finished.

HTTP configuration includes an authentication token. Never paste it into inquiries, shared documents or public repositories. HTTP is available only at this PC’s 127.0.0.1 while the app is open. Switching archives, disabling AI access or closing the app ends it; merely closing settings does not.

An automatic port can change after restarting, and the authentication token changes every time. Copy configuration again even with a fixed port. An AI-launched stdio process can remain after the Alfred window closes; to block access, disable the archive’s AI permission and end the connection in the AI app too.

Confirm the connection

• Ask AI to list permitted archives or read one small record, verifying the correct account and archive.
• Do not assume a read-only connection can edit. Reauthorize at the same server address if an existing read-only grant needs additional permission.
• Refresh server status and connection permissions after changing settings. Do not treat failure as success.
• If AI writes a document, reopen its actual title, body and links in Alfred. The AI reply alone does not prove saving.

What is transferred and how to disconnect

Content AI searches or reads in an archive you permit is transferred to the connected ChatGPT or Claude service.

This can include more than the body: tool responses such as titles, search results, sources and related-record information may be transferred. Check the external service’s privacy policy and terms before handling sensitive information.

Disconnect at any time under [App menu › Account › External AI connections]. The server immediately blocks that connection’s access. (Content already sent to the external AI service is not recalled.)

Select and confirm Disconnect in the server connection list. Changing the browser’s sign-in account or signing out of Alfred is different from revoking an existing MCP grant. Connecting another account requires new authorization.

Existing AI connections cannot access an archive whose permission is revoked. Leaving one organization does not mean all permissions to your other personal archives disappear.

Request schedule creation

Before registering explicit schedules, review the date/time zone when the statement was made, whether it is an appointment or deadline, cancellation/completion and duplicates. Not every dated sentence is a schedule.

If the archive owner enabled schedule automation for new MCP documents, the AI registering the document must read the source and existing schedules and finish the subsequent registration procedure. Successful document saving and completed schedule analysis are different. Pending or blocked analysis is not complete; check the actual result.

This is not a server feature that watches and automatically infers from every direct app/web save, backup import or existing-document edit. Existing schedule edits/cancellations and actual event creation require separate confirmation.

If connection fails

Check address copying, current account, archive AI permission and OAuth scopes first. Ensure you did not put a PC-local address in a web connector.

If unresolved, read AI connection troubleshooting or send private feedback. Do not send tokens or entire source documents.