TypeSpec based local TODO MCP Server

What is TypeSpec based local TODO MCP Server?

A local TODO list manager exposed as an MCP (Model Context Protocol) server, built using the TypeSpec MCP Server Demo Script. It is designed for developers using VS Code with GitHub Copilot Agent mode.

How to use TypeSpec based local TODO MCP Server?

Clone the repository, install dependencies (npm install), build the project (npm run build), then start the server (npm run mcp). In VS Code, configure .vscode/mcp.json to point to dist/src/mcp-server.js and start the server; then switch GitHub Copilot to Agent mode and ask it to list todos.

Key features of TypeSpec based local TODO MCP Server

• Fully vibecoded using TypeSpec MCP Server Demo Script
• Integrates with GitHub Copilot Agent mode in VS Code
• Exposes TODO management as MCP tools
• Built with Node.js (v22+) and TypeSpec
• Supports MCP Inspector for debugging

Use cases of TypeSpec based local TODO MCP Server

• Manage a local TODO list via natural language in VS Code
• Use GitHub Copilot Agent mode to add, list, or complete todos
• Develop and test MCP server workflows locally
• Inspect and debug the server with MCP Inspector

FAQ from TypeSpec based local TODO MCP Server

What prerequisites are needed?

VS Code, the GitHub Copilot and GitHub Copilot Chat extensions, and Node.js v22+.

How do I start the server?

Run npm run mcp from the project root after building. Optionally use npm run inspect for the MCP Inspector.

How do I use it with GitHub Copilot Agent mode?

Edit .vscode/mcp.json with the command node and args ["${workspaceFolder}/dist/src/mcp-server.js"], click “Start” in VS Code, then ask Copilot to perform TODO actions.

What transport does the server use?

It uses standard input/output (stdio) as the MCP transport, since the command runs a Node.js process.

Where does TODO data live?

The README does not specify; assume local storage (not defined further).