eodly-mcp

Read your team's end-of-day reports and roster from Eodly.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
63%
Naming quality
95%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~282Tokens (tool definitions)
~318 BTypical response size
Minimal attention impact (0.22% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "eodly-mcp": {
      "command": "npx",
      "args": [
        "@eodly/mcp"
      ]
    }
  }
}

Runnable packages

npm@eodly/mcp0.2.1stdio

Remote endpoints

https://eodly.io/api/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪whoami

Identify the calling Eodly API key: the organization it belongs to and the scopes it holds.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢list_reports(limit)

List recent end-of-day reports for the key's organization, most recent first. Each report summarizes who shipped, who is silent, and who is slipping. Requires the reports:read scope.

Input Schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "description": "Max reports to return (default 14)."
    }
  },
  "additionalProperties": false
}
🟢get_report(id)

Get the full structured content of one end-of-day report by id (KPI status, shipped, silent, slipping, blockers). Requires the reports:read scope.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "The report UUID."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}
🟢list_team

List the team roster for the key's organization (name, role, department, active). Personal contact details are omitted. Requires the team:read scope.

Input Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools
verifiedversion not recorded4 tools