SDK plan limits
The MCP Studio SDK has a Free plan and an SDK Pro plan.
| Audience | SDK buyers, platform admins, finance stakeholders |
|---|---|
| Prerequisites | Access to SDK pricing details and expected monthly MCP/server usage |
Current limits
SDK plan limits:
| Resource | Limit |
|---|---|
| Free plan MCP servers | 1 |
| SDK Pro MCP servers | 10 |
| Sources per server | 2 |
| MCP Studio free tier (standalone) | 3 servers, 50 calls/month |
| SDK Pro requests | 5,000 MCP requests/month |
| Indexed chunks per server | Up to 500K on Free, up to 3M on SDK Pro |
| SDK integrations per developer | No fixed cap |
| Widget configurations | No fixed cap |
MCP calls
An MCP call is a single request from an AI agent (Cursor, Claude Desktop, Windsurf, etc.) to an MCP server endpoint. Each tool invocation — for example, searching docs, extracting code, or asking a question — counts as one call.
Source limits
Each MCP server created by your end users can connect up to 2 included sources. Sources include websites, GitHub repos, documentation sites, API endpoints, PDFs, or other MCP servers. The same source guidelines from MCP Studio apply:
- Large websites can take longer indexing windows depending on crawl size and quality. Indexing continues in the background until the source completes or fails.
- Private GitHub repos require authentication from the end user.
- Source content is periodically refreshed. Unchanged pages skip re-embedding.
Source size
Beyond the source count, each MCP server has a cumulative allowance of indexed chunks shared across all of its sources. A chunk is a small passage of content stored so an AI agent can retrieve the exact part that answers a question.
| Plan | Indexed chunks per server |
|---|---|
| SDK Free | Up to 500K |
| SDK Pro | Up to 3M |
When a server reaches its allowance, indexing stops at the limit rather than failing. Everything already indexed stays queryable, and the end user is told that a larger allowance is available on a higher plan.
Limits reached
- Server limit: Users see a message that they've reached the maximum number of servers and can delete existing ones to create new ones.
- Source limit: After 2 included sources, each additional source is billed at $3.
- Source size limit: Indexing stops at the plan allowance; existing content stays queryable and upgrading raises the allowance.
- Call limit: Over-limit usage can continue through optional usage-based fees if configured.
Analytics dashboard subscriptions
New SDK developers get a 30-day trial with Core, Action, and Predictive included. After the trial:
- Core Analytics: $350/mo per MCP server
- Core + Action: $450/mo per MCP server
- Core + Action + Predictive: $550/mo per MCP server
You subscribe once at the integration level, and the tier is granted to every end user who deploys a server through your embed — they do not buy an MCP Studio analytics subscription separately.
Each tier also unlocks matching depth in your own business intelligence dashboard at Portal → Embed Usage:
| Tier | Portal insight added |
|---|---|
| Core | Adoption and activation rates, dormant servers, AI client mix, source reach |
| Action | Top questions across all end users, aggregate content gaps, ranked fixes |
| Predictive | Requests-to-answer efficiency, aggregate source grades, forecasts, at-risk integrations |
This is why SDK analytics is priced above MCP Studio standalone: it reports at the level of a business embedding the product, not a single server. See Analytics and observability.
Questions
For questions about limits, pricing, or enterprise needs, contact zair@appatools.com.