Eodly MCP server is used to read Eodly team's sourced daily work reports and member roster from any MCP client.
Purpose
Eodly sends a sourced report to founders and team leads every night: who completed work, who stayed silent, who is falling behind. Team members check in via Slack, Telegram, or Discord, and Eodly verifies each claim against actual work in GitHub and Linear. This server exposes these reports to MCP clients such as Claude and Cursor, so you can ask the agent "Who is falling behind this week?" and have it pull a source-backed answer.
Main capabilities
- Provides four tools: whoami, list_reports, get_report, list_team.
- MCP Apps: in hosts that support UI extensions, report tools render as interactive cards.
- Read-only, and scoped to one organization. Cannot change anything in the workspace.
Usage
Sign in with Eodly (recommended)
Add a custom connector using this URL. The client opens an Eodly page where you sign in and select "Allow"; no need to create or paste a key:
https://eodly.io/mcp
(Streamable HTTP, no installation required, works with all Eodly plans, including the free plan; connection is approved by a founder or lead.)
Works with Claude, Gemini CLI, and any client that supports MCP OAuth. Access can be removed at any time in Eodly's "Settings → Developers → Connected apps".
Hosted method, using an API key
For clients that use request headers instead of sign-in, use the same server. Send the key as Authorization: Bearer eodly_sk_...:
https://eodly.io/api/mcp
For a local server or API key endpoint, create an API key in the Eodly app under "Settings → Developers → API keys", then add the server to your client.
Claude Desktop (claude_desktop_config.json):
For local use, use npx @eodly/mcp (stdio), and set EODLY_API_KEY to the key created in the app.
Cursor and other MCP clients use the same configuration format.
Interactive report cards (MCP Apps)
list_reports and get_report return JSON along with an interactive view. In hosts that support the MCP Apps UI extension (SEP-1865), reports render as a card (who completed work, who stayed silent, who is falling behind) instead of a large block of text. Hosts that do not support the extension receive the same JSON as before, so there is no failure.
The view is fully self-contained (inline CSS and JS, no network access, no external resources), and declares an empty CSP allowlist. Hosted endpoints (https://eodly.io/mcp and https://eodly.io/api/mcp）提供相同的视图。
Keys are scoped to the organization and are read-only. They can be revoked at any time in the app.
Use cases
- A team lead or founder wants a quick view of the team's daily work progress, silent members, and who is falling behind.
- Query team reports in natural language in MCP clients such as Claude and Cursor.
- Need to integrate Eodly reports into agent workflows that support MCP.
Limitations
- Read-only, cannot modify anything in the workspace.
- Scoped to one organization.
- Interactive cards render only in hosts that support the MCP Apps UI extension (SEP-1865).
- Using the API key method requires first creating a key in the Eodly app.
Developer and API documentation
An OpenAPI specification is provided.
License
MIT. See LICENSE.