Skip to main content
Glama
gsccoelho

mcp-vue3-python

by gsccoelho

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

Related MCP server: Splytin MCP Project Generator

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 python3 e 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

  1. Pastas existentes são reaproveitadas (nunca recriadas do zero).

  2. Arquivos existentes são preservados — o servidor reporta ⚠️ Já existe (mantido) e não sobrescreve.

  3. 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

Available Tools

1 tool
gerar_estrutura_vueA

Utilize esta tool para gerar a estrutura completa de um CRUD Vue 3. Ela cria automaticamente os arquivos base de Molecules, Organisms e Views.

Args: module_name: Nome base do módulo em PascalCase ou camelCase (ex: 'MovCadastral') src_path: O caminho absoluto da pasta 'src' do workspace/projeto Vue atual. (ex: 'C:/projetos/meu-app/src')

ParametersJSON Schema
NameRequiredDescriptionDefault
module_nameYes
src_pathYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description reveals that the tool creates files ('cria automaticamente os arquivos base'), indicating a write operation. However, it does not disclose potential side effects such as overwriting existing files or required permissions, which are important for a generative tool with no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the main purpose in the first sentence. The argument list is structured separately, which is clear and efficient. No unnecessary information is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has two simple parameters and no output schema, the description adequately covers the purpose but lacks details on the generated output structure or return value. It could mention if the tool returns a success message or lists created files.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaningful context to both parameters, including expected formats (PascalCase/camelCase for module_name, absolute path for src_path) and an example. Since the schema itself has no descriptions (0% coverage), this compensates well by guiding proper usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool generates a complete Vue 3 CRUD structure, specifying the verb 'gerar' and the resource 'estrutura completa de um CRUD Vue 3'. It also lists the created file types (Molecules, Organisms, Views), leaving no ambiguity about the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool ('Utilize esta tool para gerar...'), covering the primary use case. However, it does not mention when not to use it or any prerequisites, though the lack of alternative tools makes this less critical.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.0.8
    • First observedgerar_estrutura_vue

TDQS

A4.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The agent will always select the correct tool.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The single name follows a clear pattern (verb_noun in Portuguese).

Tool Count4/5

The server is focused on generating Vue 3 structures, and one tool may suffice for that narrow purpose. However, it falls below the typical 3-15 tool range, making it slightly thin.

Completeness3/5

The tool generates only the base file structure for Molecules, Organisms, and Views. It lacks generation of services, stores, or Python backend components implied by the server name, leaving notable gaps for a full CRUD workflow.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    C
    quality
    D
    maintenance
    A Model Context Protocol server that automates code generation for web development, specializing in creating TypeScript API clients from Swagger/OpenAPI specs and Vue.js components for frontend development.
    3
    22
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    A unified MCP server for scaffolding project structures across multiple frameworks including Spring Boot, React, Vue, Next.js, FastAPI, Django, Flask, Express, and more.
    2
    24
    1
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gsccoelho/mcp-vue3-python'

If you have feedback or need assistance with the MCP directory API, please join our Discord server