1# Context7 for aiogram
2 
3Use Context7 when the task needs exact aiogram or aiogram_i18n API details instead of higher-level patterns.
4 
5## Install and availability
6 
7This skill does not install Context7 itself.
8 
9If the current Codex runtime already has the Context7 MCP server, use it directly.
10 
11If Context7 is missing in Codex, add an MCP entry like:
12 
13```toml
14[mcp_servers.context7]
15command = "npx"
16args = ["-y", "@upstash/context7-mcp"]
17```
18 
19Then restart Codex so the MCP tools are loaded.
20 
21## Recommended library IDs
22 
23For aiogram 3 projects, use:
24- `/aiogram/aiogram/v3.25.0` by default for aiogram 3 work
25- `/aiogram/aiogram/v3.26.0` only if the target project is already on that version or explicitly wants the latest aiogram 3 docs
26 
27For aiogram_i18n, use:
28- `/aiogram/i18n`
29 
30Avoid querying aiogram 4 docs for this skill unless the target project is explicitly on aiogram 4.
31 
32## Use Context7 for
33 
34- exact constructor parameters
35- available fields on Telegram objects
36- current examples for routers, dispatcher setup, keyboards, filters, and i18n middleware
37 
38## Practical lookup rules
39 
40- Pin aiogram queries to the closest aiogram 3 version that matches the repository.
41- Use `/aiogram/i18n` for aiogram_i18n runtime details.
42- If Context7 gives multiple plausible versions, prefer the project's installed version over the newest one.
43- If a Context7 answer conflicts with the repository's installed dependency version, trust the repository and re-query the matching version.
44- If Context7 does not cover a detail well enough, fall back to the package's upstream docs or source and say that you are doing so.
45