# platform-dev-protocols

> Protocols for agents that modify the MCP platform itself (vs agents that use the tools). Use when editing tool source code, deploying services, or changing platform architecture.

- Author: Tony Glass
- Repository: tonton2006/ai-cloud-orchestrator
- Version: 20251218103636
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-07
- Source: https://github.com/tonton2006/ai-cloud-orchestrator
- Web: https://mule.run/skillshub/@@tonton2006/ai-cloud-orchestrator~platform-dev-protocols:20251218103636

---

---
name: platform-dev-protocols
description: Protocols for agents that modify the MCP platform itself (vs agents that use the tools). Use when editing tool source code, deploying services, or changing platform architecture.
---

# Platform Development Protocols

## Purpose

Guide agents that build and modify the MCP platform (tools, services, infrastructure) as opposed to agents that merely use those tools.

## Platform Agent Responsibilities

**Can do:**
- Edit `mcp_server/tools/*.py`
- Modify service code in `shards/*/`
- Deploy Cloud Run services
- Update agent configurations
- Modify skill definitions
- Change platform architecture

**Cannot do:**
- Use the tools they're building (circular dependency)
- Make changes without testing
- Deploy without verification

## Development Pattern

1. **Understand requirement** - What needs to be built/changed?
2. **Design solution** - How will it work?
3. **Implement** - Write the code
4. **Test locally** - Verify it works
5. **Deploy** - Push to Cloud Run
6. **Verify** - Confirm deployment successful
7. **Document** - Update docs and store in Neo4j

## Testing Before Deployment

```bash
# Test MCP tool locally
python -m mcp_server.main

# Verify tool is registered
# Verify it executes correctly
# Check for errors
```

## Deployment Pattern

```bash
# Deploy to Cloud Run
gcloud run deploy [service-name] \
  --source . \
  --region us-central1 \
  --project ai-cloud-manager

# Verify deployment
curl -H "Authorization: Bearer $TOKEN" \
  https://[service-name]-carvf5rgka-uc.a.run.app/

# Refresh MCP tokens
bash ~/projects/refresh-mcp-tokens.sh
```

## Documentation Requirements

After any platform change:

```python
store_fact(
    fact="Added new MCP tool: [tool_name]. Purpose: [what it does]. Deployed to [service]. Location: [file_path].",
    category="platform_change",
    confidence=1.0,
    tags=["mcp", "tool", service_name]
)
```

## File Size Limits

**Critical:** No file >2000 lines (Read tool limit)
- Python modules: Max 2000 lines
- Split larger files into modules
- Document module structure

---

Platform agents build the tools. Tool-using agents use them. Never confuse the two.