Teepy MCP Server
Enables the Theopy AI assistant to interact with the Teepy pharmacy management ERP via the MCP protocol, with role-based access to customers, invoices, plannings, sessions, and reminders.
README
Teepy × Theopy — my contribution (sanitized extract)
This repository is a sanitized extract of Teepy, Kozea's proprietary pharmacy-management ERP (private repository, years of work by a full team, confidential to Kozea and its clients).
It exists to show, publicly and without breaching confidentiality, the code I personally wrote to connect Teepy to Theopy, an AI assistant I built as part of my RNCP39583 "Experte en Développement Logiciel" certification.
Every file and folder from the real Teepy repository is present here, at its real path, so the overall structure of the application is visible — but only the files I personally authored keep their real content. Everything else has been emptied (zero bytes) on purpose. This repo carries no git history from the original: only Teepy's own private repository has that.
Where my contribution sits in the architecture
┌─────────────────────────────────────────────────────-─────────────────┐
│ THEOPY (public, separate repo) │
│ AI assistant — Gemini / Ollama brain, chat UI, login │
└────────────────────────────────┬──────────────────────────────────────┘
│ MCP protocol over SSE
│ initialize → tools/list → tools/call
▼
┌──────────────────────────────────────────────────────────────────────┐
│ TEEPY (this repo — sanitized) │
│ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ mcp_server.py ★ MINE │ │
│ │ FastMCP entrypoint - boots the MCP server on :5001 │ │
│ └────────────────────────────┬─────────────────────────────────┘ │
│ │ │
│ ┌────────────────────────────▼───────────────────────────────--─┐ │
│ │ mcp_tools/ ★ MINE │ │
│ │ core.py - identity resolution via MCP `meta`, │ │
│ │ requires_role() access control │ │
│ │ invoices.py - factures (administrator/manager/commercial) │ │
│ │ customers.py - clients (administrator/manager/commercial) │ │
│ │ plannings.py - plannings (administrator/manager/operator) │ │
│ │ sessions.py - sessions (+ contractor) │ │
│ │ reminders.py - relances (administrator/manager/commercial) │ │
│ └────────────────────────────┬───────────────────────────────-──┘ │
│ │ calls agent_* functions │
│ ┌────────────────────────────▼──────────────────────────────-───┐ │
│ │ teepy/routes/theopy/ ★ MINE │ │
│ │ base.py, customer.py, invoice.py, planning.py, │ │
│ │ reminder.py, session.py │ │
│ │ → agent-facing business logic, wrapping Teepy's existing │ │
│ │ repositories/models │ │
│ └────────────────────────────┬─────────────────────────────-────┘ │
│ │ │
│ ┌────────────────────────────▼─────────────────────────-────────┐ │
│ │ teepy/routes/theopy_auth.py ★ MINE │ │
│ │ POST /api/theopy/authenticate │ │
│ └────────────────────────────┬───────────────────────────────-──┘ │
│ │ queries through │
│ ┌────────────────────────────▼─────────────────────────────-────┐ │
│ │ teepy/models/, teepy/repositories/, teepy/services/, │ │
│ │ teepy/routes/ (rest), teepy/templates/, teepy/static/, ... │ │
│ │ ○ PRE-EXISTING TEEPY │ │
│ │ proprietary ERP - content redacted in this repo │ │
│ └────────────────────────────┬───────────────────────────────-──┘ │
│ │ │
│ ┌────────────────────────────▼────────────────────────────-─────┐ │
│ │ PostgreSQL (Teepy production database) │ │
│ └────────────────────────────────────────────────────────────--─┘ │
└────────────────────────────────────────────────────────────────--────┘
★ MINE = full, real content, kept as-is.
○ PRE-EXISTING TEEPY = real file/folder structure preserved, content emptied.
What's mine, in full
| Path | What it is |
|---|---|
mcp_server.py |
FastMCP entrypoint for the MCP server |
mcp_tools/ (6 files) |
Role-based access control layer over every MCP tool |
teepy/routes/theopy/ (6 files) |
Agent-facing business logic (customers, invoices, plannings, reminders, sessions) |
teepy/routes/theopy_auth.py |
POST /api/theopy/authenticate - the endpoint Theopy's login calls |
test/theopy/ (7 files) |
Tests for the MCP tools and agent-facing functions, run against real business logic and a real database |
test/test_theopy_auth.py |
Tests for the authentication endpoint |
Makefile |
Includes commands I added: theopy-serve, mcp-inspect, install-db-test |
docker-compose.yml |
MCP server port (5001) and networking added for Theopy to reach Teepy |
sql/dev_data.sql |
Additional seed rows I added (synthetic dev data only, not real customer data) for realistic testing |
requirements/, uv.lock |
Dependency additions for the MCP integration |
teepy/__init__.py is intentionally emptied too, even though I added 2 lines
to it (registering the theopy_auth blueprint) - the file is overwhelmingly
pre-existing Teepy bootstrap code, not mine, so it follows the same rule as
everything else outside the list above.
Links
- Theopy (the AI assistant, fully public): https://github.com/SajedehAdelia/Theopy
- Teepy (the real repository, private - access on request): https://github.com/Kozea/teepy
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。