Skip to main content

​
Memex Plugin

This is the Memex plugin for Memex.Garden, a bookmarking second brain for humans and agents. You can save, transcribe, summarize and search anything you come across. Websites, notes, web highlights, YouTube, X, TikTok, Instagram, PDFs, Reddit or images. Here is our Privacy Policy and our docs.

​
How to install

  1. Download the plugin
  2. Extract the zip, or clone this repo and use it directly.
  3. Start Codex from the extracted directory or repo root.
  4. Open Codex’s plugin directory.
  5. Select the Memex Plugins marketplace.
  6. Install Memex.
  7. Connect Memex when your client prompts for authentication.
  8. You’re done. You can now use Memex from your agent.

​
Example prompts

  1. Search my Memex library for pages about MCP authentication and summarize the top results.
  2. Save https://docs.memex.garden/general/authentication into Memex, and tag it with #tutorials

​
Handoff command

The plugin exposes a dedicated slash command for unprocessed handoffs:
That command discovers the cloud-side handoff-listing action and invokes it through execute_action. It fetches pending handoffs by default, resolves the saved Codex project for each handoff, and creates one fresh task per handoff. The coordinator never performs or drains the handoff itself. Each created task owns only its handoff and drains it after the requested work is complete.

​
Scheduled handoff polling

In Memex, select Codex in Integrations and complete the OAuth pairing. Once Memex shows Codex as connected, Continue opens the Set up automation step. Set up now opens Codex with a prompt to create a scheduled job that runs /memex:fetch-handoffs every 10 minutes. The job polls the durable queue and routes approved pending handoffs without a local Realtime connection.

​
Authentication

The default hosted Memex MCP endpoint is:
  • https://memex.garden/api/mcp
Authentication is OAuth-first. When the plugin calls Memex for the first time, your client should start the Memex sign-in flow. OAuth clients should register as Memex Codex plugin and, when custom registration metadata is supported, include memex_client_source: "memex_codex_plugin" so Memex can show the connection as this plugin rather than a generic Codex cloud agent. In Codex CLI, use:
After signing in, start a new thread so the refreshed MCP session and plugin skills are available. Advanced fallback: if OAuth is unavailable in your client, export credentials before launching the agent. Bearer token mode:
You can also use an API key:
Endpoint override:
Local backend example:
Auth precedence:
  • OAuth is the default path when supported by the client
  • MEMEX_BEARER_TOKEN is the first fallback when present
  • otherwise the MCP server may use MEMEX_API_KEY
  • MEMEX_USER_ID is optional
  • MEMEX_MCP_URL defaults to https://memex.garden/api/mcp
Auth docs: If a client asks for the raw MCP server URL, use https://memex.garden/api/mcp for production or http://localhost:8787/mcp for local development.

​
Docs