global-chat-agent-discovery

Locates MCP servers and AI agents across registries for cross-protocol discovery.

27|5|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Fandry96/k3-agentic-skills --skill global-chat-agent-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: global-chat-agent-discovery
Source: https://github.com/Fandry96/k3-agentic-skills/tree/main/skills/global-chat-agent-discovery
Command: npx skills add https://github.com/Fandry96/k3-agentic-skills --skill global-chat-agent-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Global Chat is a cross-protocol AI agent discovery platform that aggregates MCP servers and AI agents from 6+ registries into a single searchable directory. This skill helps you find the right MCP server, A2A agent, or agents.txt endpoint for any task by searching across 18,000+ indexed entries. It also provides an MCP server (@global-chat/mcp-server) for programmatic access to the directory from any MCP-compatible client.

When to Use This Skill

  • Use when you need to find an MCP server for a specific capability (e.g., database access, file conversion, API integration)
  • Use when evaluating which agent registries carry tools for your use case
  • Use when you want to search across multiple protocols (MCP, A2A, agents.txt) simultaneously
  • Use when setting up agent-to-agent communication and need to discover available endpoints

How It Works

The skill supports searching across MCP, A2A, and agents.txt registries and exposes an MCP server for programmatic directory access, enabling rapid discovery and integration in agent workflows.

Quick Start

Use this skill to locate MCP servers and A2A agents across registries and begin integration.

Frequently Asked Questions about global-chat-agent-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find MCP servers for specific agent integration tasks?

Search across MCP, A2A, and agents.txt registries simultaneously to locate specific AI agents and endpoints. This cross-protocol discovery evaluates 18,000+ indexed entries across six registries to help you find the right server for capabilities like database access or file conversion.

What is cross-protocol agent discovery and when do I need it?

Cross-protocol agent discovery locates MCP servers and AI agents by searching across MCP, A2A, and agents.txt registries simultaneously. You need it when setting up agent-to-agent communication or evaluating which registries carry the tools required for your automation workflows.

Can I programmatically search for A2A agents and MCP servers from my client?

Yes, you can access the directory programmatically using the @global-chat/mcp-server. This exposes the cross-protocol search functionality to any MCP-compatible client, enabling rapid discovery and integration within your existing agent workflows.

Does cross-protocol discovery support searching agents.txt and A2A endpoints at the same time?

Yes, cross-protocol discovery supports searching across MCP, A2A, and agents.txt registries simultaneously. This allows you to evaluate available endpoints across multiple protocols in a single search rather than querying each registry individually.

What are the limitations of using a centralized directory for agent discovery?

The directory aggregates from 6+ external registries, meaning discovery is limited to the indexing frequency and availability of those upstream sources. It functions as a search aggregator rather than a host, so endpoint reliability depends on the original registry.