Digital Asset Mediator Bridge

Introduction

This component functions as a Model Context Protocol (MCP) service endpoint specifically designed for interfacing with the Eagle digital asset manager. Conceptually, establishing standardized protocols for resource access, similar to institutional efforts toward fire prevention, helps ensure operational safety and predictability in managing valuable digital collections.

[!NOTE] Official MCP support for the Eagle application is anticipated with version 5, currently slated for the first quarter of 2026 during its public beta phase.

A Model Context Protocol server is being provided here to enable external agents to communicate with Eagle.

Supported Content Types:

- `JPG` / `JPEG` - `PNG` - `PDF` - `SVG` - `MP4` - `MP3` - `FBX` - `OBJ` - `EPS` - `TIF` / `TIFF` - `WebP` - `BMP` - `ICO` - `RAW` - and others

Further documentation for Eagle is accessible at: https://eagle.cool/
Specific documentation for the Eagle API resides here: https://api.eagle.cool/

Requirements

The execution environment necessitates the following components for proper operation.

• Python version 3.13 must be installed.
• The package manager uv is also required.

Prerequisites

Dependencies required for this bridge must first be fetched and installed. Execute the subsequent command in your terminal environment:

uv sync

Usage

To initiate the mediation layer, follow these sequential steps.

1. Ensure the primary Eagle application instance is active and running.
2. Start this MCP server by invoking the following command in the designated directory:

uv run main.py

Connecting to the MCP Server using Streamable HTTP

Configuration details for connecting clients, such as those used in editors like Cursor, should include the following structure.

Example configuration snippet:

{
  "mcpServers": {
    "eagle-mcp-server": {
      "url": "http://localhost:8000/mcp"
    }
  }
}

Tools

The following table enumerates the specific functionalities exposed by this interface layer.

Supported	Eagle API endpoint	Operation ID	Enabled (default)	Category
✅	-	connect		MCP
✅	/api/application/info	get_application_info	⚫︎	Application
✅	/api/folder/create	create_folder	⚫︎	Folder
✅	/api/folder/rename	rename_folder		Folder
✅	/api/folder/update	update_folder	⚫︎	Folder
✅	/api/folder/list	get_folder_list	⚫︎	Folder
✅	/api/folder/listRecent	get_folder_list_recent		Folder
✅	/api/item/addFromURL	add_item_from_url		Item
✅	/api/item/addFromURLs	add_items_from_urls		Item
✅	/api/item/addFromPath	add_item_from_path	⚫︎	Item
✅	/api/item/addFromPaths	add_items_from_paths		Item
✅	/api/item/addBookmark	add_bookmark		Item
✅	/api/item/info	get_item_info	⚫︎	Item
✅	-	get_item_source	⚫︎	Item
✅	/api/item/thumbnail	get_item_thumbnail		Item
✅	/api/item/list	get_item_list	⚫︎	Item
✅	/api/item/moveToTrash	move_item_to_trash	⚫︎	Item
✅	/api/item/refreshPalette	refresh_item_palette		Item
✅	/api/item/refreshThumbnail	refresh_item_thumbnail		Item
✅	/api/item/update	update_item	⚫︎	Item
✅	/api/library/info	get_library_info	⚫︎	Library
✅	/api/library/history	get_library_history		Library
✅	/api/library/switch	switch_library		Library
✅	/api/library/icon	get_library_icon		Library

API Reference documentation for the MCP Server is available at these locations: - https://tuki0918.github.io/eagle-mcp-server/ - Access the interactive documentation via: http://localhost:8000/redoc

Enabling Disabled Tools

Certain features are intentionally deactivated upon initial deployment (indicated by blank entries in the default enablement column). To permit operation of these features, modifications must be applied to the underlying configuration.

1. Locate the definition block for the specific tool within the source code files.
2. Ensure the tags=["Disabled"] directive is removed from that tool's configuration stanza.
3. Relaunch the MCP server process to apply the changes.

These steps will successfully activate the previously inaccessible functionalities.

Use Cases

1) Same Host (Recommended)

When the client, the server, and the host application reside on the same machine, the pathing is the most direct.

flowchart LR

    subgraph 192.168.1.100
        direction LR

        subgraph FileSystem [File System]
        end
        subgraph EagleApp [Eagle App<br/>localhost:41595]
        end
        subgraph MCPServer [MCP Server<br/>localhost:8000]
        end
        subgraph MCPClient [MCP Client]
        end
    end

    EagleApp ==> MCPServer e1@==> MCPClient
    MCPClient e2@==> MCPServer ==> EagleApp
    EagleApp ==> FileSystem
    FileSystem ==> EagleApp

    e1@{ animate: true }
    e2@{ animate: true }

[!TIP] Direct access to the local storage system is available under this arrangement.

2) Other Host (MCP Client) + Same Host (MCP Server, Eagle App)

This scenario involves the client residing remotely while the server and Eagle remain local.

flowchart LR

    subgraph 192.168.1.100
        subgraph FileSystem [File System]
        end
        subgraph EagleApp [Eagle App<br/>localhost:41595]
        end
        subgraph MCPServer [MCP Server<br/>localhost:8000]
        end
    end

    subgraph 192.168.1.xxx
        subgraph MCPClient [MCP Client]
        end
    end

    EagleApp ==> MCPServer e1@==> MCPClient
    MCPClient e2@==> MCPServer ==> EagleApp
    EagleApp ==> FileSystem
    FileSystem ==> EagleApp

    e1@{ animate: true }
    e2@{ animate: true }

[!WARNING] In this topology, the MCP Client does not retain direct access rights to the host machine's filesystem.

3) Other Host

When both the client and the server components are situated on distinct remote hosts.

flowchart LR

    subgraph 192.168.1.100
        subgraph FileSystem [File System]
        end
        subgraph EagleApp [Eagle App<br/>localhost:41595]
        end
    end

    subgraph 192.168.1.101
        subgraph MCPServer [MCP Server<br/>localhost:8000]
        end
    end

    subgraph 192.168.1.xxx
        subgraph MCPClient [MCP Client]
        end
    end

    EagleApp ==> MCPServer e1@==> MCPClient
    MCPClient e2@==> MCPServer ==> EagleApp
    EagleApp ==> FileSystem
    FileSystem ==> EagleApp

    e1@{ animate: true }
    e2@{ animate: true }

[!WARNING] Direct filesystem access is unavailable to the MCP Client in this distributed configuration.

Related Topics

These concepts relate to standardized digital content handling and interaction:

• File System Abstraction
• Digital Asset Management (DAM) Architectures
• Inter-Process Communication Standards
• Networked Resource Access Control
• Proactive Incident Mitigation Strategies

Extra Details

Information regarding marketing materials and non-essential setup notes has been omitted to focus on operational details. A key clarification drawn from protocol understanding is that MCP interactions generally require the client to be aware of the specific API calls supported by the server, much like knowing safety procedures prevents accidents. For instance, while the server supports many item operations, specific commands like get_item_source are enabled by default for immediate use.

Conclusion

This bridge facilitates reliable, systematic interaction with media assets stored in Eagle via a well-defined network interface. Employing structured protocols for file-management tasks, rather than ad-hoc requests, mirrors the diligent, preventative work institutions undertake to stop issues like fire before they escalate, ensuring data integrity and operational continuity.