gia

The GIA MCP Server acts as a lightweight proxy that connects Claude Desktop and Claude Code to the hosted Governance Intelligence Architecture (GIA) governance engine. All governance logic runs on the remote GIA server, including decision classification, audit trails, human-in-the-loop gates, and compliance mapping. This server merely routes requests from Claude clients to the GIA backend and returns results, enabling enterprise-grade governance without distributing sensitive logic locally. Available capabilities include tools for decision classification, governance scoring, audit and monitoring, memory pack management, site reliability checks, infrastructure operations, and value/impact reporting. You can invoke these tools through the MCP interface provided by Claude Desktop or Claude Code, and the server ensures governance decisions are consistent with the hosted GIA policies and taxonomies.

Prerequisites:

• Node.js 18 or later
• npm (comes with Node.js)
• A GIA API key (from gia.aceadvising.com)

1. Install the MCP server package globally (or use npx as described in the config):

   npm install -g gia-mcp-server

2. Obtain your GIA API key from gia.aceadvising.com and keep it handy for configuration.

3. Run the MCP server locally (example using npx as configured):

   npx -y gia-mcp-server

4. If you’re configuring Claude Desktop or Claude Code to use the MCP server, ensure your environment variables are set to include GIA_API_KEY, and point Claude to the server via the provided mcp configuration snippet in your environment or config file.

5. Optional: set GIA_SERVER_URL if you’re targeting a non-default GIA server URL. The default is https://gia.aceadvising.com/mcp.

Environment variables:

• GIA_API_KEY: Your GIA API key required for authentication with the hosted GIA governance engine.
• GIA_SERVER_URL: Optional. Custom MCP server URL. Default is https://gia.aceadvising.com/mcp. Configuration tips:
• When using Claude Desktop, add the gia MCP server entry under mcpServers with command/npx, arguments, and the GIA_API_KEY env var as demonstrated in the Quick Start section.
• If you rotate API keys, update the GIA_API_KEY value in your Claude config to continue access. Common issues:
• If you see authentication failures, verify the API key is correct and has access to the GIA project.
• Ensure Node.js 18+ is installed and the environment can reach the GIA server URL (network egress and firewall rules).
• The MCP server itself is stateless beyond the API key; server-side governance logic remains on the GIA host.