Glean's plugin for Claude Code and Claude Cowork. This repo is a single-plugin marketplace.
Today it ships one plugin:
glean-vnext — adds two static tools, find_skills and run_tool, that
let the agent discover Glean-hosted skills for enterprise apps (Jira, Slack,
Google Workspace, Salesforce, etc.) and invoke their downstream tools via
Glean's MCP gateway. Once the user has authenticated, the plugin also
surfaces a small allow-list of Glean's first-class tools — currently
search and read_document — directly, with schemas pulled from the
remote MCP server./plugin marketplace add gleanwork/glean-plugins-vnext
/plugin install glean-vnext@glean-plugins-vnext
gleanwork/glean-plugins-vnext.The first tool call triggers OAuth sign-in to Glean via the setup tool.
The agent's skill walks the user through the sign-in URL and paste-back
flow. After sign-in, OAuth credentials are cached to ~/.glean/ and reused
across sessions — you won't be prompted again until the refresh token
expires.
# Claude Code
/plugin marketplace update glean-plugins-vnext
# Cowork: the plugin picker has a "Sync" / "Check for updates"
# button on the marketplace entry.
You can point the marketplace at a specific git branch, tag, or commit:
# Install from a specific branch (e.g. a PR branch)
/plugin marketplace add gleanwork/glean-plugins-vnext@branch-name
/plugin install glean-vnext@glean-plugins-vnext
# Or update an existing marketplace to a different branch
/plugin marketplace remove glean-plugins-vnext
/plugin marketplace add gleanwork/glean-plugins-vnext@branch-name
You can also pin to a branch in settings.json:
{
"marketplaces": [
{
"name": "glean-plugins-vnext",
"source": "https://github.com/gleanwork/glean-plugins-vnext",
"sourceType": "git",
"branch": "mohit-baseline-marketplace-layout"
}
]
}
For local development, point the marketplace at your local checkout instead:
/plugin marketplace add /path/to/glean-plugins-vnext
Then just git checkout whichever branch you want to test.
~/.glean/mcp-credentials.json and retry.GLEAN_MCP_SERVER_URL is required — the plugin's .mcp.json wasn't
picked up by the host. Reinstall; if that fails, open an issue.Prerequisites: Node 22+, npm.
npm install
npm test # vitest
npm run typecheck # tsc --noEmit
npm run build # esbuild → plugins/glean/dist/index.js
Source is at the repo root (src/, tests/, scripts/). Packaged
runtime lives under plugins/glean/. See the Layout section below.
version in plugins/glean/.claude-plugin/plugin.json.npm test && npm run typecheck — verify clean.git tag v<version>
git push && git push --tags
.claude-plugin/
marketplace.json Top-level marketplace manifest for Claude Code
/ Cowork. Points at ./plugins/glean as the
plugin source.
plugins/glean/
.claude-plugin/
plugin.json Plugin manifest — name, version, description
.mcp.json MCP server invocation read by Claude Code /
Cowork. Source of truth.
dist/index.js Built server bundle (every dep inlined; produced
by `npm run build`; checked in)
skills/glean_run/ Skill that tells the agent how to use the
tools. Uses the open SKILL.md standard.
start.sh Bash launcher that anchors PROJECT_DIR to the
host's spawn cwd, then execs node on the bundle
package.json Minimal "type": "module" manifest so Node
treats dist/index.js as ESM at runtime
src/ TypeScript sources for the MCP server
tests/ Vitest suite
scripts/ build.mjs — esbuild bundler
package.json Top-level dev config — deps, npm scripts
tsconfig.json TypeScript config for the dev tree
Apache 2.0. See LICENSE.
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub gleanwork/glean-plugins-vnextAccess Glean's developer documentation - search API references, SDK guides, and integration tutorials via the Glean Developer Docs MCP Server.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Plugin that includes the Figma MCP server and Skills for common workflows
Production-grade vibe coding suite. Structured workflows from discovery to deployment: start, build, ship, fix, refactor.
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
Claude Code settings and skills for spec-driven development workflows