Skip to main content

"At capacity" errors — what they mean and what to do

Why you might see a 503/at_capacity response, and what to do about it.

Written by Bryan Fawcett

Nyuchi MCP for YNAB runs each connected person's requests on an isolated container so one person's usage can't slow down anyone else's. There's a cap on how many of those can run at the same time — if every slot is busy when your request arrives, you'll get a response like:

{"error": "at_capacity", "hint": "Nyuchi MCP for YNAB is at capacity for concurrent users right now. Please try again in a minute or two..."}

Why this happens

This is a capacity limit, not an error in your setup or an account-specific block — it means the service is unusually busy right now. It resolves itself as other people's sessions finish and free up a slot.

What to do

  • Wait a minute or two and try again — most of the time this clears on its own quickly.

  • Check the project page for any known ongoing issue.

  • If it persists for more than a few minutes, let us know via the chat bubble or email below — that's a signal we may need to raise the capacity limit.

Still stuck?

Use the chat bubble in the corner of ynab.nyuchi.com, or email [email protected].

Did this answer your question?