omcp

Created By
fastomopa year ago
Model Context Protocol Server for the Observational Medical Outcomes Partnership (OMOP) Common Data Model
Overview

What is OMCP?

OMCP is a Model Context Protocol Server designed for the Observational Medical Outcomes Partnership (OMOP) Common Data Model, enabling AI models to interact with healthcare data in a standardized manner.

How to use OMCP?

To use OMCP, set up the server and configure it to connect with your healthcare data stored in the OMOP format. You can then query and analyze the data through the provided API.

Key features of OMCP?

  • Standardized interface for querying OMOP formatted healthcare data.
  • Integration capabilities with various AI models for data analysis.
  • Comprehensive documentation for easy setup and usage.

Use cases of OMCP?

  1. Analyzing patient outcomes using AI models.
  2. Conducting research on healthcare data trends.
  3. Facilitating data-driven decision-making in healthcare organizations.

FAQ from OMCP?

  • What is the OMOP Common Data Model?

The OMOP Common Data Model is a standardized framework for organizing healthcare data to enable efficient analysis and research.

  • Is OMCP open-source?

Yes! OMCP is available on GitHub under the MIT license.

  • What programming language is OMCP built with?

OMCP is developed using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fastomop
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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