Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From tak
References TAK Server API for missions, data sync, WebCOP, CoT events, federation, certificates, endpoints, authentication, and administration. Use when integrating with TAK/ATAK servers.
npx claudepluginhub nkuntz1934/tak-skills --plugin takHow this skill is triggered — by the user, by Claude, or both
Slash command
/tak:tak-serverThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
TAK (Team Awareness Kit) Server provides situational awareness through real-time position tracking (CoT), mission-based data sharing, and federated server connectivity. The API is a REST interface (OpenAPI 3.1.0) served over HTTPS on port 8446 (TLS/mTLS) or HTTP on port 8080.
Provides curl examples to create, list, and manage Telnyx Missions—automated workflows and tasks for AI-driven telecom operations.
Conducts red team operations with Covenant C2 for authorized adversary simulation, including listener setup, grunt deployment, task execution, and lateral movement tracking.
Conducts red team operations with Covenant C2 for authorized adversary simulation, including listener setup, grunt deployment, task execution, and lateral movement tracking.
Share bugs, ideas, or general feedback.
TAK (Team Awareness Kit) Server provides situational awareness through real-time position tracking (CoT), mission-based data sharing, and federated server connectivity. The API is a REST interface (OpenAPI 3.1.0) served over HTTPS on port 8446 (TLS/mTLS) or HTTP on port 8080.
This skill is organized into focused reference files. Read the one that matches what the user needs:
| Reference | When to read |
|---|---|
references/endpoints.md | Looking up any specific API endpoint, path, method, or parameters |
references/mission-api.md | Working with missions, data sync, subscriptions, content, or mission packages |
references/webcop-api.md | Building browser-based SA, WebSocket/STOMP messaging, chat, or COP views |
references/schemas.md | Configuration schemas, response formats, or data types |
references/connections-auth.md | Connecting to TAK Server, authentication methods, CoT XML format, certificate management, input configuration |
TAK Server supports two auth methods:
All JSON responses follow a standard envelope:
// Success
{"version": "1.0.0", "type": "<ResourceType>", "data": [...]}
// Error (404, 400, etc.)
{"status": "NOT_FOUND", "code": 1, "message": "Human-readable error"}
2016-04-22T15:26:17.260Zapplication/json;charset=UTF-8 unless returning binary filesCoT is the XML-based messaging format used across all TAK products. Key fields:
ANDROID-48:5A:3F:52:29:78)a-f-G-U-C = friendly ground unit combat)Missions are the primary collaboration mechanism. They contain:
Content is referenced by deterministic hash of binary content. Clients subscribe to missions and receive change notifications. Mission roles control access: MISSION_OWNER, MISSION_SUBSCRIBER, MISSION_READONLY_SUBSCRIBER.
The TAK Server API is organized into these groups:
Core Data:
Real-time / Browser:
Administration:
Collaboration:
Server Management:
Other: