How no-code MCP works
Build absolutely anything...with the right context.
When you create an MCP server through the wizard, MCP Studio turns source content into searchable context and returns it through the Model Context Protocol (MCP).
| Audience | Technical evaluators, platform teams, developers |
|---|---|
| Prerequisites | Understanding of MCP clients and access to source content you want to index |
Context pipeline
- Crawl: MCP Studio visits your sources and extracts content from web pages, GitHub files, PDFs, and federated MCP sources.
- Index: Content is organised into passages that preserve headings and code blocks, then indexed for search. Indexing runs in the background and resumes on its own, so large sources finish reliably.
- Search: Both keyword and meaning-based matching are used to return the passages that best answer the agent's query, favouring your current documentation.
- Deliver: The MCP runtime returns results to any connected MCP client, such as Cursor, Claude Desktop, or Windsurf.
- Measure: Telemetry powers Core, Action, and Predictive dashboards so you can see which context creates value.
Indexing
After you deploy, sources begin indexing automatically as background jobs. You do not need to keep the dashboard open. The MCP server is usable during indexing because it uses live fetching as a fallback until indexing completes.
About indexing times
- 1-3 sources: Usually 1-6 minutes, based on source size and accessibility.
- Large docs sites: Continue in the background. The dashboard shows percent complete, pages indexed, and a stalled warning if progress stops.
- GitHub repos: Often index faster for markdown-heavy content and slower for large codebases.
- Sources auto-refresh daily at 7:00 AM Central US time. Content that has not changed is skipped.
- You can manually refresh any source from the dashboard, including while it is already indexing.
- Each source supports up to 5,000 pages, and a run that fails leaves your last good index intact.
MCP protocol
Your server exposes two transport options:
| Transport | Endpoint | Use case |
|---|---|---|
| Streamable HTTP (default) | POST /api/mcp/{slug} | Recommended for new MCP client integrations |
| SSE (compatibility) | GET /api/mcp/{slug}/sse | Legacy clients that still require SSE |
Both follow the Model Context Protocol specification, so your server works with any compliant client.
Analytics loop
Analytics help you answer product and operations questions:
- Which sources do AI agents use most often?
- Which exact passages answer user questions?
- Which content gaps prevent useful answers?
- Which sources should you improve first?