Tutorials
Each tutorial takes you from an empty wizard to a working MCP endpoint connected to your AI client. They differ in which sources you add, which tools you turn on, and what you do with the result.
Build absolutely anything...with the right context.
| Audience | Anyone creating their first MCP server |
|---|---|
| Prerequisites | An MCP Studio account and at least one source URL |
Pick a starting point
| Tutorial | For | You end up with |
|---|---|---|
| Build a full-stack context server | Developers | One server holding every docs site and repo in your architecture, wired into your IDE |
| Your first context server | Vibe coders | A server built from the docs you already keep in browser tabs, in about two minutes |
| A docs MCP for writers | Technical writers and docs engineers | Your documentation as a measurable MCP server, with a content-gap report |
These are not sequential. Start with whichever matches how you work.
What every tutorial has in common
The wizard is the same in all three cases. What changes is the judgement: which sources are worth indexing for your goal, and which of the ten tools earn their place.
Start narrow
Whichever tutorial you follow, resist the urge to add every source you can think of on the first pass. Retrieval quality goes down as unrelated material goes up. Three well-chosen sources beat ten sprawling ones, and you can always add more later.
Related
- Create an MCP server — the reference walkthrough of the wizard
- Add sources — source types, crawl limits, and private repos
- Choose tools — what each of the ten tools does
- Connect to AI clients — Cursor, Claude Desktop, and Windsurf