Which integrations are available for this server?

Provides comprehensive integration with the [Eagle](/mcp/servers/integrations/eagle) app, enabling management of folders and items (images, documents, media) in an Eagle library. Supports creating, renaming, and updating folders; adding items from URLs and file paths; retrieving item information, thumbnails, and source files; and managing items through operations like moving to trash and updating metadata. Supports visualization of workflows and architecture diagrams through [Mermaid](/mcp/servers/integrations/mermaid) integration, as demonstrated in the use case diagrams showing different deployment scenarios.

Eagle MCP Server (Unofficial)

NOTE

Official MCP support is planned for Eagle v5 (public beta in Q1 2026)

A Model Context Protocol (MCP) server for Eagle.

JPG / JPEG
PNG
PDF
SVG
MP4
MP3
FBX
OBJ
EPS
TIF / TIFF
WebP
BMP
ICO
RAW
etc

Eagle: https://eagle.cool/
Eagle API docs: https://api.eagle.cool/

Requirements

Python 3.13
uv

Related MCP server: Alchemy MCP Server

Prerequisites

Install the required dependencies:

uv sync

Usage

Launch the Eagle app.
Launch this MCP server by running the following command:

uv run main.py

Connecting to the MCP Server using Streamable HTTP

MCP config:

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

{ "mcpServers": { "eagle-mcp-server": { "command": "uvx", "args": [ "--from", "git+https://github.com/tuki0918/eagle-mcp-server@fastmcp-stdio", "eagle-mcp-server" ] } } }

See #17 for more details.

Tools

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

MCP Server API docs:

Enabling Disabled Tools

Some tools are disabled by default (shown as empty cells in the "Enabled (default)" column above). To enable these disabled tools:

Locate the tool definition in the source code
Remove the tags=["Disabled"] line from the tool configuration
Restart the MCP server

This will make the previously disabled tools available for use.

Use Cases

1) Same Host (Recommended)

flowchart LR subgraph 192.168.1.100 direction LR subgraph FileSystem [File System] end subgraph EagleApp [Eagle App localhost:41595] end subgraph MCPServer [MCP Server 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

You have direct access to the filesystem.

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

flowchart LR subgraph 192.168.1.100 subgraph FileSystem [File System] end subgraph EagleApp [Eagle App localhost:41595] end subgraph MCPServer [MCP Server 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

You don't have access to the filesystem.

3) Other Host

flowchart LR subgraph 192.168.1.100 subgraph FileSystem [File System] end subgraph EagleApp [Eagle App localhost:41595] end end subgraph 192.168.1.101 subgraph MCPServer [MCP Server 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

You don't have access to the filesystem.

Eagle MCP Server

Eagle MCP Server (Unofficial)

Requirements

Prerequisites

Usage

Connecting to the MCP Server using Streamable HTTP

Tools

Enabling Disabled Tools

Use Cases

1) Same Host (Recommended)

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

3) Other Host

Resources

New MCP Servers

Latest Blog Posts

MCP directory API