The `agentdrop-mcp-server` package provides the Model Context Protocol (MCP) server for the AgentDrop ecosystem, facilitating secure, structured communication and tool access for AI agents. It acts as a core infrastructure component, enabling agents to send and receive files, manage connections, and execute predefined tools like `send_file` and `download_transfer` without needing to implement underlying cryptographic details (X25519/AES-256-GCM). The current stable version is 0.2.22, indicating an active development phase, though release cadence is not explicitly stated. Key differentiators include its tight integration with AgentDrop for AI agent communication, automatic encryption/decryption of file transfers, and self-updating agent profile retrieval, positioning it as a dedicated agent communication backbone rather than a general-purpose server.
npm install agentdrop-mcp-serverVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to install the `agentdrop-mcp-server` globally and how to configure an MCP client to launch it with necessary environment variables.
Always use the provided MCP tools like `download_transfer` for file operations. Trust the built-in cryptography.
Regularly check the official documentation at `docs.agent-drop.com` for release notes and migration guides before updating to new versions.
Ensure your Node.js environment is updated to version 18.0.0 or later. Use `nvm` or similar tools to manage Node.js versions if needed.
Verify that `AGENTDROP_API_KEY`, `AGENTDROP_AGENT_ID`, and `AGENTDROP_AGENT_UUID` environment variables are correctly set and correspond to an active AgentDrop agent with appropriate API access.
Ensure you have installed the package globally using `npm install -g agentdrop-mcp-server` or that `npx` is correctly configured in your PATH.
Set all required environment variables in your MCP client's configuration or directly in your shell before launching the server. For example: `export AGENTDROP_API_KEY=agd_your_key`.
Upgrade your Node.js installation to version 18.0.0 or higher. Using `nvm install 18 && nvm use 18` is recommended for managing Node.js versions.
No dependency data recorded yet.