Integrate Amazon Q CLI MCP server management into dotfiles setup

## Overview

Amazon Q CLI has robust MCP (Model Context Protocol) server management capabilities that we could leverage in our dotfiles to automate development environment setup.

## Background

Amazon Q CLI now supports comprehensive MCP server management via `q mcp` commands. This includes:
- Server lifecycle management (`add/remove/list/status`)
- Global and workspace-scoped configurations
- Tool trust management
- Multiple configuration file support
- Environment variable and timeout configuration

**Reference**: https://github.com/aws/amazon-q-developer-cli-autocomplete/pull/262

## Opportunity

Following our **Spilled Coffee Principle**, we could automate MCP server setup so that anyone can destroy their machine and have a fully configured Q CLI environment that afternoon.

## Potential Integrations

### 1. Setup Script Enhancement
Add MCP server installation to `setup.sh`:
- Automatically configure our battle-tested `atxtechbro-git-mcp-server`
- Set up common servers like filesystem operations
- Configure appropriate tool trust settings

### 2. Project-Specific MCP Configs
Leverage `--mcp-config-paths` for project-aware server loading:
- Different MCP servers for different project types
- Automatic server configuration based on detected project structure

### 3. Environment-Aware Configuration
- Development vs production MCP server configurations
- Conditional server loading based on environment variables

## Implementation Considerations

- Build on our existing MCP protocol testing knowledge
- Apply **subtraction-creates-value** principle - only add servers that provide clear value
- Use **tracer-bullets** approach - start with minimal configuration and expand
- Ensure configurations are reproducible across different machines

## Next Steps

1. Research current Amazon Q CLI MCP capabilities in detail
2. Identify which MCP servers provide the most value for our workflow
3. Design integration points with existing dotfiles structure
4. Implement and test automated MCP server setup
5. Document usage patterns and best practices

## Related Work

- Our MCP server development experience with git-mcp-server
- Existing dotfiles automation in `setup.sh`
- Modular shell configuration patterns

This enhancement would make our development environment setup even more comprehensive and reduce manual configuration overhead.

Start by reading setup.sh and the existing modular shell configuration, then research the Amazon Q CLI q mcp capabilities and the referenced MCP server work. Define a minimal, reproducible integration before expanding it; done should include automated setup, environment-appropriate configuration, testing across supported machines, and usage documentation.

Written by the indexing model from the issue text.