Installing the server

The MCP server is published as @agelo-platform/mcp on npm.

Install

npm install -g @agelo-platform/mcp

This puts the agelo-mcp binary on your PATH. To check:

agelo-mcp --version

Configure

The server reads two environment variables:

Variable	Purpose
AGELO_PUBLIC_URL	Base URL of your agelo-server install (e.g. https://agelo.example.com).
AGELO_API_KEY	The team-scoped API key the server should use. Issue one from Settings → API keys.

You can also pass them on the command line: agelo-mcp --url https://… --api-key AGK_….

Verify

Run the server in stdio mode and make a single tool call to make sure auth works:

agelo-mcp --transport stdio

Then send the standard MCP initialize + tools/list JSON-RPC payloads on stdin. If you get a tool list back, you’re set.

For HTTP mode:

agelo-mcp --transport http --port 8765

Then curl http://localhost:8765/mcp/tools/list (the path is the MCP-standard surface).

Auto-start

Most desktop clients spawn the server themselves — see Claude Desktop for the config file format. For a long-running HTTP deployment, run it under a process manager (systemd, pm2, Docker). It exits non-zero on auth failure; supervise accordingly.

Updating

npm install -g @agelo-platform/mcp@latest

The MCP tool surface is versioned alongside the platform: agelo-mcp 0.4.x talks to agelo-server 0.4.x. Mismatched majors will refuse to start.