notebooklm
01MCP server Claude CodeCodexCursor +2
NotebookLM research automation — CLI, MCP server, and Claude Code Skill. Runs locally from the notebooklm-skill Python package.
MCP server Claude CodeCodexCursor +2
NotebookLM research automation — CLI, MCP server, and Claude Code Skill. Runs locally from the notebooklm-skill Python package.
Skill Claude CodeCodex
Automate source-grounded research with Google NotebookLM. Create notebooks from URLs, text, or local files; ask cited questions; run fast or deep web research; create articles and social drafts; and generate or download audio, video, cinematic video, slides, reports, study guides, quizzes, flashcards, mind maps…
claude-world/director-mode-lite
Plugin Claude Code
Bundles 36 skills, 14 agents · 3,213 tokens together
Guidance-first Director workflows for Claude Code, Codex CLI, and Grok Build, with portable session relay and native adapters.
claude-world/claude-skill-antivirus
Skill Claude Code
A simple skill that helps with greeting messages.
claude-world/claude-world-studio
MCP server Claude CodeCodexCursor +2
One of 4 in .mcp.json
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
claude-world/claude-world-studio
MCP server Claude CodeCodexCursor +2
One of 4 in .mcp.json
MCP server "trend-pulse" as configured in claude-world/claude-world-studio. Runs locally from the trend-pulse[mcp] Python package.
claude-world/claude-world-studio
MCP server Claude CodeCodexCursor +2
One of 4 in .mcp.json
MCP Server with 15 browser tools for Claude Code — powered by Cloudflare Browser Rendering. Runs locally from the cf-browser-mcp Python package.
claude-world/claude-world-studio
MCP server Claude CodeCodexCursor +2
One of 4 in .mcp.json
NotebookLM research automation — CLI, MCP server, and Claude Code Skill. Runs locally from the notebooklm-skill Python package.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: