Install 1c in Goose
What you need first
- Goose, installed.
- Node.js, which
gives the
npxcommand the server starts with. - Your own values for
YOUR_MCP_1C_BASE,YOUR_MCP_1C_USER,YOUR_MCP_1C_PASSWORD,YOUR_RCS_LICENSE_KEY.
Steps
- Open
~/.config/goose/config.yaml. On Windows it is%APPDATA%\Block\goose\config\config.yaml. - Add this entry. If the file already has
extensions, add only the entry inside it.
extensions:
"mcp-1c":
type: stdio
name: "mcp-1c"
enabled: true
cmd: "npx"
args: ["-y", "@rcs-kz/[email protected]"]
env_keys: []
envs: { "MCP_1C_BASE": "YOUR_MCP_1C_BASE", "MCP_1C_USER": "YOUR_MCP_1C_USER", "MCP_1C_PASSWORD": "YOUR_MCP_1C_PASSWORD", "RCS_LICENSE_KEY": "YOUR_RCS_LICENSE_KEY" }
timeout: 300 - Replace
YOUR_MCP_1C_BASE,YOUR_MCP_1C_USER,YOUR_MCP_1C_PASSWORD,YOUR_RCS_LICENSE_KEYwith your own values. - Save the file and start a new Goose session.
Check it worked
Ask Goose: List the tools of mcp-1c.
If it does not start
- spawn npx ENOENT
- Node.js is not on the PATH that Goose sees. Install it, or write the
full path of
npxin the config. - The server starts, but its tools fail
- A
YOUR_…placeholder is still in the config, or its value is wrong. - Nothing changes after a restart
- The file is not valid YAML any more. Check that the entry is indented like the lines around it.