Medical MCP Server

Medical MCP Postmessage Application

Current State: Ozwell Integration Status

❌ No Real Ozwell API Integration

Currently, this application does NOT have actual Ozwell API integration. What you have is:

Local simulation only - All "Ozwell" functionality is mocked
Missing API calls - No HTTP requests to real Ozwell endpoints
Incomplete implementation - Several methods are called but not implemented

🏗️ What Exists (Local Simulation)

✅ MCP Server with medical tools (add medication, allergies, etc.)
✅ PostMessage communication between iframe and parent
✅ Local medical data management
✅ Chat UI interface
✅ Tool execution framework

🚫 What's Missing for Real Ozwell Integration

1. API Configuration

// You need real Ozwell API credentials
const ozwellConfig = {
    apiUrl: 'https://api.ozwell.com', // Real Ozwell API URL
    apiKey: 'your-actual-api-key',    // Real API key
    model: 'ozwell-medical-model'     // Real model name
};

2. API Implementation

The following methods in ozwell-integration.js need real implementation:

generateResponse() - Make HTTP calls to Ozwell chat API
parseToolCalls() - Parse Ozwell's tool call format
formatResponse() - Format Ozwell responses for display

3. Authentication

Obtain Ozwell API credentials
Implement proper API authentication
Handle API rate limits and errors

4. Medical Model Integration

Configure Ozwell medical model
Set up medical-specific prompts and context
Implement medical safety guardrails

🔧 How to Add Real Ozwell Integration

Step 1: Get Ozwell API Access

Sign up for Ozwell API access
Obtain API key and model information
Review Ozwell's medical API documentation

Step 2: Update Configuration

// Update agent-iframe/ozwell-config.js
export const OzwellConfig = {
    apiUrl: 'https://api.ozwell.com',  // Real URL
    apiKey: 'your-real-api-key',       // Real API key
    model: 'ozwell-medical-v1'         // Real model name
};

Step 3: Implement API Calls

The ozwell-integration.js file has been updated with a template for real API integration. You need to:

Replace the API URL and authentication
Implement proper error handling
Add medical context to API calls
Handle streaming responses

Step 4: Test Integration

# Start the development server
npm run dev

# Test API calls in browser console

📁 Current Architecture

agent-iframe/               # Medical AI chat interface
├── ozwell-integration.js  # Ozwell API integration (needs real implementation)
├── ozwell-config.js       # API configuration
├── medical-mcp-server.js  # MCP server with medical tools
├── mcp-client.js          # Chat client and UI management
└── index.html             # Chat interface

parent-app/                # Medical practice simulation
├── medical-data.js        # Local medical data management
├── ozwell-agent-sim.js    # Iframe management and communication
└── index.html             # Practice management interface

🚀 To Run Current Application

# Install dependencies
npm install

# Start development server (Vite)
npm run dev

# Or use http-server for simple static serving
npx http-server -p 8080 -c-1

Access:

Parent app: http://localhost:3000/parent-app/
Agent iframe: http://localhost:3000/agent-iframe/

⚠️ Important Notes

This is currently a proof-of-concept with local simulation only
No real AI or Ozwell integration exists yet
Medical data is simulated for demonstration purposes
Not suitable for production medical use without proper integration

🎯 Next Steps

Obtain Ozwell API credentials
Implement real API calls in ozwell-integration.js
Add proper error handling and rate limiting
Test with real medical scenarios
Add medical safety and compliance features

This server cannot be installed

security - not tested

license - not found

quality - not tested

How are these scores calculated?

hybrid server

The server is able to function both locally and remotely, depending on the configuration or use case.

A medical communication protocol server that enables PostMessage-based integration between iframes and parent applications, providing simulated medical tools for medication management, allergy tracking, and other healthcare functions.

Related MCP Servers

Frontapp MCP Server
zqushair
-
security
A
license
-
quality
A Model Context Protocol server that integrates LLMs with Frontapp's customer communication platform, enabling access to conversations, contacts, and tags while supporting real-time updates via webhooks.
Last updated -
4
TypeScript
MIT License
Healthcare MCP Server
Cicatriiz
A
security
A
license
A
quality
A Model Context Protocol server providing AI assistants with access to healthcare data tools, including FDA drug information, PubMed research, health topics, clinical trials, and medical terminology lookup.
Last updated -
7
69
18
JavaScript
MIT License
AppSignal MCP Server
c20020207
A
security
A
license
A
quality
A Model Context Protocol server that connects to AppSignal, allowing users to fetch, list, and analyze incident information from their AppSignal monitoring.
Last updated -
3
1
2
TypeScript
MIT License
HAPI-MCP
ericmc21
-
security
F
license
-
quality
A Model Context Protocol server that enables querying FHIR healthcare data using natural language, allowing doctors to retrieve patient information, medications, observations, and other healthcare records.
Last updated -
1
Python

View all related MCP servers