UniqueSoft/APAW
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

[Phase 3] Update capability-index.yaml + orchestrator permissions for all 18 MCP integrations #56

New Issue
Closed
opened 2026-04-06 23:04:13 +00:00 by NW · 0 comments
NW commented 2026-04-06 23:04:13 +00:00
Owner
Copy Link

User Story

As an orchestrator, I need all 18 MCP integrations registered in capability-index.yaml with proper routing so that I can dispatch tasks to MCP-enabled agents.

Acceptance Criteria

  • Update capability-index.yaml with new MCP capabilities
  • Update orchestrator.md permissions for all new agents
  • Update kilo.jsonc with new agent configurations
  • Update AGENTS.md with new capabilities
  • Update KILO_SPEC.md documentation
  • Run full pipeline test to verify routing
  • Verify all 18 MCP servers accessible

New Capabilities to Add

Phase 1 Capabilities

  • mcp_repository_context (GitMCP)
  • mcp_e2e_testing (Playwright MCP)
  • mcp_agent_patterns (Multi Agent Architect MCP)
  • mcp_api_conversion (OpenAPI to MCP Converter)
  • mcp_prompt_versioning (Ai Prompt Library)
  • mcp_tech_monitoring (DevTrends MCP)
  • mcp_vulnerability_scan (CVE Search MCP)
  • mcp_server_validation (MCP Validator)

Phase 2 Capabilities

  • mcp_documentation_access (Docfork + API Doc MCP)
  • mcp_web_search (Brave Search + Tavily MCP)
  • mcp_knowledge_base (Wikipedia + ArXiv MCP)
  • mcp_document_conversion (Markitdown MCP)
  • mcp_chart_visualization (Antvis Chart MCP)
  • mcp_e2e_cypress (Cypress Test Runner)
  • mcp_team_communication (Slack MCP)

Routing Map Updates

Add to capability_routing:

  • mcp_repository_context: history-miner
  • mcp_e2e_testing: browser-automation
  • mcp_vulnerability_scan: security-auditor
  • mcp_prompt_versioning: prompt-optimizer
  • mcp_tech_monitoring: capability-analyst
  • mcp_documentation_access: system-analyst
  • mcp_web_search: capability-analyst
  • mcp_chart_visualization: pipeline-judge
  • mcp_team_communication: product-owner

Files to Modify

  • .kilo/capability-index.yaml
  • .kilo/agents/orchestrator.md
  • .kilo/kilo.jsonc
  • AGENTS.md
  • .kilo/KILO_SPEC.md

Milestone

Phase 2: MCP Integration - Quality and Knowledge #56

## User Story As an orchestrator, I need all 18 MCP integrations registered in capability-index.yaml with proper routing so that I can dispatch tasks to MCP-enabled agents. ## Acceptance Criteria - [ ] Update capability-index.yaml with new MCP capabilities - [ ] Update orchestrator.md permissions for all new agents - [ ] Update kilo.jsonc with new agent configurations - [ ] Update AGENTS.md with new capabilities - [ ] Update KILO_SPEC.md documentation - [ ] Run full pipeline test to verify routing - [ ] Verify all 18 MCP servers accessible ## New Capabilities to Add ### Phase 1 Capabilities - mcp_repository_context (GitMCP) - mcp_e2e_testing (Playwright MCP) - mcp_agent_patterns (Multi Agent Architect MCP) - mcp_api_conversion (OpenAPI to MCP Converter) - mcp_prompt_versioning (Ai Prompt Library) - mcp_tech_monitoring (DevTrends MCP) - mcp_vulnerability_scan (CVE Search MCP) - mcp_server_validation (MCP Validator) ### Phase 2 Capabilities - mcp_documentation_access (Docfork + API Doc MCP) - mcp_web_search (Brave Search + Tavily MCP) - mcp_knowledge_base (Wikipedia + ArXiv MCP) - mcp_document_conversion (Markitdown MCP) - mcp_chart_visualization (Antvis Chart MCP) - mcp_e2e_cypress (Cypress Test Runner) - mcp_team_communication (Slack MCP) ## Routing Map Updates Add to capability_routing: - mcp_repository_context: history-miner - mcp_e2e_testing: browser-automation - mcp_vulnerability_scan: security-auditor - mcp_prompt_versioning: prompt-optimizer - mcp_tech_monitoring: capability-analyst - mcp_documentation_access: system-analyst - mcp_web_search: capability-analyst - mcp_chart_visualization: pipeline-judge - mcp_team_communication: product-owner ## Files to Modify - .kilo/capability-index.yaml - .kilo/agents/orchestrator.md - .kilo/kilo.jsonc - AGENTS.md - .kilo/KILO_SPEC.md ## Milestone Phase 2: MCP Integration - Quality and Knowledge #56
NW closed this issue 2026-04-19 09:57:51 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agent::agent-architect
Owned by agent-architect
 agent::capability-analyst
Owned by capability-analyst
 agent::code-skeptic
Owned by code-skeptic
 agent::evaluator
Owned by evaluator
 agent::history-miner
Owned by history-miner
 agent::lead-developer
Owned by lead-developer
 agent::orchestrator
Owned by orchestrator
 agent::sdet-engineer
Owned by sdet-engineer
 agent::system-analyst
Owned by system-analyst
 agent::the-fixer
Owned by the-fixer
 budget::exhausted
Token budget exhausted
 budget::sufficient
Token budget sufficient
 budget::warning
Token budget low
 cascade::depth-0
No subagent calls
 cascade::depth-1
1-level subagent calls
 cascade::depth-2
2-level subagent calls
 cascade::depth-exceeded
Depth limit exceeded
 cascade::depth-n
Unlimited subagent calls
 dashboard::frozen
Dashboard feature freeze — no new features until thaw
 evolution::model-change
Model change evolution
 evolution::new-agent
New agent evolution
 evolution::new-skill
New skill evolution
 evolution::new-workflow
New workflow evolution
 evolution::prompt-opt
Prompt optimization evolution
 memory::checkpoint
Checkpoint stored
 memory::fresh
Checkpoint fresh
 memory::recoverable
Checkpoint recoverable
 memory::stale
Checkpoint stale
 permission::evolve-system
Can evolve system
 permission::read-only
Read-only access
 permission::violation
Security violation
 permission::write-code
Can write code
 permission::write-config
Can write config
 phase::awaiting-review
Agent awaits review
 phase::drafting-spec
Agent is drafting specification
 phase::executing
Agent is executing task
 phase::gathering-evidence
Agent is gathering data
 phase::refining-prompt
Agent is refining prompts
 phase::researching
Research phase — gathering evidence and solutions
 phase::verifying
Agent is verifying results
 priority::critical
Critical priority
 priority::high
High priority
 priority::low
Low priority
 priority::medium
Medium priority
 quality::blocked
Blocked by quality
 quality::fail
Quality check failed
 quality::needs-fix
Needs fixes
 quality::pass
Quality check passed
 size::l
Large (4-8 hours)
 size::m
Medium (2-4 hours)
 size::s
Small (1-2 hours)
 size::xl
Extra large (>8 hours)
 size::xs
Extra small (<1 hour)
 status::blocked
Blocked
 status::cancelled
Cancelled
 status::done
Completed
 status::in-progress
Work in progress
 status::new
New issue, not started
 status::planned
Planned for sprint
 status::review
Under review
 status::testing
In testing
 type::bug
Something is broken
 type::chore
Maintenance task
 type::documentation
Documentation
 type::enhancement
Improvement
 type::feature
New feature
 type::refactor
Code refactoring
 type::test
Testing
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
NW olilovedani
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: UniqueSoft/APAW#56
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?