mcp-vue3-python
Servidor MCP em Python que gera estrutura completa de CRUD Vue 3 (Composition API).
Instalação
cd mcp-vue3-python
pip install -r requirements.txt
Configuração no Claude Desktop
Edite o arquivo claude_desktop_config.json:
Windows:
%APPDATA%\Claude\claude_desktop_config.json
macOS / Linux:
~/Library/Application Support/Claude/claude_desktop_config.json
Conteúdo a adicionar:
{
"mcpServers": {
"mcp-vue3-python": {
"command": "python",
"args": ["-m", "mcp_vue3.app"]
}
}
}
Windows com WSL/Docker: use
python3e ajuste o caminho conforme necessário.
Uso
No Claude, digite:
Utilize a tool gerar_crud do mcp mcp-vue3-python para gerar toda a estrutura de
arquivos e código para o seguinte módulo: CtreProfissionais
Ou com caminho base customizado:
Utilize a tool gerar_crud do mcp mcp-vue3-python para gerar toda a estrutura de
arquivos e código para o módulo CtreProfissionais com base_path /meu-projeto/src/views/ctreProfissionais
Arquivos gerados
Para o módulo CtreProfissionais com base_path padrão
/projeto-vue3/src/views/ctreProfissionais:
ctreProfissionais/
├── index.vue # Listagem com tabela e botões
├── services/
│ └── ctreProfissionaisService.js # axios: table, edit, post, patch, delete
├── components/
│ └── CtreProfissionaisForm.vue # Modal de criação/edição
├── store/
│ └── ctreProfissionaisStore.js # Pinia store
├── routes.js # Fragmento para router/index.js
└── README.md # Documentação do módulo
Regras
- Pastas existentes são reaproveitadas (nunca recriadas do zero).
- Arquivos existentes são preservados — o servidor reporta
⚠️ Já existe (mantido)e não sobrescreve. - Arquivos novos são criados e reportados com
✅ Criado.
Nomenclatura automática
| Entrada (PascalCase) | Derivado | Exemplo |
|---|---|---|
CtreProfissionais |
kebab-case | ctre-profissionais |
CtreProfissionais |
camelCase | ctreProfissionais |
CtreProfissionais |
snake_case | ctre_profissionais |
CtreProfissionais |
campo ID | id_ctre_profissionais |
CtreProfissionais |
rota base | /ctre-profissionais |
Metadata
Release files for mcp-vue3-python 0.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_vue3_python-0.0.8.tar.gz | 13.7 kB | Without provenance | Details for mcp_vue3_python-0.0.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_vue3_python-0.0.8-py3-none-any.whl | Python 3 | none | any | Details for mcp_vue3_python-0.0.8-py3-none-any.whl |
Total release size: 33.5 kB
Release files / mcp_vue3_python-0.0.8.tar.gz
| Download URL | mcp_vue3_python-0.0.8.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4ff319f02f38d27ba2e46a2a4d86be3cd71601accaa52d5f420660c068bfc9f
|
|
BLAKE2b-256 checksum How to use checksums |
b342a34dac7ae5e92827e15a5987bfd0df797fc6bb606cda4a84b012b41ecb8b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / mcp_vue3_python-0.0.8-py3-none-any.whl
| Download URL | mcp_vue3_python-0.0.8-py3-none-any.whl |
|---|---|
| Size | 19.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5c00d54311da22b866ec1aa3a0735a16e60075c2c419b40caf1a1bfe885757da
|
|
BLAKE2b-256 checksum How to use checksums |
126836e4587790fdb3030be2147a2003fdb6439787fd6e14433d7789d23a36ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for mcp-vue3-python 0.0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.