eagle

This Eagle MCP Server acts as a bridge between the Eagle application and the MCP ecosystem, exposing a set of programmable endpoints that Eagle can call to manage files, folders, items, and library data. The server implements a collection of API endpoints described in the Tools table, enabling operations such as fetching application info, creating and renaming folders, listing items, adding items from URLs or paths, updating items, and retrieving library information. By running the server locally and pointing Eagle at it, you unlock programmatic data flows and automation capabilities within your Eagle workflow. To use it, ensure Eagle is running and connect to the MCP server at http://localhost:8000/mcp (the default port used in the example configuration). The Tools section documents which endpoints are available, their operation IDs, and whether they’re enabled by default. You can enable additional tools by removing the Disabled tag in the source configuration and restarting the server. See the provided API docs at the MCP Server API docs link for detailed request/response formats and examples.

Prerequisites:

• Python 3.13
• uv (Python package) installed in your environment

Installation steps:

1. Set up a Python virtual environment (optional but recommended): python3 -m venv venv source venv/bin/activate # macOS/Linux .\venv\Scripts\activate # Windows

2. Install the uv package which provides the MCP server runtime: pip install uv

3. Ensure Eagle is installed and running (as per Eagle documentation).

4. Start the MCP server: uv run main.py

5. Verify the server is up by visiting http://localhost:8000/redoc or the MCP API docs linked in the README.

Tips and common issues:

• The MCP server exposes a collection of endpoints; some tools may be disabled by default. To enable them, locate the tool definition in the source code and remove the tags ["Disabled"], then restart the server.
• Default port for the example configuration is 8000. If you change ports, update the client Eagle configuration accordingly.
• If you want to use the stdio transport (instead of HTTP), configure the mcpServers entry with command and args as shown in the README under the stdio transport example.
• Ensure Eagle is running before starting the MCP server; otherwise, initial connections may fail.
• Use the provided MCP Server API docs for exact request payloads, required fields, and response shapes.