What are Scoped MCPs?
Instead of using Nia’s full MCP server with all tools, you can generate a specialized MCP server that:- Focuses on a single source — One framework, one documentation site, one research paper
- Has fewer tools — Only the tools relevant to that source
- Reduces context noise — Your agent sees only what’s relevant
How It Works
1
Pick a Pre-indexed Source
Go to app.trynia.ai and browse the Global Sources. Find the documentation, repository, or paper you want.
2
Generate Scoped MCP
Click on the source and select “Create Scoped MCP”. Nia generates a dedicated MCP configuration for that source.
3
Add to Your IDE
Copy the generated configuration into your IDE’s MCP settings. The scoped MCP connects only to that specific knowledge source.
Example: Vercel AI SDK Scoped MCP
Instead of querying all of Nia’s knowledge, create an MCP that only knows about the Vercel AI SDK:source parameter is URL-encoded. For https://sdk.vercel.ai/docs, it becomes https%3A%2F%2Fsdk.vercel.ai%2Fdocs.
Now your agent has access to Vercel AI SDK documentation without being distracted by other sources.
Popular Scoped MCPs
Some commonly requested scoped servers:| Source | Use Case |
|---|---|
| Next.js | React framework with App Router, Server Components |
| BetterAuth | Authentication library for TypeScript |
| FastAPI | Python web framework |
| Tailwind CSS | Utility-first CSS framework |
| Prisma | TypeScript ORM |
| LangChain | LLM orchestration framework |
Any pre-indexed source can become a scoped MCP. If it’s in Global Sources, you can create a focused server for it.
When to Use Scoped MCPs
Use Scoped MCP When
- Working on a single-framework project
- Want minimal tool clutter
- Need faster, more focused responses
- Prefer explicit control over context
Use Full Nia MCP When
- Working across multiple technologies
- Need indexing and research tools
- Want to search your own repos/docs
- Building with diverse dependencies
Multiple Scoped MCPs
You can run multiple scoped MCPs simultaneously:Scoped vs. Subscribed Sources
| Scoped MCP | Subscribed Source (Full MCP) |
|---|---|
| Dedicated MCP server per source | Single MCP, multiple sources |
| Separate tool namespace | Shared tools query all subscribed |
| Best for focused workflows | Best for cross-source queries |
| Multiple MCP configs needed | One config, manage sources in UI |

