Agent plugins for developing ALLPLAN PythonParts with AI coding assistants. They work with Claude Code, Claude Desktop, GitHub Copilot (VS Code, CLI, and app), and OpenAI Codex.
The marketplace allplan-pythonparts provides one plugin per ALLPLAN major version. Currently, it includes the plugin for ALLPLAN 2027.
The ALLPLAN 2027 plugin includes:
| Agent | Purpose |
|---|---|
pythonparts-planner |
Plans a PythonPart before any code is written. |
pythonparts-coder |
Implements PythonParts. |
pythonparts-researcher |
Answers framework questions for the planner and coder with a short, source-cited briefing. Does not edit files. |
| Server name | Purpose |
|---|---|
pythonparts-local-mcp |
Runs locally with your ALLPLAN installation. Type checks code, runs snippets, and inspects the PythonParts API. |
pythonparts-knowledge-mcp |
Hosted PythonParts knowledge base. Requires sign-in with ALLPLAN Connect. |
| Skill name | Purpose |
|---|---|
pythonparts-mcp-setup |
Sets the ALLPLAN Std and Usr paths for pythonparts-local-mcp. |
pythonparts-local-mcp runs with uvx. Install uv. On Windows, you can use winget:
winget install astral-sh.uvCheck that uvx is available in a new terminal:
uvx -VIn ALLPLAN, open Allmenu > Service > File Explorer:
| Path | Allmenu entry | Example |
|---|---|---|
| Std | Office standard (STD) | C:\Data\Allplan\Allplan 2027\Std |
| Usr | My own CAD documents (USR) | C:\Users\<you>\Documents\Nemetschek\Allplan\2027\Usr\Local |
Choose your AI coding assistant:
VS Code with GitHub Copilot
- Paste this link in your browser:
vscode://chat-plugin/install?source=NemetschekAllplan%2Fpythonparts-vibe-coding&plugin=pythonparts-2027- Confirm the installation of the plugin.
- In the chat, run
/pythonparts-mcp-setupand enter your Std and Usr paths.
Alternatively:
- In the VS Code command input (Ctrl+Shift+P or Cmd+Shift+P on macOS), type Chat: Manage Plugin Marketplaces
- Select Add Marketplace...
- Paste
NemetschekAllplan/pythonparts-vibe-coding - Select the newly added
allplan-pythonpartsmarketplace an then Browse. - Install the
pythonparts-2027plugin. - In the chat, run
/pythonparts-mcp-setupand enter your Std and Usr paths.
VS Code with Claude Code
Claude Code CLI
-
In your terminal, run:
claude plugin marketplace add NemetschekAllplan/pythonparts-vibe-coding claude plugin install pythonparts-2027@allplan-pythonparts
-
In Claude Code, run
/plugin configure pythonparts-2027@allplan-pythonpartsand enter your Std and Usr paths.
To skip step 2, pass the paths during installation:
claude plugin install pythonparts-2027@allplan-pythonparts --config "std_path=C:\Data\Allplan\Allplan 2027\Std" --config "usr_path=C:\Users\<you>\Documents\Nemetschek\Allplan\2027\Usr\Local"Claude Desktop
Follow the steps for Claude Code CLI above.
GitHub Copilot CLI
-
In your terminal, run:
copilot plugin marketplace add NemetschekAllplan/pythonparts-vibe-coding copilot plugin install pythonparts-2027@allplan-pythonparts
-
In a Copilot CLI session, run
/pythonparts-2027:pythonparts-mcp-setupand enter your Std and Usr paths. -
Start a new Copilot CLI session for the changes to take effect.
GitHub Copilot app
-
Click the button to add the marketplace:
Alternatively, go to Customize > Plugins, click the marketplace settings icon next to the marketplace dropdown, and add
NemetschekAllplan/pythonparts-vibe-coding. -
In Customize > Plugins, find
pythonparts-2027and click Install. -
In a session, run
/pythonparts-2027:pythonparts-mcp-setupand enter your Std and Usr paths. -
Start a new session.
OpenAI Codex
-
In your terminal, run:
codex plugin marketplace add NemetschekAllplan/pythonparts-vibe-coding codex plugin add pythonparts-2027@allplan-pythonparts
-
Start a new Codex session, run
$pythonparts-mcp-setup, and enter your Std and Usr paths. -
Start a new Codex session.
pythonparts-knowledge-mcp requires sign-in with your ALLPLAN Connect account. Your client prompts you when it first connects to the server. In Claude Code, run /mcp and authenticate the server.
Note
Updating or reinstalling the plugin resets paths configured with pythonparts-mcp-setup. Run the skill again afterwards. To change the paths later, repeat the configuration step for your client.