Borrowing it
Nothing to install: this file belongs to cogell/mural-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cogell/mural-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/cogell/mural-mcpWrote 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/cogell/mural-mcp/claude-md)<a href="https://agentmods.dev/instructions/cogell/mural-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/cogell/mural-mcp/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.1 | $0.00694 | $0.00694 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
mural-mcp 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 7d 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 — 77 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.
Package Manager
Use pnpm for all package management operations.
Common Development Commands
Building and Development
pnpm run build- Compile TypeScript to JavaScript inbuild/directorypnpm run dev- Watch mode compilation with TypeScriptpnpm start- Run the compiled MCP serverpnpm run prepublishOnly- Pre-publish build step
Testing and Debugging
- Test the MCP server manually:
node build/index.js - Use MCP inspector:
npx @modelcontextprotocol/inspector node build/index.js - Test OAuth flow: Set environment variables and run
pnpm start
Architecture Overview
This is a Model Context Protocol (MCP) server that provides integration with the Mural visual collaboration platform through OAuth 2.0 authentication.
Core Components
-
MCP Server (
src/index.ts) - Main entry point that:- Uses stdio transport for MCP communication
- Implements 4 tools:
list-workspaces,get-workspace,test-connection,clear-auth - Handles environment variable validation for
MURAL_CLIENT_ID - Uses Zod for input validation
-
OAuth Handler (
src/oauth.ts) - Manages authentication:- Implements OAuth 2.0 with PKCE (Proof Key for Code Exchange)
- Stores tokens in
~/.mural-mcp-tokens.json - Automatically refreshes expired tokens
- Runs temporary HTTP server on port 3000 for OAuth callback
-
Mural API Client (
src/mural-client.ts) - API interaction:- Makes authenticated requests to
https://app.mural.co/api/public/v1 - Handles token refresh automatically
- Provides workspace listing and retrieval methods
- Makes authenticated requests to
-
TypeScript Types (
src/types.ts) - Type definitions for:- Mural API responses (
MuralWorkspace,MuralWorkspacesResponse) - OAuth flow data (
OAuthTokens,PKCEChallenge, etc.)
- Mural API responses (
Environment Variables
Required:
MURAL_CLIENT_ID- OAuth client ID from Mural Developer Portal
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.
- 7d ago First seen · 77 lines · 694 tokens per session scan A 7435aeccd8be
mural-mcp CLAUDE.md is an instructions file published in the GitHub repository cogell/mural-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 694 tokens to every session, about $0.0035 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
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.