Eodly MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EODLY_API_KEY | Yes | An Eodly API key (eodly_sk_...) created in the app under Settings, Developer, API keys. Required for authentication. | |
| EODLY_API_BASE | No | The base URL of the Eodly API. Defaults to https://eodly.io/api/v1. | https://eodly.io/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| extensions | {
"io.modelcontextprotocol/ui": {
"mimeTypes": [
"text/html;profile=mcp-app"
]
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Identify the API key: returns the Eodly organization it belongs to and the scopes it holds. |
| list_reportsA | List recent end-of-day report summaries for the organization, most recent first. Requires the reports:read scope. |
| get_reportA | 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. |
| list_teamB | List the team roster for the organization (names, roles, departments). Requires the team:read scope. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| eodly_report_view | Interactive end-of-day report card: who shipped, who's slipping, who's silent. |
TDQS
Scored across 4 tools
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.
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.
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.
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.