MCP tools discovery

This guide explains how to discover and use MCP (Model Context Protocol) tools available on the Bridge Platform. MCP tools provide your agent with capabilities to interact with external services like ServiceNow, Azure, Dynatrace, and the Bridge Data platform.

Before registering your agent in the Bridge Catalog, you need to:

Discover available MCP tools on your Bridge Platform instance

Select the tools your agent requires

Configure the tools in your agent-catalog-registration.json

The Bridge Platform provides a centralized MCP server that exposes tools from multiple backend services.

Prerequisites

Bridge Platform access with KAIF_HOST URL

Service API Key (SERVICE_API_KEY)

MCP Server URL (BRIDGE_MCP_SERVER_URL) — optional; SDK auto-resolves from KAIF_HOST

Python 3.12+ with requests and python-dotenv packages

Discovery Script

Use the scripts/list_mcp_tools.py utility to discover available MCP tools.

Installation

Copy the script to your agent project:

mkdir -p scripts
# Copy from template or sample agent repository

Configuration

Ensure your .env file contains the required variables:

# Bridge Platform host
KAIF_HOST=https://your-instance.bridge.kyndryl.com

# Service API Key (from Bridge Platform Admin)
SERVICE_API_KEY=your-service-api-key

# MCP Server URL (optional — SDK auto-resolves from KAIF_HOST in bridge_dev)
# BRIDGE_MCP_SERVER_URL=https://your-account-us-accountid.bridge.kyndryl.com/kaif/v2/mcp/tools

Usage

# Activate virtual environment
source venv/bin/activate

# List all available tools (summary view)
python scripts/list_mcp_tools.py

# Export tools to JSON file
python scripts/list_mcp_tools.py --output available-tools.json

# Format for catalog registration
python scripts/list_mcp_tools.py --format catalog --output catalog-tools.json

# Filter specific MCP servers
python scripts/list_mcp_tools.py --filter servicenow,bridge

# Quiet mode (for CI/CD)
python scripts/list_mcp_tools.py --quiet --output tools.json

Command options

Option	Description
--output, -o	Output file path (JSON format)
--format, -f	Output format: raw, catalog, summary (default)
--filter	Comma-separated MCP server prefixes to filter
--quiet, -q	Suppress progress messages

Available MCP servers

The Bridge Platform typically provides these MCP servers:

Core platform tools

MCP Server	Description	Common Operations
servicenow_mcp	ServiceNow ITSM integration	servicenow_get_all_incidents, servicenow_create_incident, servicenow_search_incidents
bridge_mcp	Bridge Data Platform	bridge_execute_query, bridge_list_domains, bridge_get_table_details
aiops_mcp	Artificial Intelligence for IT Operations Analytics	aiops_ask_me_anything, aiops_nlq_service

Cloud provider tools

MCP Server	Description	Example Operations
azure_mcp	Azure services (50+ tools)	azure_aks, azure_keyvault, azure_monitor, azure_cosmos

Observability tools

MCP Server	Description	Example Operations
dynatrace_mcp (if configured)	Dynatrace monitoring	execute_dql, list_problems, get_environment_info
mock_mcp	Mock data for testing	mock_datadog_metrics, mock_servicenow_changes

Utility tools

MCP Server	Description	Operations
search_mcp	Web search	search_web, search_news, search_images
file_mcp	File operations	file_read, file_write, file_list_directory
db_mcp	MongoDB operations	db_mongo_query, db_mongo_insert
api_mcp	HTTP requests	api_get, api_post, api_request

Tool definition structure

Each MCP tool has this structure:

{
 "name": "servicenow_get_all_incidents",
 "description": "Get all incidents from ServiceNow ITSM platform...",
 "inputSchema": {
 "type": "object",
 "properties": {
 "limit": {
 "type": "integer",
 "description": "Maximum number of incidents to return",
 "default": 100
 }
 },
 "required": []
 }
}

Key fields

Field	Description
name	Tool identifier (used in call_tool())
description	What the tool does
inputSchema	JSON Schema defining required/optional parameters
inputSchema.required	List of mandatory parameters