Used as the development server for running the MCP application, enabling hot module replacement and efficient local development.
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
2. API Implementation
The following methods in ozwell-integration.js
need real implementation:
generateResponse()
- Make HTTP calls to Ozwell chat APIparseToolCalls()
- Parse Ozwell's tool call formatformatResponse()
- 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
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
š Current Architecture
š To Run Current Application
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
Environment Configuration
API Keys Setup
Copy the environment template:
cp .env.example .envAdd your API credentials to
OZWELL_API_KEY=your_actual_api_key_here OZWELL_BASE_URL=https://ai.bluehive.com/api/v1/completion OZWELL_MODEL=ozwell-medical-v1 FORCE_SIMULATION_MODE=falseThe
The API key will be fetched from the environment variable
Fallback to hardcoded values if
.env
file is not availableNever commit the
.env
file to version control (it's in.gitignore
)
Security Notes
Keep your API keys secure and never commit them to version control
Use
.env.example
as a template for other developersThe application will fall back to hardcoded values if environment loading fails
This server cannot be installed
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
- AsecurityAlicenseAqualityA 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 -71450MIT License
- AsecurityAlicenseAqualityA Model Context Protocol server that connects to AppSignal, allowing users to fetch, list, and analyze incident information from their AppSignal monitoring.Last updated -313MIT License
- AsecurityAlicenseAqualityA Model Context Protocol server that enables natural language commands to manage healthcare data stored in Medplum FHIR servers through standardized Create, Read, Update, and Search operations.Last updated -3711MIT License