Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/gleanwork/configure-mcp-server/claude-mdgit clone --depth 1 https://github.com/gleanwork/configure-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/gleanwork/configure-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/gleanwork/configure-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/gleanwork/configure-mcp-server/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01956 | $0.01956 |
| Opus 5 | $0.00978 | $0.00978 |
| Sonnet 5 | $0.00391 | $0.00391 |
| Haiku 4.5 | $0.00196 | $0.00196 |
Grade A, and why
configure-mcp-server CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Overview
This is a CLI tool that configures MCP (Model Context Protocol) clients to connect to Glean's MCP servers. The package is published as @gleanwork/configure-mcp-server on npm and supports both local MCP servers (stdio transport) and remote MCP servers (HTTP transport with OAuth/DCR or bearer tokens).
Development Commands
Building
npm run build # Clean build directory, compile TypeScript, and copy templates
npm run watch # Watch mode for TypeScript compilation
The build process:
- Removes the
build/directory - Compiles TypeScript from
src/tobuild/ - Copies markdown templates from
src/init/templates/markdown/tobuild/init/templates/markdown/
Testing
npm test # Run tests once with Vitest
npm run test:watch # Run tests in watch mode
npm run test:all # Run linting, type checking, and tests
Tests are located in src/test/**/*.test.ts and use Vitest.
Linting and Formatting
npm run lint # Run all linters (ESLint, package.json, TypeScript)
npm run lint:eslint # Run ESLint on TypeScript files (with --fix)
npm run lint:ts # TypeScript type checking (noEmit)
npm run format # Format all files with Prettier
Running Locally
npm run go -- [command] # Run the CLI using ts-node without building
node build/index.js [command] # Run the built CLI
Single Test Execution
To run a single test file:
npm test -- src/test/configure.test.ts
Architecture
Three Main Commands
-
local- Configures local MCP server (stdio transport)- Requires:
--client,--token,--instance(or--env) - Uses
@gleanwork/local-mcp-serverpackage
- Requires:
-
remote- Configures remote MCP server (HTTP transport)- Requires:
--client,--url - Optional:
--token(if not provided, uses OAuth with Dynamic Client Registration) - Uses
mcp-remotepackage as a proxy
- Requires:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 184 lines · 1,956 tokens per session scan A d85114b0a576
configure-mcp-server CLAUDE.md is an instructions file published in the GitHub repository gleanwork/configure-mcp-server (3 stars, last pushed 3d ago), licensed MIT. It adds 1,956 tokens to every session, about $0.0098 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.