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/keithdev21/business-central-mcp/claude-mdgit clone --depth 1 https://github.com/keithdev21/Business-Central-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/keithdev21/business-central-mcp/claude-md)<a href="https://agentmods.dev/instructions/keithdev21/business-central-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/keithdev21/business-central-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 | $0.06026 | $0.06026 |
| Opus 5 | $0.03013 | $0.03013 |
| Sonnet 5 | $0.01205 | $0.01205 |
| Haiku 4.5 | $0.00603 | $0.00603 |
Grade A, and why
Business-Central-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 3d 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.
This is a copy
100% identical to Business-Central-MCP-Integration CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BC MCP Server v2
Development Philosophy
This project is NOT released and in active development:
- Always choose the best solution, not the quickest compromise
- Refactor aggressively when architecture is flawed
- Fix problems properly, not with workarounds
- No stubs, mocks, or skeleton implementations -- everything must be fully functional
- No backwards compatibility concerns -- make breaking changes freely
Quick Start
Project Location
- v2 source:
U:/git/bc-mcp/ - v1 reference (deprecated):
C:\bc4ubuntu\Decompiled\bc-poc\ - Decompiled BC28:
U:/git/bc-mcp/reference/bc28/decompiled/ - Decompiled BC27:
C:\bc4ubuntu\Decompiled\(various Microsoft.Dynamics.* directories) - Architecture spec:
C:\bc4ubuntu\Decompiled\bc-poc\docs\superpowers\specs\2026-04-03-bc-mcp-v2-design.md
BC Test Environments
| BC28 | |
|---|---|
| URL | http://cronus28/BC/?tenant=default |
| Username | sshadows |
| Password | 1234 |
| Auth | NavUserPassword |
| License popup | Auto-dismissed |
| Protocol version | 15041 |
Uses NavUserPassword authentication (not Windows/NTLM).
Essential Commands
cd U:/git/bc-mcp
npx tsc --noEmit # Type check
npx vitest run # Unit + protocol tests (292 tests)
npx vitest run --config vitest.integration.config.ts # Integration tests against real BC28 (111 tests)
npm start # HTTP server on port 3000
npm run start:stdio-direct # Direct stdio for Claude Desktop
Rules
- Use Windows paths with forward slashes in bash
- NEVER use
2>nul(creates undeletable files on Windows) - NEVER use emojis -- Windows rendering issues
- Always run
npx tsc --noEmitafter changes - Run integration tests after any protocol-level change
- ESM project -- use
.jsextensions in all imports
Protocol Verification Procedure
CRITICAL: Always verify protocol behavior against decompiled BC source, not v1 code.
V1 had several incorrect assumptions (per-page connections, SaveValue not echoing, etc.). When implementing or debugging any BC protocol interaction:
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.
- 3d ago First seen · 361 lines · 6,026 tokens per session scan A ef4f890cf7c6
Business-Central-Mcp CLAUDE.md is an instructions file published in the GitHub repository keithdev21/Business-Central-Mcp (0 stars, last pushed 24d ago), licensed MIT. It adds 6,026 tokens to every session, about $0.0301 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Business-Central-MCP-Integration CLAUDE.md, differing in 0 lines, and is treated as a copy.
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.