METAESTETICS-ClinicManagement-Platform-By-Blackcode

Created By
AndyLeong33deva year ago
This repository contains all source code for METAESTETICS(Firebase API server, Clinic admin website, patient app in React Native, Doctor app in React native). This will be a good example using MCPs
Overview

what is METAESTETICS?

METAESTETICS is a comprehensive clinic management platform that includes a Firebase API server, a clinic admin website, a patient app built with React Native, and a doctor app also in React Native.

how to use METAESTETICS?

To use METAESTETICS, developers can clone the repository from GitHub, set up the Firebase API server, and deploy the admin and patient applications for managing clinic operations.

key features of METAESTETICS?

  • Integrated Firebase API for backend services
  • Admin dashboard for clinic management
  • Patient and doctor mobile applications for seamless communication
  • Example implementation of MCPs (Mobile Clinic Platforms)

use cases of METAESTETICS?

  1. Managing patient appointments and records in clinics.
  2. Facilitating communication between doctors and patients through mobile apps.
  3. Streamlining clinic operations with an admin dashboard.

FAQ from METAESTETICS?

  • Is METAESTETICS suitable for all types of clinics?

Yes! METAESTETICS can be customized to fit various clinic types and sizes.

  • What technologies are used in METAESTETICS?

METAESTETICS uses Firebase for backend services and React Native for mobile applications.

  • Is there documentation available for METAESTETICS?

Yes! Documentation is provided in the repository to help developers set up and customize the platform.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AndyLeong33dev
Star
0
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago