Skip to main content
Glama
Sign In
deenesjakoruzh
Eodly MCP server

Eodly MCP server

by layergen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Eodly MCP server

Read your team's sourced end-of-day reports and roster from any MCP client. Sign in with your Eodly account, or use an Eodly API key.

Sign in (OAuth): https://eodly.io/mcp (Streamable HTTP, nothing to install, works on every Eodly plan including the free one; a founder or lead approves the connection). With an API key: https://eodly.io/api/mcp (send Authorization: Bearer eodly_sk_...), or locally with npx @eodly/mcp (stdio) and EODLY_API_KEY set to a key created in the app under Settings, Developer, API keys. Tools: whoami, list_reports, get_report, list_team. MCP Apps: report tools render as an interactive card in hosts that support the UI extension. Read-only, and scoped to one organization.

Eodly sends founders and team leads one sourced report every evening: who shipped, who is silent, who is slipping. Your team checks in from Slack, Telegram or Discord, and Eodly weighs each claim against the real work in GitHub and Linear. This server exposes those reports to MCP clients such as Claude and Cursor, so you can ask an agent "who is slipping this week?" and have it pull the sourced answer.

Read-only. It cannot change anything in your workspace.

Install

Sign in with Eodly (recommended)

Add a custom connector with this URL. The client opens an Eodly page where you sign in and choose Allow; no key to create or paste:

https://eodly.io/mcp

Works in Claude, Gemini CLI and any client that supports MCP OAuth. Remove access any time in Eodly under Settings, Developer, Connected apps.

Hosted, with an API key

The same server for clients that take a header instead of a sign-in. Send the key as Authorization: Bearer eodly_sk_...:

https://eodly.io/api/mcp

Local (stdio)

npx @eodly/mcp

Related MCP server: linear-mcp

Configure

For the local server or the API-key endpoint, create an API key in the Eodly app under Settings → Developer → API keys, then add the server to your client.

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "eodly": {
      "command": "npx",
      "args": ["-y", "@eodly/mcp"],
      "env": { "EODLY_API_KEY": "eodly_sk_..." }
    }
  }
}

Cursor and other MCP clients use the same shape.

Tools

Tool

What it does

Scope

whoami

Identify the connected workspace and the scopes the connection holds

none

list_reports

Recent end-of-day report summaries, most recent first (limit, 1-50, default 14)

reports:read

get_report

Full structured content of one report by id

reports:read

list_team

The team roster: names, roles, departments

team:read

Interactive report card (MCP Apps)

list_reports and get_report ship an interactive view alongside their JSON. In a host that supports the MCP Apps UI extension (SEP-1865), the report renders as a card (who shipped, who's silent, who's slipping) instead of a wall of text. Hosts without the extension get the same JSON as before, so nothing breaks.

Resource

ui://eodly/report.html

MIME type

text/html;profile=mcp-app

Capability

io.modelcontextprotocol/ui

The view is fully self-contained (inline CSS and JS, no network access, no external assets) and declares an empty CSP allowlist. The hosted endpoints (https://eodly.io/mcp and https://eodly.io/api/mcp) serve the identical view.

Environment

Variable

Required

Default

EODLY_API_KEY

yes

none. An Eodly API key (eodly_sk_...)

EODLY_API_BASE

no

https://eodly.io/api/v1

Keys are organization-scoped and read-only. Revoke one at any time in the app.

Links

License

MIT. See LICENSE.

Available Tools

4 tools
get_reportAInspect

Get the full structured content of a single end-of-day report by id (use list_reports to find ids). Requires the reports:read scope.

Inputs: id (required).

list_reportsAInspect

List recent end-of-day report summaries for the organization, most recent first. Requires the reports:read scope.

Inputs: limit.

list_teamBInspect

List the team roster for the organization (names, roles, departments). Requires the team:read scope.

Inputs: no named parameters.

whoamiAInspect

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

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: whoami identifies the API key, list_reports and get_report separate listing from retrieval, and list_team targets the team roster. There is no meaningful overlap that would cause misselection.

    Naming Consistency4/5

    list_reports, get_report, and list_team follow a consistent verb_noun pattern. whoami is a common identity command but breaks the pattern, making it a minor deviation rather than a major inconsistency.

    Tool Count4/5

    Four tools is a reasonable, well-scoped set for a read-only reporting and team-access server. It is slightly lean, but each tool earns its place and there are no redundant entries.

    Completeness4/5

    The surface covers identity, report listing and retrieval, and team roster access, which is coherent for a read-only integration. Minor gaps exist, such as no team member detail lookup or report filtering, but core read workflows are covered.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers