F
license-
qualityD
maintenanceEnables integration with the Cliniko practice management system through MCP tools and resources. Supports patient management, appointment scheduling, and practice data access through natural language interactions.
Teepy MCP Server
Click on "Install 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., "@Teepy MCP ServerShow me unpaid invoices"
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.
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.
Related MCP server: PyerP MCP Server
What's mine, in full
Path | What it is |
| FastMCP entrypoint for the MCP server |
| Role-based access control layer over every MCP tool |
| Agent-facing business logic (customers, invoices, plannings, reminders, sessions) |
|
|
| Tests for the MCP tools and agent-facing functions, run against real business logic and a real database |
| Tests for the authentication endpoint |
| Includes commands I added: |
| MCP server port ( |
| Additional seed rows I added (synthetic dev data only, not real customer data) for realistic testing |
| 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
This server cannot be installed
Maintenance
–Maintainers
–Response time
–Release cycle
–Releases (12mo)
Commit activity
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-quality-maintenanceAn MCP server that enables LLM agents to interact with PyerP ERP systems via a REST API. It allows users to search, read, create, and update ERP records such as inventory, clients, and users using natural language.
- Alicense-qualityDmaintenanceEnables AI agents to interact with Odoo ERP to perform sales tasks such as searching clients and products, and creating and confirming quotations via the MCP protocol.2MIT
- AlicenseAqualityCmaintenanceMCP server for Tebra practice management that gives AI agents access to 45 tools for patients, appointments, billing, documents, and clinical data via SOAP and FHIR APIs.338451MIT
Related MCP Connectors
Self-hosted MCP gateway: turn any API, database or MCP server into AI connectors — no code.
Hosted MCP server exposing US hospital procedure cost data to AI assistants
Connect e-commerce and marketing data to AI assistants via MCP.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SajedehAdelia/Teepy-mcp-contribution'
If you have feedback or need assistance with the MCP directory API, please join our Discord server