Connect NotebookLM to Hermes Agent and OpenClaw with Composio

阅读中文版

First check which NotebookLM account you have

Composio’s notebook_lm toolkit connects to NotebookLM Enterprise, which Google now calls Gemini Notebook Enterprise. It works with notebooks in your Google Cloud project. A personal NotebookLM account or a Google AI subscription alone does not meet these requirements, and your personal notebooks do not appear automatically.

Google: Gemini Notebook Enterprise overview

What you need before connecting

• A Google Cloud project with billing enabled and the Discovery Engine API enabled.
• An administrator who has configured the project’s identity provider, granted you the Cloud NotebookLM User role, and assigned an Enterprise license for the relevant region.
• The Google account that has access to that licensed project and its notebooks. Record the numeric project number from Google Cloud; the notebook API uses it in resource paths.
• A deployment compatible with the connector’s global location. Composio currently describes this toolkit as global-location only; Google’s separate US/EU options do not prove this connector supports them.

Google Cloud setup · Enterprise licensing

Authorize NotebookLM in Composio

1. Open your own Composio project and select the NotebookLM toolkit (slug: notebook_lm). Choose Composio-managed OAuth unless your organization requires its own OAuth application.
2. Use the toolkit-specific connection flow to provide the Google Cloud Project ID or Number field. Supply the project number for the Enterprise project you intend to use. This project field is separate from your Composio API key.
3. Open the generated Connect Link, sign in with the licensed Google account, and review the permissions. Managed OAuth supplies the OAuth application, so registering your own client is unnecessary for the default flow.
4. Confirm the connected account is ACTIVE. The MCP configuration and connected account must use the same Composio project and user ID. A connection created under another identity will not automatically become available to your agent.

The toolkit metadata checked on October 3, 2026 required a connection field named prefix.one, labeled Google Cloud Project ID or Number. If your connection screen does not collect it, use Composio’s toolkit-specific flow or ask Composio support how to provide it. Repeating Google consent does not fill in missing project context.

NotebookLM toolkit and current tools · Composio-managed OAuth · Connected-account setup

Using OpenClaw Launch

Hermes Agent and OpenClaw share the Integrations catalog on OpenClaw Launch. Search for NotebookLM there. The current generic managed-OAuth flow does not collect the required Google Cloud project field, so the catalog entry alone is not a complete one-click Enterprise setup.

Browse integrations

Connect your own agent through MCP

In the same Composio project, create a single-toolkit MCP configuration for notebook_lm with your auth configuration. Generate the MCP URL for the same user ID that owns the ACTIVE connected account. Copy the exact generated URL and use your own project API key for x-api-key. Keep both private.

Composio single-toolkit MCP setup

Hermes Agent

Store COMPOSIO_API_KEY with your own key in ~/.hermes/.env. Merge this entry into mcp_servers in ~/.hermes/config.yaml, preserving existing servers. Replace the URL placeholder with the generated Composio MCP URL; Hermes resolves the environment variable in the header when it connects.

mcp_servers:
  composio:
    url: "YOUR_GENERATED_COMPOSIO_MCP_URL"
    headers:
      x-api-key: "${COMPOSIO_API_KEY}"
    connect_timeout: 60
    timeout: 180

Start a fresh chat with the command below, or run /reload-mcp inside an existing session. This loads the MCP tools; it does not replace the Google authorization completed above.

hermes chat

Hermes MCP configuration reference

OpenClaw

Use a current OpenClaw release that includes the mcp CLI. Replace the URL and key placeholders with your own values. Avoid leaving the key in shared shell history. The probe checks MCP discovery; a successful probe does not prove the Google account can access your project.

openclaw mcp add composio \
  --url "YOUR_GENERATED_COMPOSIO_MCP_URL" \
  --transport streamable-http \
  --header x-api-key=YOUR_COMPOSIO_PROJECT_API_KEY
openclaw mcp probe composio

OpenClaw MCP registry commands

Verify with a read-only notebook request

Ask the agent to call NOTEBOOK_LM_LIST_RECENT_NOTEBOOKS with an empty input object. It lists recently viewed notebooks, up to 500, rather than every notebook in your organization. A successful empty list can be valid when there are no recent notebooks.

Use Composio’s notebook_lm toolkit to list my recent Enterprise notebooks. Return their titles and notebook IDs. Do not create, change, share, or delete anything. If authorization or project context is missing, show the exact error and connection step required.

What the connector can do

• Create, retrieve, share, and delete notebooks, and list recent notebooks.
• Add raw text sources, upload a plain-text source file, inspect source ingestion, and retrieve or delete sources.
• Create or delete an audio overview. Generation is asynchronous: a started operation is not a finished audio download.

The current catalog lists 11 tools. It does not list a notebook query or chat action. Its file-upload tool accepts text/plain; do not assume that the richer NotebookLM interface’s PDF or Google Drive imports are available through this tool. Confirm notebook and source IDs before any write, share, or delete operation.

Common connection problems

Frequently asked questions

Related guides

• Hermes Agent + Composio setup
• OpenClaw + Composio setup
• Google Docs integration
• Managed Hermes hosting