Skip to content
Eodly logo

Eodly MCP server

Which MCP servers are Eodly's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-09

← Back to Eodly

Whose server it is
  • Addresshttps://eodly.io/api/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on eodly.io when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools4
  • Server calls itselfeodly
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 542 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "Spot teammates who have gone silent or are slipping", the likely first call is list_reports.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer134 ms
  • Space in an agent's context≈ 302 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · Check daily what each teammate shipped, with GitHub and Linear proof
  • can do · Spot teammates who have gone silent or are slipping
  • not sure · Catch status claims that disagree with commits and issues

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-28
  • whoami

    Identify the connected Eodly workspace and the scopes this connection holds.

  • list_reports

    List recent end-of-day reports for the connected workspace, most recent first. Each report summarizes what got done, who is silent, and who is slipping. Requires the reports:read scope.

  • get_report

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

  • list_team

    List the team roster for the connected workspace (name, role, department, active). Personal contact details are omitted. Requires the team:read scope.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "eodly": {
      "type": "http",
      "url": "https://eodly.io/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http eodly https://eodly.io/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://eodly.io/api/mcp as a custom connector in the settings.

OpenAPI spec

5 paths, read 2026-10-09. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.