Rial-Soft plugin marketplace

This repository distributes the portal-onec plugin to Codex, Claude Code, and the Chat tab in Claude Desktop. One installation adds the shared production MCP endpoint and the Portal 1C skill. Every user completes a separate OAuth/PKCE sign-in with their own 1C account.

The repository contains no 1C passwords, JWTs, cookies, OAuth credentials, client secrets, or production signing keys.

Подробная русскоязычная инструкция для Codex, Claude Desktop и Claude Code: INSTALL_RU.md.

Install in Codex and Claude Code

Clone this repository from the internal Forgejo server, then run:

git clone http://192.168.230.222:3000/aleks/portal-onec-marketplace.git
Set-Location portal-onec-marketplace
Set-ExecutionPolicy -Scope Process Bypass
.\Install-PortalOnecPlugin.ps1 -Target All

If Codex Desktop is installed but the separate codex command is missing, opt in to installing the official npm CLI and continue in one step:

.\Install-PortalOnecPlugin.ps1 -Target Codex -InstallCodexCliIfMissing

The installer does not use the protected internal executable from the Microsoft Store app. The optional switch runs npm install -g @openai/codex and then uses the generated user-level CLI wrapper.

On Windows, the installer automatically detects the standard Git Bash location for Claude Code. It sets CLAUDE_CODE_GIT_BASH_PATH only for the installer process and does not change the user's or machine's environment.

Use -Target Codex or -Target Claude to install only one host. Use -StartCodexAuthentication to ask Codex CLI to open its OAuth browser flow immediately after installation. Without that switch, Codex should offer the connection during install because the marketplace policy is ON_INSTALL; the Settings fallback remains available.

Claude Code completes remote MCP OAuth from /mcp. Its plugin installer cannot safely enter a 1C password or finish the user consent step.

Install in Claude Desktop Chat (no CLI)

1. Download releases/portal-onec-claude-desktop.zip. Do not unpack it.
2. In Claude Desktop open Customize → Plugins.
3. Choose the action to upload a custom plugin and select the downloaded ZIP.
4. Open Customize → Connectors, find Portal 1C / onec_portal, and click Connect.
5. Enter the 1C username, password, and 2FA only on the HTTPS Portal page opened by Claude.
6. In a conversation enable Portal 1C through + → Connectors and ask Claude to show the current 1C user.

Do not add this remote server to claude_desktop_config.json. Claude Desktop Chat brokers remote connectors through the Claude account; the config file is a different local-MCP mechanism.

For Team or Enterprise, an Owner can upload this same ZIP to the organization plugin marketplace once. Members then install it from Browse plugins and each member connects their own 1C account. The ZIP contains no shared credential.

Update

git pull --ff-only
.\Install-PortalOnecPlugin.ps1 -Target All

Start a new Codex task or Claude Code session after updating plugin files. Do not clear existing MCP OAuth credentials: short-lived access tokens refresh through the server's rotating refresh grant.

Publisher workflow

The canonical plugin source is D:\Projects\Portal\plugins\portal-onec. Rebuild this marketplace from the Portal workspace with:

powershell.exe -ExecutionPolicy Bypass -File D:\Projects\Portal\scripts\Build-PortalOnecMarketplace.ps1

Validate both hosts before publishing. Bump the shared plugin version whenever the installed package changes.