@iadev/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IADEV_URL | Yes | URL da API (padrão: https://iadev.dev) | https://iadev.dev |
| IADEV_API_KEY | No | API Key para auto-autenticação | |
| IADEV_PROJECT | Yes | Slug do projeto |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginB | Autenticar como admin do projeto. Retorna accessToken e refreshToken. |
| get_service_tokenB | Trocar API Key por um JWT técnico. Usa IADEV_API_KEY se apiKey não for informada. |
| get_project_infoB | Informações do projeto atual (nome, slug, plano, status). |
| list_tablesB | Listar todas as tabelas do schema do projeto. |
| get_columnsC | Listar colunas de uma tabela específica. |
| query_dataC | Buscar dados paginados de uma tabela. |
| execute_sqlB | Executar SQL no schema do projeto. Use com cuidado — suporta DDL e DML. |
| list_usersB | Listar usuários do projeto. |
| create_userC | Criar um novo usuário no projeto. |
| update_userC | Atualizar dados de um usuário do projeto. |
| create_projectA | Criar um novo projeto IAdev (banco + schema + API key). Admin ou super_admin. |
| list_my_projectsC | Listar meus projetos IAdev. |
| provision_projectB | Provisionar projeto completo com infraestrutura. Requer super_admin. |
| publish_projectB | Conectar repositório GitHub e iniciar deploy. Admin (dono) ou super_admin. |
| deploy_statusB | Consultar status do deployment. Admin (dono) ou super_admin. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools are clearly distinct (e.g., list_tables vs get_columns vs query_data). However, create_project, list_my_projects, provision_project, publish_project, and deploy_status could be confused without careful reading of descriptions, especially around project lifecycle stages.
Tool names consistently use snake_case and follow a verb_noun pattern (e.g., login, get_service_token, list_tables, create_user). Minor inconsistency: 'login' lacks a noun object, but overall predictable.
15 tools is within the reasonable range (3-15) for a server covering authentication, project management, data querying, and deployment. Slightly on the higher side but each tool appears to serve a distinct purpose.
While the surface covers authentication, project info, table/column listing, data query, SQL execution, user CRUD, and project creation/deployment, there are gaps: no delete operations for users or projects, no update for projects, and no explicit get_project (only list_my_projects). These missing operations may cause dead ends for agents needing full lifecycle management.