What is mcp-agileday AGENTS.md?

A repository instruction file for eficode/mcp-agileday, an MCP server that connects AI agents to Agileday employee and competence data. It records the project structure and important coding rules, including how its web server handles requests.

Use it to guide development in this Python server, especially when changing transport code, routes, or the separation between server logic and the web framework.

It prevents changes that conflict with the project's architecture, such as returning responses in a way that can crash its MCP endpoints.

mcp-agileday AGENTS.md — Instructions file by eficode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add instructions/eficode/mcp-agileday/agents-md

Clone the repo

git clone --depth 1 https://github.com/eficode/mcp-agileday

Made for: Codex, OpenCode.

Per session 1,028 This file is loaded in full into every session.

When invoked 1,028 The same file — it is already loaded in full.

Security scan A 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.01028	$0.01028
Opus 5	$0.00514	$0.00514
Sonnet 5	$0.00206	$0.00206
Haiku 4.5	$0.00103	$0.00103

Measured 2d ago against content hash b34e1a96ca77, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-agileday AGENTS.md scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

* **Mocking:** strictly mock `requests.get` using `unittest.mock.patch`. Never make real HTTP calls.

AGENTS.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AI Context & Coding Guidelines

This document provides context, architectural decisions, and coding standards for AI assistants (GitHub Copilot, Cursor, etc.) working on the mcp-agileday repository.

1. Project Overview

This is a Model Context Protocol (MCP) Server for the Agileday platform (SaaS).

Goal: Bridge Agileday's employee and competence data with LLMs.
Language: Python 3.11+
Transport: Supports both stdio (for local Docker/Desktop usage) and http-streamable (SSE) via Starlette/Uvicorn.

2. Architectural Patterns (CRITICAL)

The "Raw ASGI" Pattern

We use Starlette for routing, but we DO NOT use standard Starlette request/response handlers for the MCP endpoints.

Why: The mcp Python SDK writes responses directly to the ASGI send channel. If Starlette also tries to send a Response object, the server crashes with a "Double Response" runtime error.
Rule: When touching src/agileday_server.py transport layer, ensure the MCPHandler class uses the raw ASGI signature: async def __call__(self, scope, receive, send).
Do Not: Do not refactor the MCP routes to return standard starlette.responses.Response objects unless handling errors outside the SDK logic.

Logic Separation

To ensure testability, we separate Tool Definitions from Business Logic.

Pattern:
1. Define the tool in list_tools.
2. In call_tool, immediately delegate to a helper function (e.g., find_experts_logic, profile_logic).
3. The helper function performs the API call and string formatting.
Benefit: This allows unit tests (tests/test_agileday_server.py) to test logic without needing to mock the entire MCP server protocol.

3. Tech Stack & Dependencies

Core: mcp (Model Context Protocol SDK)
Web Server: starlette, uvicorn
HTTP Client: requests (for synchronous calls inside logic), httpx (for testing ASGI)
Testing: pytest

4. Testing Guidelines

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 93 lines · 1,028 tokens per session scan A b34e1a96ca77

Subscribe to this mod's changes

mcp-agileday AGENTS.md is an instructions file published in the GitHub repository eficode/mcp-agileday (1 stars, last pushed 8mo ago), licensed MIT. It adds 1,028 tokens to every session, about $0.0051 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

mcp-agileday AGENTS.md