Equinix Docs and API Specifications MCP Server

This project is an experimental Model Context Protocol (MCP) server, for local use and learning, that provides access to Equinix APIs and documentation. This project is not expected to offer high quality (production-ready) results. This is offered for developers learning about MCP, Equinix APIs and documentation, and their potential integration.

Note

The full list of Equinix API operationIds will overwhelm the context windows of local LLMs making this tool impractical for more than learning.

Features

• API Access: Fetches and caches Equinix API specifications then exposes operationIds as MCP tools.
  • API Authentication: Supports both OAuth2 Client Credentials used by most API services and Metal API tokens
  • Configurable Overlays: Use overlay specifications to normalize API responses before LLM processing
  • Arazzo Workflows (Experimental): Define and execute higher-level workflows chaining multiple API operations
• Documentation Integration: Search Equinix documentation via sitemap and Lunr search
  • TODO: fetch docs content (and not just the URLs)

Supported APIs

Any Equinix API specification can be added to the configuration file but operations may need to be filtered and overlays may be needed for this tool to use the spec in the MCP server. The config/apis.yaml file defines API specifications that have been used during development to test behavior.

Quick Start

Installation

python3 -m venv .venv
source .venv/bin/activate
pip install -e .

Or replace .venv/bin/python with uvx (if preferred) and change the commands examples and configuration blocks accordingly.

Adding the MCP Server to VS Code

After cloning this repository, you can add the Equinix MCP server to VS Code with a single command:

Using Python Virtual Environment (.venv)

code --add-mcp '{
 "servers": {
  "equinix": {
   "type": "stdio",
   "command": ".venv/bin/python",
   "args": [
    "-m",
    "equinix_docs_mcp_server.main"
   ],
   "cwd": "'$PWD'",
   "env": {
    "PYTHONPATH": "'$PWD'$'/src",
    "EQUINIX_CLIENT_ID": "$\{input:EQUINIX_CLIENT_ID\}",
    "EQUINIX_CLIENT_SECRET": "$\{input:EQUINIX_CLIENT_SECRET\}",
    "EQUINIX_METAL_TOKEN": "$\{input:EQUINIX_METAL_TOKEN\}"
   },
   "disabled": false
  }
 },
 "inputs": [
  {
   "type": "promptString",
   "id": "EQUINIX_CLIENT_ID",
   "description": "Equinix Client ID",
   "password": true
  },
  {
   "type": "promptString",
   "id": "EQUINIX_CLIENT_SECRET",
   "description": "Equinix Client Secret",
   "password": true
  },
  {
   "type": "promptString",
   "id": "EQUINIX_METAL_TOKEN",
   "description": "Equinix Metal API Token",
   "password": true
  }
 ]
}}'

Note: The configuration is stored in .vscode/mcp.json per project. You do not need to set cwd unless you have a special setup.

For more details, see VS Code MCP Server documentation.

Usage

Configuration

Set your Equinix API credentials as environment variables:

# Required for most APIs (OAuth2 Client Credentials)
export EQUINIX_CLIENT_ID="your_client_id"
export EQUINIX_CLIENT_SECRET="your_client_secret"

# Optional for Metal API (if you prefer API token over OAuth2)
export EQUINIX_METAL_TOKEN="your_metal_token"

API Spec Fetching

The server uses cached API specifications by default for faster startup. Use --update-specs to force fetching fresh specs from remote sources.

equinix-docs-mcp-server --update-specs # --config path/to/custom/config.yaml

Server Configuration

The server is configured via config/apis.yaml. This file defines:

• API endpoints and versions
• Authentication methods
• Overlay file locations
• Documentation settings

Example API Configuration

apis:
  metal:
    url: "https://docs.equinix.com/api-catalog/metalv1/openapi.yaml"
    overlay: "overlays/metal.yaml"
    auth_type: "metal_token"
    service_name: "metal"
    version: "v1"
    # include: []
    # exclude: [".*"]
    # enabled: true

  fabric:
    url: "https://docs.equinix.com/api-catalog/fabricv4/openapi.yaml"
    overlay: "overlays/fabric.yaml"
    auth_type: "client_credentials"
    service_name: "fabric"
    version: "v4"

Overlay Files

Overlay files in the overlays/ directory normalize API specifications before processing:

• Standardize authentication schemes
• Normalize base paths and servers
• Add consistent tagging
• Handle API-specific quirks

Available MCP Tools

The server exposes MCP tools for:

1. API Operations: Dynamic tools generated from individual API specifications
2. Documentation:
   • list_docs - List and filter documentation
   • find_docs - Find documentation by filename/title matching
   • search_docs - Full-text search documentation using indexed content
3. Workflows (Arazzo):
   • Tools prefixed with workflow__ represent multi-step orchestrations defined in Arazzo-like YAML files.
   • Example: workflow__list_metal_metros_then_prices

Defining Arazzo Workflows (Experimental)

Add an arazzo section to your config/apis.yaml:

arazzo:
   specs:
      - examples/workflows.yaml

Example workflow spec (examples/workflows.yaml):

workflows:
   list_metal_metros_then_prices:
      description: Retrieve Metal metros then spot market prices.
      inputs:
         metro: "SV"
      steps:
         - id: get_metros
            operation: metal_findMetros
            saveAs: metros
         - id: get_prices
            operation: metal_findMetroSpotMarketPrices
            params:
               metro: "{{ metro }}"
            saveAs: prices

Run the server and invoke: workflow__list_metal_metros_then_prices.

Currently supported features:

• Sequential steps referencing existing API tools
• Simple variable capture via saveAs
• Jinja2 templated parameter rendering (falls back to Python str.format)

Development

Running Tests

pip install -e .[dev]
pytest

License

MIT License. See LICENSE for details.

Links

• Equinix Documentation
• Equinix API Documentation
• FastMCP Framework
• Model Context Protocol