Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Server Starter Template greet John"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Part of NextFlows Academy — the free cohort program Building an MCP for an AI Engine.
Clone this repo to build your Model Context Protocol (MCP) server in TypeScript. By Demo Day you will ship a public GitHub repo with real tools, Zod validation, docs, and a live demo — the same path used in the free NextFlows Academy cohort.
Program hub: nextflows.ai/academy
Full program page (in this repo): docs/PROGRAM.md
Apply: Cohort application
NextFlows Academy runs structured, cohort-based programs with live sessions, mentor support, and a real project you ship by the end.
This repository belongs to:
Program | Building an MCP for an AI Engine |
Audience | 4th & 5th year CS / CE students |
Duration | 6 weeks |
Format | Cohort + project |
Price | Free |
Level | Intermediate |
Outcome | Shipped MCP server on GitHub |
Schedule | Wed & Sat online 1:30–3:30 PM + Monday on-site workshop days |
You go from “what’s an MCP?” to a working MCP server connected to an AI engine (for example Claude), fully documented, and live on GitHub.
See docs/PROGRAM.md for outcomes, weekly plan, starter projects, and who it’s for.
Related MCP server: Notes Manager
Path | Purpose |
| MCP server + stdio transport |
| One register helper per tool |
| Zod input contracts (with |
| Sample JSON args for Inspector |
| Full NextFlows Academy program page |
| Full Week 2 step-by-step plan |
| 6-week overview |
| Week 2 project choice template |
| Week 2 design doc template |
Week 1 is already wired: a working greet tool so you can open Inspector on day one.
Week 2 examples included: stub tools for Notes & FAQ Search (search_notes, list_notes, add_note). Enable them when you pick that starter (or copy the pattern for your own idea).
Node.js 20+ (node -v)
npm (npm -v)
Git + a GitHub account
Cursor or VS Code
git clone <YOUR_FORK_OR_ORG_URL>/MCPRepo.git
cd MCPRepo
npm install
npm run inspectIn the Inspector browser tab:
Click Connect
Open Tools
Select greet and put Alex in the name field (see examples/greet.json for the full args shape)
Try invalid input (empty name) and confirm Zod rejects it
To run the server alone (waits on stdin):
npm run devImportant: log only with
console.error. Never useconsole.log— stdout is reserved for the MCP protocol.
Week 2 is design-first. Follow docs/WEEK-2.md.
Useful scripts:
Script | What it does |
| Start the MCP server on stdio (stays alive; stop with Ctrl+C) |
| Same as |
| Open MCP Inspector against this server |
TypeScript via tsx (no build step early on)
Official MCP TypeScript SDK (@modelcontextprotocol/server)
Zod for tool inputSchema
MCP Inspector for local testing
stdio transport for Claude Desktop / Cursor demos
Week | Focus |
1 | Set up & first MCP tool ( |
2 | Design your own tools → see |
3 | Connect tools to real data |
4 | Make it safe & reliable |
5 | Test & write docs people can follow |
6 | Ship on GitHub & Demo Day |
Full program details: docs/PROGRAM.md
Notes & FAQ Search — fully offline (example stubs included)
Personal Expense Tracker — summarize spending from a spreadsheet
To-Do List — create / list / complete tasks
Weather Briefing — free API (e.g. Open-Meteo), no paid keys
Quote of the Day — simple offline or public API
Advanced ideas (repo health, course planner, job tracker) need mentor approval before you expand scope.
MCPRepo/
├── docs/
│ ├── PROGRAM.md
│ ├── CURRICULUM.md
│ ├── WEEK-2.md
│ ├── project-choice.md
│ └── design.md
├── examples/
│ └── <tool_name>.json
├── src/
│ ├── index.ts
│ ├── schemas/
│ └── tools/
├── package.json
└── README.mdOne job per tool; use verb_noun names (search_notes, add_expense)
Write descriptions for the model, not only for humans
Every Zod field needs .describe(...)
Prefer small focused tools over one mega-tool with an action enum
Avoid paid APIs / OAuth-heavy projects in Weeks 1–2
MIT — built for NextFlows Academy students.
Return a short greeting for a person. Use this to verify the MCP server is running.
Inputs: name (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The purpose is clear and singular.
There is only one tool, so there is no inconsistency. The name 'greet' follows a simple verb pattern.
Tool count is 1, which is too few for a meaningful server. Even as a starter template, it lacks the typical minimal set (e.g., a few related operations).
The server has only a single greeting tool, which does not cover any functional domain. There are obvious gaps like any actual operations or data management.
Kickstart development with a customizable TypeScript template featuring sample tools for greeting,…
A simple Typescript MCP server built using the official MCP Typescript SDK and smithery/cli. This…
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
A TypeScript MCP server for Home Assistant, enabling programmatic management of entities, automati…
