Patient Search & Create Tasks MCP Server

Created By
Flight-Healtha year ago
MCP server for searching patients and creating tasks in Flight Health Atlas system.
Overview

what is Patient Search & Create Tasks MCP Server?

This project provides a Model Context Protocol (MCP) server for searching patients in the Flight Health Atlas system and creating new tasks.

how to use Patient Search & Create Tasks MCP Server?

To use the MCP server, clone the repository, install dependencies, update your credentials, and build the server. You can then use the available tools to search for patients or create tasks.

key features of Patient Search & Create Tasks MCP Server?

  • V2 Server using Puppeteer for advanced web automation and reliable login handling.
  • Tools for searching patients and creating tasks with detailed parameters.

use cases of Patient Search & Create Tasks MCP Server?

  1. Searching for patient information in the Flight Health Atlas system.
  2. Creating new tasks related to patient care or management.
  3. Automating patient search processes in healthcare applications.

FAQ from Patient Search & Create Tasks MCP Server?

  • What are the prerequisites for using the MCP server?

You need Node.js 18 or higher and a package manager like npm or yarn.

  • How do I update my credentials?

Update the LOGIN_CREDENTIALS in the auth.ts file with your email and password.

  • What should I do if the browser launch fails?

Ensure you have sufficient system resources and try running with the --no-sandbox flag.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Flight-Health
Star
0
Language
TypeScript
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