Eagle MCP Server
Provides comprehensive integration with the 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 integration, as demonstrated in the use case diagrams showing different deployment scenarios.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Eagle MCP Serveradd this image from https://example.com/design.png to my inspiration folder"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Eagle MCP Server (Unofficial)

A Model Context Protocol (MCP) server for Eagle.
JPG/JPEGPNGPDFSVGMP4MP3FBXOBJEPSTIF/TIFFWebPBMPICORAWetc
Eagle: https://eagle.cool/
Eagle API docs: https://api.eagle.cool/
Requirements
Python 3.13
Related MCP server: files-mcp-ts
Prerequisites
Install the required dependencies:
uv syncUsage
Launch the Eagle app.
Launch this MCP server by running the following command:
uv run main.pyConnecting 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 |
✅ | - |
| MCP | |
✅ | /api/application/info |
| ⚫︎ | Application |
✅ | /api/folder/create |
| ⚫︎ | Folder |
✅ | /api/folder/rename |
| Folder | |
✅ | /api/folder/update |
| ⚫︎ | Folder |
✅ | /api/folder/list |
| ⚫︎ | Folder |
✅ | /api/folder/listRecent |
| Folder | |
✅ | /api/item/addFromURL |
| Item | |
✅ | /api/item/addFromURLs |
| Item | |
✅ | /api/item/addFromPath |
| ⚫︎ | Item |
✅ | /api/item/addFromPaths |
| Item | |
✅ | /api/item/addBookmark |
| Item | |
✅ | /api/item/info |
| ⚫︎ | Item |
✅ | - |
| ⚫︎ | Item |
✅ | /api/item/thumbnail |
| Item | |
✅ | /api/item/list |
| ⚫︎ | Item |
✅ | /api/item/moveToTrash |
| ⚫︎ | Item |
✅ | /api/item/refreshPalette |
| Item | |
✅ | /api/item/refreshThumbnail |
| Item | |
✅ | /api/item/update |
| ⚫︎ | Item |
✅ | /api/library/info |
| ⚫︎ | Library |
✅ | /api/library/history |
| Library | |
✅ | /api/library/switch |
| Library | |
✅ | /api/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 configurationRestart 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<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 }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<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 }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<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 }You don't have access to the filesystem.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for Clipkit — gives AI agents a video toolbox via the Clipkit schema.
DocBase MCP server for AI agents
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
MCP server for the FFmpeg Micro video transcoding API — create, monitor, download transcodes.
Related MCP Servers
- AlicenseAqualityAmaintenanceMCP Server that enables LLMs to interact with the local filesystem.131,923 npm21MIT
- FlicenseBqualityDmaintenanceA lightweight MCP server for basic file operations, enabling reading, writing, and listing files securely via the Model Context Protocol.31-
- AlicenseCqualityBmaintenanceA full-featured secure MCP server for local file system operations, with built-in image processing, OCR and media tools. Fully compliant with the official Model Context Protocol specification, offering standardized request/response schemas, large-file streaming I/O, multi-transport remote deployment, and comprehensive text search & replace functionality for LLM agent integration.22Apache 2.0
- AlicenseAqualityCmaintenanceLocal MCP server that compresses images and videos, extracts video frames, and prepares media for AI vision agents by returning file paths instead of inline base64.65 npm1MIT