mcp-vue3-python
Generates Vue 3 CRUD code that uses Axios for API calls (table, edit, post, patch, delete).
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-vue3-pythonGenerate Vue 3 CRUD structure for CtreProfissionais module"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.txtRelated MCP server: Splytin MCP Project Generator
Configuração no Claude Desktop
Edite o arquivo claude_desktop_config.json:
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonmacOS / Linux:
~/Library/Application Support/Claude/claude_desktop_config.jsonConteú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: CtreProfissionaisOu 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/ctreProfissionaisArquivos 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óduloRegras
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 |
| kebab-case |
|
| camelCase |
|
| snake_case |
|
| campo ID |
|
| rota base |
|
Available Tools
1 toolgerar_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')
| Name | Required | Description | Default |
|---|---|---|---|
| module_name | Yes | ||
| src_path | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
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.
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.
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.
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.
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.
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 tool update
v0.0.8- First observed
gerar_estrutura_vue
TDQS
With only one tool, there is no possibility of confusion between tools. The agent will always select the correct tool.
Since there is only one tool, naming consistency is inherently perfect. The single name follows a clear pattern (verb_noun in Portuguese).
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.
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
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
MCP Server for Slima - AI Writing IDE for Novel Authors with AI Beta Reader.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
MCP server for Google Veo AI video generation
Primarily to be used as a template repository for developing MCP servers with FastMCP in Python, P…
Related MCP Servers
- AlicenseCqualityDmaintenanceA 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.322MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that enables the automated creation and scaffolding of Python Django, React, and PHP projects. It provides tools for initializing new project structures and generating Django CRUD components.1-
- AlicenseAqualityDmaintenanceAn MCP server that scaffolds full-stack projects with consistent structure, Docker setup, CI/CD pipelines, and database configuration.6MIT
- AlicenseAqualityDmaintenanceA unified MCP server for scaffolding project structures across multiple frameworks including Spring Boot, React, Vue, Next.js, FastAPI, Django, Flask, Express, and more.2241MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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