What authentication does the MangaDex API use?

The spec declares an HTTP bearer scheme, required by 87 of its 113 operations. MangaDex issues those tokens from its OAuth2 service on auth.mangadex.org, using a personal client id and secret; an access token lasts 15 minutes and is renewed with the refresh token. The older POST /auth/login and POST /auth/refresh operations are marked deprecated in the spec. The remaining 26 operations need no credential, including catalogue reads such as GET /manga and GET /chapter. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so the agent never sees it.

Can I read manga chapter images through the MangaDex API?

Yes, but image bytes are not served from api.mangadex.org. Call GET /at-home/server/{chapterId} to get a signed at-home server URL plus the chapter hash and page filenames; the client then fetches the image bytes from that at-home host. The acceptable use policy requires crediting MangaDex and the scanlation group when displaying chapters.

What are the rate limits for the MangaDex API?

MangaDex documents a global limit of approximately 5 requests per second per IP address for api.mangadex.org as a whole, plus per-endpoint limits such as 40 per minute on GET /at-home/server/{chapterId}. Rate-limited responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Retry-After, the last being the UNIX timestamp for the end of the current period. Once above the limit, requests to mangadex.org return HTTP 429 until your rate falls back in line, and persisting triggers a temporary IP ban.

How do I connect the MangaDex API to my agent through Jentic?

Install Jentic One on your own infrastructure, then tell your agent to add the MangaDex API from the Jentic API Directory. Your agent searches by intent, for example 'search the MangaDex catalogue', and Jentic returns the GET /manga operation with its query parameter schema (title, includedTags[], contentRating[], status[]) for the agent to execute. Get started with Jentic One, the self-hosted execution layer, at github.com/jentic/jentic-one.

Are commercial uses of the MangaDex API allowed?

No. MangaDex's acceptable use policy forbids running ads or paid services on apps and sites that consume the API, and requires crediting MangaDex and scanlation groups. Build personal, fan, or non-commercial tools only.

Is there a MangaDex MCP server?

You do not need an MCP server to give your agent the MangaDex API. Jentic connects it directly from the API Directory: import the API, store your credential once, and your agent calls it. Catalogue reads work unauthenticated, and the 87 operations that need a bearer token get it injected at call time by your own Jentic One instance.

Can I limit what my agent is allowed to do with the MangaDex API?

Yes. Because you run Jentic One yourself, your own rules decide which MangaDex operations the agent may call, so you scope access per operation. You can allow only catalogue reads such as searching manga with GET /manga, fetching a title with GET /manga/{id}, or getting its chapter aggregate with GET /manga/{id}/aggregate, and leave the other endpoints out. The agent can only reach the operations you picked, and your MangaDex credentials stay with your own instance rather than the agent.