MCP Server Card Support

Publish MCP server metadata at /.well-known/mcp/server-card.json for automated discovery.

21|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/berkayoztunc/orquestra --skill mcp-server-card-support
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: MCP Server Card Support
Source: https://github.com/berkayoztunc/orquestra/tree/main/packages/frontend/assets/.well-known/agent-skills/mcp-server-card
Command: npx skills add https://github.com/berkayoztunc/orquestra --skill mcp-server-card-support

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Agents often need a reliable way to discover which MCP server endpoint to call, without hard-coded URLs or extra documentation.

Core Features & Use Cases

  • Publishes an MCP Server Card: Exposes MCP server metadata at /.well-known/mcp/server-card.json so tools can locate the server.
  • Includes discovery-ready transport and tool info: Provides serverInfo (name/version), Streamable HTTP endpoint details, and the public MCP tool capability names for the surface.
  • Use Case: When integrating an AI agent with Orquestra, the agent can automatically discover where to send MCP requests and which tools are available.

Quick Start

Ask an AI agent to read the MCP server card at /.well-known/mcp/server-card.json, then configure an MCP client to use the advertised endpoint and tool list.

Frequently Asked Questions about MCP Server Card Support

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

FAQPage Schema
How do I enable automatic MCP server discovery for AI agents?

MCP server discovery is enabled by publishing a server-card JSON at /.well-known/mcp/server-card.json. This file exposes server metadata so AI agents can automatically locate the correct Streamable HTTP endpoint without manual URL configuration.

What information needs to be included in an MCP server card?

An MCP server card must include serverInfo with name and version, Streamable HTTP endpoint details, and the list of public MCP tool capability names available on that surface. This metadata allows agents to enumerate available tools automatically.

Can an AI agent locate MCP tools without hard-coded URLs?

Yes, an AI agent can locate MCP tools without hard-coded URLs by reading the server card at /.well-known/mcp/server-card.json. The agent extracts the advertised endpoint and tool list to configure its MCP client automatically.

How do I set up agent discovery for a Streamable HTTP MCP server?

To set up agent discovery for a Streamable HTTP MCP server, serve a valid server-card JSON at /.well-known/mcp/server-card.json. Ask an AI agent to read this card, then configure an MCP client to use the advertised endpoint and tool list.

Does MCP server discovery work with Orquestra integrations?

Yes, MCP server discovery works with Orquestra integrations by exposing server metadata at the well-known URI. This allows Orquestra AI agents to automatically discover where to send MCP requests and identify available tools.