GAIIA Expert Proxy (MCP Server)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gaiia_list_expertsC | List available AI experts and their specialties. |
| sync_specsA | Synchronizes all locally discovered API specifications in the 'specs/' directory to the GAIIA Registry. |
| gaiia_set_active_expertC | Select an expert to use for code transformations. |
| gaiia_transformC | Audit, refactor, or generate code using the active GAIIA expert. |
| gaiia_analyze_projectC | Perform a deep architectural audit of an entire local project directory. |
| interrogate_endpointB | Intelligently interrogates a REST endpoint to discover its schema via reinforcement learning loop. |
| gaiia_list_processesA | List all registered BPMN process blueprints/templates in the GAIIA registry for the authenticated tenant. |
| gaiia_start_processB | Starts/triggers an instance of a registered BPMN process blueprint with an optional custom payload. |
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 8 tools
Each tool has a clearly distinct purpose: project analysis, expert listing/selection, process listing/starting, code transformation, API interrogation, and spec syncing. No significant overlap.
Six of eight tools use the consistent 'gaiia_' prefix with verb_noun pattern, but two tools ('interrogate_endpoint', 'sync_specs') lack the prefix, creating a mixed naming convention.
With 8 tools, the set is well-scoped for a proxy server providing GAIIA platform operations, covering multiple areas without being overwhelming.
The tool surface covers core workflows (expert management, project analysis, process execution, code transformation, API spec handling), but lacks a get_active_expert tool and some CRUD operations, leaving minor gaps.