AI governance MCP server for policy enforcement, cost control, and observability.
Connect Runs on your machine
claude mcp add fulcrum -e FULCRUM_API_ENDPOINT=<FULCRUM_API_ENDPOINT> -e FULCRUM_TENANT_ID=<FULCRUM_TENANT_ID> -e FULCRUM_API_KEY=<FULCRUM_API_KEY> -- npx -y @fulcrum-governance/[email protected]
{
"mcpServers": {
"fulcrum": {
"command": "npx",
"args": [
"-y",
"@fulcrum-governance/[email protected]"
],
"env": {
"FULCRUM_API_ENDPOINT": "<FULCRUM_API_ENDPOINT>",
"FULCRUM_TENANT_ID": "<FULCRUM_TENANT_ID>",
"FULCRUM_API_KEY": "<FULCRUM_API_KEY>"
}
}
}
}
{
"mcpServers": {
"fulcrum": {
"command": "npx",
"args": [
"-y",
"@fulcrum-governance/[email protected]"
],
"env": {
"FULCRUM_API_ENDPOINT": "<FULCRUM_API_ENDPOINT>",
"FULCRUM_TENANT_ID": "<FULCRUM_TENANT_ID>",
"FULCRUM_API_KEY": "<FULCRUM_API_KEY>"
}
}
}
}
{
"servers": {
"fulcrum": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@fulcrum-governance/[email protected]"
],
"env": {
"FULCRUM_API_ENDPOINT": "<FULCRUM_API_ENDPOINT>",
"FULCRUM_TENANT_ID": "<FULCRUM_TENANT_ID>",
"FULCRUM_API_KEY": "<FULCRUM_API_KEY>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
FULCRUM_API_ENDPOINTOptional | The Fulcrum gRPC API endpoint (e.g., localhost:50051) |
FULCRUM_TENANT_IDOptional | Your Fulcrum tenant identifier |
FULCRUM_API_KEYOptional | API key for authentication (optional for local development) |
Details
| Package | @fulcrum-governance/[email protected] (NPM, stdio) |
| Package | [email protected] (PYPI, stdio) |
| First published | 7 Jan 2026 |
| Last updated | 7 Jan 2026 |
| Registry name | io.github.Dewars30/fulcrum |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
