Skip to content

MCP Internal Tools

MCP internal tools are Model Context Protocol tools that enable AI assistants to discover, install, manage, and interact with MCP servers programmatically. These tools are exposed through the MCP protocol and provide comprehensive automation capabilities for server lifecycle management.

Unlike CLI commands which are used by humans, internal tools are designed specifically for AI assistant integration and automated workflows.

Overview

The internal tools are organized into three functional domains:

Tool Categories

Discovery Tools

Enable AI assistants to search for and discover MCP servers from various registries and sources.

  • mcp_search - Search MCP registry for servers
  • mcp_registry_status - Check registry availability and health
  • mcp_registry_info - Get detailed registry information
  • mcp_registry_list - List available registries
  • mcp_info - Get detailed server information

Installation Tools

Provide complete lifecycle management for MCP server installation and removal.

  • mcp_install - Install MCP server from registry or custom source
  • mcp_uninstall - Remove MCP server with backup and rollback options
  • mcp_update - Update MCP server to latest or specified version

Management Tools

Offer operational control over MCP servers including state management and configuration.

  • mcp_enable - Enable a disabled MCP server
  • mcp_disable - Disable an MCP server without removal
  • mcp_list - List MCP servers with filtering and status information
  • mcp_status - Get detailed server status and health information
  • mcp_reload - Reload server configuration or restart server
  • mcp_edit - Edit MCP server configuration

Example Usage

AI Assistant Workflow

Here's how an AI assistant might use these internal tools to help a user:

Example 1: Setting up a Development Environment

json
// User: "I need to work with a PostgreSQL database and Git repository"

[
  {
    "tool": "mcp_search",
    "arguments": {
      "query": "postgresql database"
    }
  },
  {
    "tool": "mcp_search",
    "arguments": {
      "query": "git repository"
    }
  },
  {
    "tool": "mcp_install",
    "arguments": {
      "serverName": "postgres",
      "version": "2.0.1"
    }
  },
  {
    "tool": "mcp_install",
    "arguments": {
      "serverName": "git",
      "version": "3.1.0"
    }
  },
  {
    "tool": "mcp_list",
    "arguments": {
      "filter": "enabled"
    }
  }
]

Example 2: Server Health Monitoring

json
// AI Assistant performs routine health check

[
  {
    "tool": "mcp_list",
    "arguments": {}
  },
  {
    "tool": "mcp_status",
    "arguments": {
      "serverName": "filesystem"
    }
  },
  {
    "tool": "mcp_registry_status",
    "arguments": {}
  }
]

Programmatic Integration

Example 3: CI/CD Pipeline Integration

bash
# Deploy script using 1MCP internal tools via API
#!/bin/bash

# Install required MCP servers for the project
echo "Installing MCP servers..."

curl -X POST http://localhost:3050/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "tool": "mcp_install",
    "arguments": {
      "serverName": "project-dependencies",
      "version": "latest"
    }
  }'

# Verify installation
curl -X POST http://localhost:3050/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "tool": "mcp_list",
    "arguments": {
      "filter": "enabled"
    }
  }'

Example 4: Infrastructure as Code

json
{
  "mcp_servers": [
    {
      "tool": "mcp_install",
      "arguments": {
        "serverName": "redis-cache",
        "version": "1.2.1",
        "config": {
          "host": "localhost",
          "port": 6379
        }
      }
    },
    {
      "tool": "mcp_install",
      "arguments": {
        "serverName": "file-storage",
        "version": "2.0.0",
        "config": {
          "rootPath": "/data/storage"
        }
      }
    }
  ]
}

Use Cases

AI Assistant Automation

AI assistants can use these tools to automatically:

  • Discover relevant servers for specific tasks or domains
  • Install required servers based on user needs or project requirements
  • Manage server lifecycle including updates, health monitoring, and troubleshooting
  • Orchestrate complex workflows involving multiple MCP servers

Programmatic Server Management

Developers can integrate these tools into:

  • CI/CD pipelines for automated MCP server deployment
  • Infrastructure as code solutions for server configuration
  • Monitoring systems for server health and performance tracking
  • Automated testing frameworks for MCP server validation

Dynamic Configuration

Tools enable dynamic server management scenarios:

  • On-demand server installation based on user requirements
  • Graceful server updates with rollback capabilities
  • Health-based server failover and recovery
  • Configuration synchronization across environments

Key Features

Comprehensive API Coverage

All internal tools provide complete input/output schemas with:

  • Typed parameters with validation and constraints
  • Structured output with consistent data formats
  • Error handling with detailed error information
  • Progress feedback for long-running operations

Safe Operations

Internal tools prioritize safety and reliability:

  • Backup and restore capabilities for destructive operations
  • Dependency validation to prevent breaking changes
  • Rollback support for failed operations
  • Health checks before and after operations

Integration-Friendly

Designed for seamless AI assistant integration:

  • Semantic naming following MCP conventions
  • Descriptive error messages for troubleshooting
  • Progress indicators for user feedback
  • Cross-references between related operations

API Reference

For detailed API documentation including schemas, parameters, and examples:

Getting Started

AI assistants typically access these tools through the MCP protocol when connected to a 1MCP instance. The tools are automatically available based on the server's capabilities and configuration.

For CLI users, many of these capabilities are also available through the 1MCP commands, providing human-friendly interfaces for the same operations.

See Also

Released under the Apache 2.0 License.