@sibermatedev/mcp
v0.1.1
Published
Local stdio bridge for the SiberMate remote MCP server.
Maintainers
Readme
@sibermatedev/mcp
Local stdio bridge for the SiberMate remote MCP server.
Use this package when an MCP client supports local or stdio MCP servers but does not yet support remote MCP OAuth.
Usage
npx -y @sibermatedev/mcpSet a dedicated SiberMate tenant API key in the client environment:
{
"mcpServers": {
"sibermate": {
"command": "npx",
"args": ["-y", "@sibermatedev/mcp"],
"env": {
"SIBERMATE_API_KEY": "..."
}
}
}
}Environment Variables
SIBERMATE_API_KEY: Required. Dedicated SiberMate tenant API key.SIBERMATE_MCP_URL: Optional. Defaults tohttps://mcp.sibermate.com/mcp.
Notes
- The remote MCP server remains the canonical implementation.
- This package forwards stdio JSON-RPC messages to
https://mcp.sibermate.com/mcp. - Keep API keys out of repositories, logs, screenshots, and shared prompts.
