Install
$ agentstack add mcp-onwardplatforms-infracodebase-mcp ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
@infracodebase/mcp
MCP server bringing infracodebase's compliance, rulesets, and governance to your AI agent. Works with Claude Code/Desktop, Cursor, or any of your favorite MCP client.
Quickstart
Get a token from infracodebase.com/settings/tokens, then add the server to your MCP client with the token in its env.
For Claude Code:
claude mcp add infracodebase --env INFRACODEBASE_TOKEN=icb_pat_xxx -- npx -y @infracodebase/mcp@latest
For Claude Desktop / Cursor and other clients, add to your mcp.json:
{
"mcpServers": {
"infracodebase": {
"command": "npx",
"args": ["-y", "@infracodebase/mcp@latest"],
"env": { "INFRACODEBASE_TOKEN": "icb_pat_xxx" }
}
}
}
Self-hosted
Add INFRACODEBASE_API_URL to the same env block (or pass --api-url)
"env": {
"INFRACODEBASE_TOKEN": "icb_pat_xxx",
"INFRACODEBASE_API_URL": "https://infra.your-company.com/api/v1"
}
No public npm access? Run from a clone instead - same server. Build it, then point your client at node /abs/path/to/mcp/dist/index.js with the same env:
git clone https://github.com/onwardplatforms/infracodebase-mcp.git
cd infracodebase-mcp && npm install && npm run build
Configuration
Token and API URL resolve from flag → env var → default. There is no stored config file: the MCP client owns the configuration and passes it in via env.
| Flag | Env var | Default | | ----------------- | ----------------------- | ---------------------------------- | | --token= | INFRACODEBASE_TOKEN | required | | --api-url= | INFRACODEBASE_API_URL | https://infracodebase.com/api/v1 |
CLI
You rarely run this directly - your MCP client spawns it. When you do, use the npx form (or infracodebase / infracodebase-mcp if installed globally):
npx -y @infracodebase/mcp@latest # Start the server (stdio) - default
npx -y @infracodebase/mcp@latest help # Full usage
Development
npm install
npm run build
npm run test:run # unit tests (Vitest)
npm run smoke # offline test of the MCP protocol layer
See CONTRIBUTING.md for the full guide. MIT licensed.
Releases
Versions are published to npm automatically. Each release is tagged vX.Y.Z with notes generated from the changes in that release - browse the full changelog on the GitHub Releases page.
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: onwardplatforms
- Source: onwardplatforms/infracodebase-mcp
- License: MIT
- Homepage: https://infracodebase.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.