Local MCP BridgeStdio · approval-bound · scoped APIs

Put a narrow, inspectable bridge between a local agent and a paid API.

Version 0.3.2 gives an MCP client a local path to authenticated Maha MPS audit and book-access APIs—without turning the client into an unbounded payment or infrastructure operator.

Install command

A local process, not a hidden service dependency.

npm install -g @mahastrategies/maha-mcp-bridge

Configure the credential in your local MCP client according to the published manifest. Do not put a credential in a prompt, a public repository, or an agent instruction.

Control boundary

Useful access without delegated authority.

Local transport

The bridge runs as a local stdio process. It is not the hosted Enterprise MCP Gateway or a general-purpose remote proxy.

Scoped access

A credential can access only the documented MPS audit and book entitlement/content APIs allowed by its active scope.

No payment authority

The bridge does not receive a merchant secret, sign a payment, or autonomously complete checkout.

Separate service

The bridge is not the Cognitive Gateway.

The hosted Cognitive Gateway serves Maha OS, publishing, and research workflows. Its token and tools are separate from this local bridge. If you need a governed path to tenant-owned MCP servers, use the Enterprise MCP Gateway instead.