Aspire MCP ecosystem — connected tools + per-environment matrix
Context
Aspire uses Model Context Protocol (MCP) extensively to give AI agents programmatic access to external services. Knowing which MCP is wired up where is the single most-asked question by new agents — and getting it wrong means wasted token cycles trying tools that don't work.
This concept page is the single source of truth for the inventory. Source files: MEMORY.md (reference_mcp_inventory) + claude_desktop_config.json + ~/.claude.json mcpServers.
Detail
Where MCPs live (3 environments)
| Environment | Config file | Use case |
|---|---|---|
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json | Kom's day-to-day chat |
| Claude Code (this CLI) | ~/.claude.json mcpServers | This session right now |
| OpenClaw VPS agents | Per-agent config under ~/.openclaw/ on VPS | Background 28-agent fleet |
A given MCP can be present in 0, 1, 2, or all 3 — and that placement matters.
Inventory by category (as of 2026-05-21)
Finance / accounting
| MCP | Code | Desktop | Cloud | Notes |
|---|---|---|---|---|
| Xero (5 orgs: adg, ahg, sixdegree, chanyathai, venice) | ✅ | ✅ | — | Xero MCP wrappers broken for some calls — fall back to curl with X-API-Key on xero.aspiredigitalgroup.com.au |
| PowerEPOS | ✅ | ✅ | — | Six Degrees / Chanya Thai / Venice POS data |
| Stripe (Zinga eSIM account) | ✅ | — | — | Connected to wrong account for alby-studio audit; needs separate alby-studio Stripe account wiring |
Hospitality ops
| MCP | Notes |
|---|---|
| Tanda | Rosters, timesheets, leave, payroll |
| STAAH | Accommodation channel manager (NOTE: STAAH MCP repointed to Zinga Channel Manager at cm.getzinga.com.au) |
| PowerEPOS | POS / sales / stock for 3 venues |
Knowledge OS specific
| MCP | Status |
|---|---|
ko-knowledge (this project!) | ✅ wired in Claude Code; 6 tools (health, knowledge_query, get_page, ingest, update_page, lint_page) |
| Recall MCP (per-agent FTS5 over briefs/memory/dreams/skills) | OpenClaw only |
| Skill-registry MCP (per-agent skill files) | OpenClaw only |
Comms
- Gmail (Desktop)
- SendGrid (Code)
- Twilio (SMS/calls)
- Slack (via Salesforce plugin, Code+Desktop)
- Roundcube email
- 32+ Aspire-specific MCP servers at
~/mcp-servers/
Analytics
- GA4 per-brand (7 brands: ADG, Alby, Chanya, Gold Room, Six Degrees, Venice, Zinga)
- Ahrefs (SEO + web analytics)
- Microsoft Clarity (8 brand tokens)
- Search Console + Bing equivalents
Browser automation (4 distinct, all in Code)
| MCP | When to use |
|---|---|
| Claude in Chrome | Paired Browser 1, one Claude session at a time, flip-flop |
| chrome-devtools | --isolated, parallel-safe, no cookies; for ad-hoc clean browser |
| playwright (master) | Persistent profile at ~/.cache/playwright-mcp-profile/, one session at a time; for logins/state-changing work |
| playwright-parallel | --isolated --storage-state ~/.cache/playwright-mcp-storage-state.json --output-mode stdout, true parallel across sessions; for scrape/audit |
Default routing:
- Logins → playwright master
- Scrape on logged-in services → playwright-parallel
- Ad-hoc clean browser → chrome-devtools
AI / LLM
- Aspire LLM Gateway at
llm.aspiredigital.group/v1— single egress for all LLM/vision/OCR. See aspire-llm-gateway-only-egress - Perplexity (research)
- Suno (music generation)
- HeyGen (avatar video)
- Gamma (decks)
- Nano-banana, Freepik (image)
- Veo (video)
- ElevenLabs (TTS, planned)
Design
- Canva (multiple plugins: Connect, Marketing)
- Figma (read-only) + Talk-to-Figma (write-capable, local Bun MCP)
- Stitch (Aspire's own design tool)
Other notable
- Coolify (deploy orchestration)
- GitLab (self-hosted at
gitlab.dssc.co.th) - Odoo 18.0 Enterprise (ERP — projects, tasks, CRM, inventory, HR, manufacturing)
- Nextcloud (cookbook, deck, calendar, notes, etc.)
- ClickUp (legacy — migrated to Odoo, MCP removed 2026-05-06)
How to choose the right MCP
The decision tree (per aios-workflow):
- Need to read/write a specific app's data? → use that app's MCP if listed above
- Need to call an LLM? → Always through Aspire LLM Gateway, never direct
- Need to send a notification? → Telegram per telegram-bot-pattern for internal, SendGrid for customers
- Need to deploy code? → Coolify MCP if customer-facing app, GitLab MCP for CI
What's NOT yet wired but planned
- HeyGen (already in inventory but underused)
- OBS (planned for streaming/recording automation)
- Vapi (voice AI)
- Postiz (LIVE on infra; integration with content-studio still WIP per MEMORY.md
project_postiz_integration) - PostHog (analytics — Clarity covers most of this)
- Linear (some Aspire teams prefer over Odoo for engineering tickets)
Related
- aios-workflow — the agent vs skill vs slash command decision tree
- aspire-llm-gateway-only-egress — gateway-only directive for LLM traffic
- knowledge-os-stage-1 —
ko-knowledgeMCP is part of this project
🔗 Relationships
graph LR
aspire_mcp_ecosystem["aspire-mcp-ecosystem"]:::self
aspire_mcp_ecosystem --> aspire_llm_gateway_only_egress["aspire-llm-gateway-only-egress"]
aspire_mcp_ecosystem --> aios_workflow["aios-workflow"]
aspire_mcp_ecosystem --> telegram_bot_pattern["telegram-bot-pattern"]
aspire_mcp_ecosystem --> knowledge_os_stage_1["knowledge-os-stage-1"]
classDef self fill:#715EE3,color:#fff,stroke:#291F50;