# Limits & Troubleshooting

Rate limits and fixes for common connection problems.

## Limits

| Limit | Value | Counted per | Applies to |
| --- | --- | --- | --- |
| Requests per minute | **30** | API key | All tools (channel About / videos / shorts get their own 100/min bucket, job-status polls their own 60/min bucket) |
| Requests per 24h | **1,000 / 2,000 / 4,000** (Starter / Professional / Ultimate) | Account | Search, channel-data, viral and workspace tools. Generation tools that spend credits don't count. |
| Max page number | **20** | — | Search tools |
| Max results per page | **50** | — | Search tools |
| Max results per query | **1,000** | — | Search tools (20 pages × 50 results) |
| Max concurrent jobs | **8 / 20 / 40** (Starter / Professional / Ultimate) | Account | TTS, scraper, video, other media jobs |
| Max concurrent image jobs | **10 / 25 / 50** (Starter / Professional / Ultimate) | Account | Image generation — separate bucket, doesn't count against the cap above |
| Max videos per retrieval | **100** | — | `get_youtube_video_data` |
| Max script length | **200,000 chars** | — | `generate_tts` |

**Per key or per account?** The per-minute limit is counted per API key. The 24h request cap and the concurrent-job caps are counted per account and shared by every key you own, so minting more keys does not raise them.

**Search query required:** All search tools (`search_shorts_channels`, `search_longform_channels`, `search_viral_videos`) require a search query. Browsing without a query is not supported.

## Troubleshooting

#### Server not appearing in Claude Code

1. Run `/mcp` in Claude Code to see connected servers

2. Check your `~/.claude.json` syntax with a JSON linter

3. Restart Claude Code completely

#### Server not appearing in Claude Desktop

1. Restart Claude Desktop completely (not just close the window)

2. Verify config file path is correct for your OS

3. Check JSON syntax — a trailing comma will break it

4. Look for the MCP indicator (hammer icon) in the chat input area

#### API key errors

1. Verify your API key at [algrow.online/settings/api-keys](https://algrow.online/settings/api-keys)

2. Make sure the key is in the `Authorization` header, not `args` or `env`

3. Check your subscription is active

**Still stuck?** Contact support at [support@algrow.online](mailto:support@algrow.online) or check the [REST API docs](/docs/api) to verify your API key works with direct HTTP requests.