Project 5 MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Project 5 — First MCP Server
A task kitchen behind MCP, plus a Groq assistant that calls those tools through the protocol — not by importing the kitchen.
Project 4 imported tasks.py. Project 5 puts the same kind of functions in another layer: an MCP server. Any client (a test script, or Groq) can discover and call them.
You
→ assistant.py Groq loop + ALLOWED lock
→ Client(mcp) MCP client (official SDK v2)
→ server.py MCP server (MCPServer)
→ kitchen.py
→ data/tasks.jsonRelated repos:
What you will learn
What MCP is (a standard plug for tools)
MCP server vs MCP client
Why the cook (
kitchen.py) and the plug (server.py) are separate filesOfficial Python SDK v2:
MCPServer, not the oldFastMCPimportTool discovery:
list_tools()then Groq schemasPermissions still live in Python (
ALLOWED)
Related MCP server: Task Manager MCP Server
What this is not
Not Gmail / Calendar
Not multiple agents (that is Project 6)
Not OpenClaw
Not Streamlit (optional later)
MCP 2.x note
pip install mcp now installs 2.x.
Wrong (v1): from mcp.server.fastmcp import FastMCP
Right (v2): from mcp.server import MCPServer@mcp.tool() is unchanged. Pin mcp<2 only if you must run old tutorials.
Requirements
Python 3.12+
Groq key in
.envasGROQ_API_KEY(forassistant.pyonly)Packages:
mcp[cli],openai,python-dotenv
Setup
cd ~/Desktop/projects/project-5-mcp-server
python3.12 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
cp ~/Desktop/projects/project-1-first-agent/.env ..env is required only for the Groq assistant. kitchen.py and client.py do not need a key.
Never commit .env or data/.
Project structure
project-5-mcp-server/
├── kitchen.py # cook — add / list / complete, writes JSON
├── server.py # plug — MCPServer + @mcp.tool wrappers
├── client.py # test waiter — no Groq
├── assistant.py # talking waiter — Groq + MCP
├── requirements.txt
├── .gitignore
├── .env # local only
└── data/ # local only
└── tasks.jsonHow to think about the files
File | Room | Needs Groq? |
| Cook | No |
| Plug / menu | No |
| Silent waiter | No |
| Talking waiter | Yes |
If the cook is broken, fix kitchen.py.
If the menu is wrong, fix server.py.
If Groq never calls a tool, fix the prompt / schemas.
Do not debug all three at once.
Run tests in order
1. Kitchen only
python kitchen.py
cat data/tasks.json2. Silent client (starts the server in-process)
python client.pyYou should see tool names and a new task in data/tasks.json.
Do not leave python server.py running in another window for these tests. Client(mcp) talks to the server object in the same process. python server.py alone waits on stdio; Control+C prints a KeyboardInterrupt — that is normal.
3. Groq assistant
python assistant.pyAdd a task to buy milk
List my tasks
Complete task 3Look for:
[loop] discovered tools: ['tool_add_task', 'tool_list_tasks', 'tool_complete_task']
[loop] round 1: tool_add_task(...)
[loop] result: ...INFO HTTP Request ... groq.com lines are just API traffic.
Environment
Name | Required for | Purpose |
|
| Model calls |
API base: https://api.groq.com/openai/v1
Model: openai/gpt-oss-20b
Security
Key only in
.envTasks only under
data/.gitignorelists.env,.venv/,data/ALLOWEDinassistant.pyis the lock. The model is not.This server is local and in-process. Do not expose it on the public internet in this slice.
Troubleshooting
Symptom | Cause | Fix |
| SDK v2 rename |
|
| New venv |
|
Missing credentials | No | Copy |
| You stopped stdio | Expected |
Model talks, no | Tool not chosen | Stronger system prompt |
| Name not in | Add the exact MCP tool name |
Kitchen works, assistant does not write JSON | Tool never called | Read |
GitHub
Public repo name: project-5-mcp-server
Push code only. Never push .env or data/tasks.json.
Next
Project 6: more than one agent sharing this (or another) MCP server.
Do not add email here. The plug is the lesson.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Local-first task manager: create, edit, and complete tasks, projects, and checklists via MCP.
Headless task management for bots, apps and AI agents. Remote MCP server, OAuth or access token.
MCP server for Google Tasks: review, plan and tidy your tasks by asking. Deletes always ask first.
Create, list, and complete todo items through MCP.
Related MCP Servers
- AlicenseAqualityDmaintenanceModel Context Protocol server for Task Management. This allows Claude Desktop (or any MCP client) to manage and execute tasks in a queue-based system.10689 npm216MIT
- FlicenseCqualityDmaintenanceEnables local task management through the Model Context Protocol with tools for creating, updating, and deleting tasks. It also provides read-only resources for viewing task summaries and full task lists.4-
- AlicenseNot gradedqualityCmaintenanceA lightweight task management MCP server that enables CRUD operations on tasks stored in a single JSON file, including listing, creating, updating progress, and setting priorities.ISC
- AlicenseBqualityDmaintenanceEnables task management via MCP tools for creating, listing, updating, completing, and deleting tasks with JSON file storage.6ISC