Add /export and /mcp-status commands

- /export command to export session data as Markdown or JSON
  - Export for sharing with other Claude instances
  - Include session details, topics, summary, and memory items
- /mcp-status command to check MCP integration health
  - Gmail venv and credentials status
  - Calendar API dependencies
  - Delegation helpers presence
  - MCP server configuration
- Updated shell completions with 15 aliases total
- Test suite now covers 23 tests

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
OpenCode Test
2026-01-01 18:47:50 -08:00
parent c1a3c1812c
commit 2ff7f6b133
9 changed files with 559 additions and 4 deletions

44
commands/mcp-status.md Normal file
View File

@@ -0,0 +1,44 @@
---
name: mcp-status
description: Check status of MCP integrations
aliases: [mcp, integrations]
invokes: skill:mcp-status
---
# MCP Status Command
Check the status of MCP integrations (Gmail, Calendar, etc.).
## Usage
```
/mcp-status # Show integration status
/mcp-status --json # Output as JSON
```
## Implementation
Run the MCP status script:
```bash
~/.claude/automation/mcp-status.sh [--json]
```
## Integrations Checked
| Integration | What's Checked |
|-------------|----------------|
| Gmail | Venv, gmail-mcp package, credentials, token |
| Calendar | google-api-python-client, credentials, token |
| Delegation | Helper scripts present |
| MCP Servers | .mcp.json configuration |
## Status Levels
| Status | Meaning |
|--------|---------|
| `ready` | Fully configured and working |
| `needs_auth` | Credentials present, needs OAuth |
| `needs_setup` | Missing configuration |
| `missing_deps` | Python packages not installed |
| `not_installed` | Integration not set up |