SA
SkillAvatars
Back to MCP Tools

Ateles

devops-infra MCP Server

Personal agent swarm infrastructure — attributed, capability-scoped, Neotoma-canonical

bymarkmhendrickson
Verified
devops-infradevops-infra
3 views1 stars0 forks
View on GitHub

Why This Matters

Discovered via github-topic:mcp and last synced 3mo ago.

Verified
Source
github-topic:mcp
Stars
1
Last synced
3mo ago
Install
Check source

Install

Install instructions not detected yet

Check the source repository for the latest setup steps.

View source instructions
17
Tools
0
Resources
0
Prompts
Standard I/O
Transport

Available Tools (17)

notifies

Onychomys Anthus -->

agent_action_observation

One row per harness tool call — AAuth sub, PAT attribution, tool, owner/repo, result

dispatch

Others[20+ other T4 agents] Gryllus & Vanellus & Pavo & Others -->

Foundation

What it means

Property

Without swarm infra

participation_record

Per-gate dispatch + satisfaction history

Concept

Lives as

Interface

Description

agent_definition

Identity, prompt, triggers, context types, operational types, allowed tools

Mode

What you're doing

agent_grant

Capability scope — Neotoma entity-type allowlist + MCP tool allowlist + external resource scope

entity_type

What it stores

Tier

Role

workflow_definition

Phases, gates, owner agents, skip conditions, preconditions

agent_policy

Operating rules (mandatory/recommended/prohibited) with scope

strategy_drift_signal

Agent-emitted observation when work contradicts current operating assumptions

Tool

How Ateles uses it

Browse all MCP servers