ConnectSecure MCP
Vulnerability management across all ConnectSecure clients: exposure ranking, CVE impact, blind spots
{ "mcpServers": { "io.github.servosity-connectsecure-mcp": { "command": "mcpb", "args": [ "https://github.com/Servosity/msp-skills/releases/download/connectsecure-v0.1.10/connectsecure-mcp.mcpb" ], "env": { "CONNECTSECURE_BASE_URL": "<value>", "CONNECTSECURE_TENANT": "<value>", "CONNECTSECURE_CLIENT_ID": "<secret>", "CONNECTSECURE_CLIENT_SECRET": "<secret>", "CONNECTSECURE_ACCESS_TOKEN": "<secret>", "CONNECTSECURE_USER_ID": "<value>", "CONNECTSECURE_MCP_READ_ONLY": "<value>", "CONNECTSECURE_USER_AGENT": "<value>", "CONNECTSECURE_MCP_HTTP_TOKEN": "<secret>", "PRINTING_PRESS_CLIENT_PROFILE": "<secret>", "CONNECTSECURE_NO_LOCAL_DATA": "<value>", "CONNECTSECURE_MCP_UPLOAD_ROOT": "<value>" } } }}.cursor/mcp.jsonMCP-сервер
- Транспорт
- stdio
- Статус
- Локальный
Усильте агента
Добавить этот сервер
Собственная команда издателя. Не эндпоинт PlugMCP.
Host a copy with our keys and logs.
Локальная команда
mcpb https://github.com/Servosity/msp-skills/releases/download/connectsecure-v0.1.10/connectsecure-mcp.mcpbУчётные данные от издателя
- CONNECTSECURE_BASE_URL — Your tenant's pod URL, e.g. https://pod104.myconnectsecure.com (Profile > API Documentation in the portal). Each tenant has its own pod; there is no working default.
- CONNECTSECURE_TENANT — Tenant name you type on the ConnectSecure portal login screen.
- CONNECTSECURE_CLIENT_ID — API client ID from Settings > Users > (user) > API Key.
- CONNECTSECURE_CLIENT_SECRET — API client secret from Settings > Users > (user) > API Key.
- CONNECTSECURE_ACCESS_TOKEN — Optional. A pre-minted JWT from /w/authorize; while it is unexpired it is used instead of minting one. The tenant, client ID and secret are still needed so the CLI can mint a fresh token once it expires.
- CONNECTSECURE_USER_ID — Optional user_id from /w/authorize. Only needed with a pre-minted access token; minting fills it automatically.
- CONNECTSECURE_MCP_READ_ONLY — Set to 1 to make the MCP server refuse every write and hide the sync, export and tail tools (import is never an MCP tool). Credential reads are still answered.
- CONNECTSECURE_USER_AGENT — Overrides the User-Agent the CLI sends on ConnectSecure requests.
- CONNECTSECURE_MCP_HTTP_TOKEN — Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
- PRINTING_PRESS_CLIENT_PROFILE — Optional: binds the MCP server to a tenant-gated Printing Press client profile. This connector registers none; leave unset.
- CONNECTSECURE_NO_LOCAL_DATA — Optional. Set to 1 to keep no local copy of API responses: reads go to the API, the response cache is off, and sync refuses to run. Leave blank to keep the local store.
- CONNECTSECURE_MCP_UPLOAD_ROOT — Optional. Leave blank: MCP file uploads then take the file as base64 content and the server never opens a local path. Set it to a folder only to let MCP uploads read files from inside that folder.
У Claude Code нет ссылки для установки локальной команды. Скопируйте команду ниже и выполните её в терминале.
shClaude Code
CONNECTSECURE_BASE_URL=<value> CONNECTSECURE_TENANT=<value> CONNECTSECURE_CLIENT_ID=<secret> CONNECTSECURE_CLIENT_SECRET=<secret> CONNECTSECURE_ACCESS_TOKEN=<secret> CONNECTSECURE_USER_ID=<value> CONNECTSECURE_MCP_READ_ONLY=<value> CONNECTSECURE_USER_AGENT=<value> CONNECTSECURE_MCP_HTTP_TOKEN=<secret> PRINTING_PRESS_CLIENT_PROFILE=<secret> CONNECTSECURE_NO_LOCAL_DATA=<value> CONNECTSECURE_MCP_UPLOAD_ROOT=<value> claude mcp add io.github.servosity-connectsecure-mcp -- mcpb https://github.com/Servosity/msp-skills/releases/download/connectsecure-v0.1.10/connectsecure-mcp.mcpbВыполните в терминале.
jsonClaude Desktop
{ "mcpServers": { "io.github.servosity-connectsecure-mcp": { "command": "mcpb", "args": [ "https://github.com/Servosity/msp-skills/releases/download/connectsecure-v0.1.10/connectsecure-mcp.mcpb" ], "env": { "CONNECTSECURE_BASE_URL": "<value>", "CONNECTSECURE_TENANT": "<value>", "CONNECTSECURE_CLIENT_ID": "<secret>", "CONNECTSECURE_CLIENT_SECRET": "<secret>", "CONNECTSECURE_ACCESS_TOKEN": "<secret>", "CONNECTSECURE_USER_ID": "<value>", "CONNECTSECURE_MCP_READ_ONLY": "<value>", "CONNECTSECURE_USER_AGENT": "<value>", "CONNECTSECURE_MCP_HTTP_TOKEN": "<secret>", "PRINTING_PRESS_CLIENT_PROFILE": "<secret>", "CONNECTSECURE_NO_LOCAL_DATA": "<value>", "CONNECTSECURE_MCP_UPLOAD_ROOT": "<value>" } } }}claude_desktop_config.json
Локальный · mcpbУстановка от издателяПошагово: как добавить в Claude
Удалённый URL или команда на вашем компьютере? Чем различаются два способа установки
Запустить на PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
ЗапускСведения о сервере
Локальный- Транспорт
- stdio
- Версия
- 0.1.10
- Лицензия
- NOASSERTION
- API-ключ
- CONNECTSECURE_BASE_URL, CONNECTSECURE_TENANT, CONNECTSECURE_CLIENT_ID, CONNECTSECURE_CLIENT_SECRET, CONNECTSECURE_ACCESS_TOKEN, CONNECTSECURE_USER_ID, CONNECTSECURE_MCP_READ_ONLY, CONNECTSECURE_USER_AGENT, CONNECTSECURE_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE, CONNECTSECURE_NO_LOCAL_DATA, CONNECTSECURE_MCP_UPLOAD_ROOT
- Последняя проверка
- 2026-11-15
- Звёзды
- 82
- Инструменты
- —
- Аптайм
- —
Инструменты
Инструменты
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Вопросы
Как установить ConnectSecure MCP?
Скопируйте на этой странице конфигурацию stdio для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
Нужен ли API-ключ для ConnectSecure MCP?
Издатель указывает следующие переменные окружения: CONNECTSECURE_BASE_URL, CONNECTSECURE_TENANT, CONNECTSECURE_CLIENT_ID, CONNECTSECURE_CLIENT_SECRET, CONNECTSECURE_ACCESS_TOKEN, CONNECTSECURE_USER_ID, CONNECTSECURE_MCP_READ_ONLY, CONNECTSECURE_USER_AGENT, CONNECTSECURE_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE, CONNECTSECURE_NO_LOCAL_DATA, CONNECTSECURE_MCP_UPLOAD_ROOT.
Какой транспорт использует ConnectSecure MCP?
ConnectSecure MCP работает локально через stdio.
Когда ConnectSecure MCP проверялся в последний раз?
Последняя проверка: 2026-11-15. Vulnerability management across all ConnectSecure clients: exposure ranking, CVE impact, blind spots
От издателя
Документация
README ещё не проиндексирован. Открыть репозиторий
Vulnerability management across all ConnectSecure clients: exposure ranking, CVE impact, blind spots