How do I install the 2704 008 Federation Discovery 753ace5b skill?

Run npx skillmds@latest add tools-only/2704-008-federation-discovery-753ace5b in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the 2704 008 Federation Discovery 753ace5b skill do?

ADR-0008: Federation & Auto-Discovery via DNS-SD It is listed under Product & Planning on SkillMD.

Is 2704 008 Federation Discovery 753ace5b safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 2704 008 Federation Discovery 753ace5b?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 2704 008 Federation Discovery 753ace5b free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published 2704 008 Federation Discovery 753ace5b?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

2704 008 Federation Discovery 753ace5b by tools-only

Name: 2704 008 Federation Discovery 753ace5b
Author: tools-only

File contents

ADR-0008: Federation & Auto-Discovery via DNS-SD

Status: Deprecated (see #1912)
Date: 2025-02-21
Deprecated: 2026-01-07
Deciders: Core Engineering Team

⚠️ Deprecation Notice: The DiscoveryService (mDNS auto-discovery) and ForwardingService have been removed. The ToolService now handles all gateway tool invocations with improved OAuth, plugin, and SSE support. Gateway peer management via /gateways API remains available.

Context

ContextForge must support federated operation, where multiple gateway instances:

Automatically discover each other on a shared network
Exchange metadata and tool/service availability
Merge registries and route calls to remote nodes

Manual configuration (e.g. hardcoded peer IPs) is error-prone and brittle in dynamic environments like laptops or Kubernetes.

The codebase included a DiscoveryService and federation settings such as:

FEDERATION_ENABLED (deprecated)
FEDERATION_DISCOVERY (deprecated)
FEDERATION_PEERS (deprecated)
FEDERATION_SYNC_INTERVAL (deprecated)

Decision

We enabled auto-discovery via DNS-SD (mDNS/zeroconf) by default. Each gateway:

Published itself using _mcp._tcp.local. with TXT records
Periodically probed for peers using zeroconf or a fallback registry
Merged discovered gateways into its internal routing map
Sent periodic liveness pings to verify peer health

Static peer configuration was supported for restricted networks.

Consequences

🔌 Gateways connected seamlessly on the same local network or overlay mesh
🕵️♂️ DNS-SD added moderate background network traffic, tunable via TTL
⚠️ Firewalls or environments without multicast required static peer config
♻️ Federated topologies were self-healing and required no orchestration

Alternatives Considered

Option	Why Not
Static peer list only	Manual entry, error-prone, not zero-config.
Central registry (e.g. etcd, Consul)	Adds external infrastructure and tight coordination.
Cloud DNS-based discovery	Requires cloud provider integration and persistent internet access.
gRPC service registry	Less transparent, requires protobuf tooling and internal coordination layer.

Deprecation Rationale

mDNS Discovery was not required for current deployment models (Kubernetes, cloud environments)
ForwardingService duplicated functionality already present in ToolService, which provides more advanced features (OAuth, plugins, SSE)
Gateway peer management remains available via the /gateways REST API
FEDERATION_TIMEOUT setting is retained for gateway request timeouts

Status

Deprecated. The DiscoveryService and ForwardingService have been removed. Use the /gateways API for manual gateway peer registration.

---name: 2704-008-federation-discovery-753ace5bdescription: ADR-0008: Federation & Auto-Discovery via DNS-SD---# ADR-0008: Federation & Auto-Discovery via DNS-SD- *Status:* **Deprecated** (see [#1912](https://github.com/IBM/mcp-context-forge/issues/1912))- *Date:* 2025-02-21- *Deprecated:* 2026-01-07- *Deciders:* Core Engineering Team> **⚠️ Deprecation Notice:** The `DiscoveryService` (mDNS auto-discovery) and `ForwardingService` have been removed. The `ToolService` now handles all gateway tool invocations with improved OAuth, plugin, and SSE support. Gateway peer management via `/gateways` API remains available.## ContextContextForge must support **federated operation**, where multiple gateway instances:- Automatically discover each other on a shared network- Exchange metadata and tool/service availability- Merge registries and route calls to remote nodesManual configuration (e.g. hardcoded peer IPs) is error-prone and brittle in dynamic environments like laptops or Kubernetes.The codebase included a `DiscoveryService` and federation settings such as:- `FEDERATION_ENABLED` *(deprecated)*- `FEDERATION_DISCOVERY` *(deprecated)*- `FEDERATION_PEERS` *(deprecated)*- `FEDERATION_SYNC_INTERVAL` *(deprecated)*## DecisionWe enabled **auto-discovery via DNS-SD (mDNS/zeroconf)** by default. Each gateway:- Published itself using `_mcp._tcp.local.` with TXT records- Periodically probed for peers using `zeroconf` or a fallback registry- Merged discovered gateways into its internal routing map- Sent periodic liveness pings to verify peer healthStatic peer configuration was supported for restricted networks.## Consequences- 🔌 Gateways connected seamlessly on the same local network or overlay mesh- 🕵️♂️ DNS-SD added moderate background network traffic, tunable via TTL- ⚠️ Firewalls or environments without multicast required static peer config- ♻️ Federated topologies were self-healing and required no orchestration## Alternatives Considered| Option | Why Not ||--------|---------|| **Static peer list only** | Manual entry, error-prone, not zero-config. || **Central registry (e.g. etcd, Consul)** | Adds external infrastructure and tight coordination. || **Cloud DNS-based discovery** | Requires cloud provider integration and persistent internet access. || **gRPC service registry** | Less transparent, requires protobuf tooling and internal coordination layer. |## Deprecation Rationale- **mDNS Discovery** was not required for current deployment models (Kubernetes, cloud environments)- **ForwardingService** duplicated functionality already present in `ToolService`, which provides more advanced features (OAuth, plugins, SSE)- Gateway peer management remains available via the `/gateways` REST API- `FEDERATION_TIMEOUT` setting is retained for gateway request timeouts## Status**Deprecated.** The `DiscoveryService` and `ForwardingService` have been removed. Use the `/gateways` API for manual gateway peer registration.

Frequently asked questions

2704 008 Federation Discovery 753ace5b