@skematica/secop-bridge
v2.0.0
Published
Universal MCP Bridge for Skemática SECOP MCP Server. Connects any local MCP client (Claude Desktop, VS Code, Cursor, etc.) to the remote server via Streamable HTTP (preferred) or SSE (fallback).
Maintainers
oddradiocircleReadme
Skemática SECOP Bridge
The Official Universal Connector for the SECOP II MCP Server.
This utility bridges the gap between local MCP clients (like Gemini CLI, Claude Desktop, VS Code, or Antigravity) and the remote SECOP Intelligent Procurement API.
It translates local stdio (standard input/output) communication into Server-Sent Events (SSE) secure traffic over HTTPS.
Installation
You don't need to install it! Just use npx.
Usage
1. Prerequisite
You need a SECOP API Key. If you are authorized, you should have received one (e.g., secop-v1-xxxxxxxx).
2. Configuration for Clients
Generic Configuration (JSON)
For any client that supports standard MCP configuration (Gemini, Claude, VS Code extensions):
{
"mcpServers": {
"secop": {
"command": "npx",
"args": [
"-y",
"@skematica/secop-bridge@latest"
],
"env": {
"MCP_API_KEY": "YOUR_API_KEY_HERE"
}
}
}
}That's it. No connect commands, no complex arguments.
3. Environment Variables
| Variable | Description | Default |
|----------|-------------|---------|
| MCP_API_KEY | Required. Your authentication token. | - |
| MCP_SSE_URL | Optional. Override the server URL. | https://secop.skemati.ca/sse |
| MCP_DEBUG | Optional. Set to true to log debug info to temp file. | false |
Troubleshooting
If connection fails:
- Check that your API Key is correct.
- Ensure you have internet access to
secop.skemati.ca. - Set
"env": { "MCP_DEBUG": "true", ... }and check the logs in your temp directory (e.g.,/tmp/secop_mcp_bridge.logor%TEMP%).
Copyright © 2026 Skemática.