Agent Care MCP Server - Azalea Health Integration

Created By
vlcosenta year ago
Agent Care MCP Server configured for Azalea Health FHIR API integration
Overview

What is Agent Care MCP Server?

Agent Care MCP Server is a configuration repository designed to integrate with Azalea Health's Ambulatory FHIR API, enabling seamless data exchange and interaction with healthcare services.

How to use Agent Care MCP Server?

To use the Agent Care MCP Server, clone the repository, install the necessary dependencies, build the project, and start the server using the provided scripts for your operating system.

Key features of Agent Care MCP Server?

  • Integration with Azalea Health's FHIR API for healthcare data management.
  • Support for multiple operating systems (Linux, Mac, Windows).
  • Testing capabilities using the MCP inspector tool.

Use cases of Agent Care MCP Server?

  1. Connecting healthcare applications to Azalea Health's FHIR API.
  2. Facilitating data exchange between healthcare providers and patients.
  3. Testing and validating FHIR API interactions in a sandbox environment.

FAQ from Agent Care MCP Server?

  • What are the prerequisites for using this server?

You need Node.js v14 or later and npm installed on your machine.

  • Can I use this server for production?

This configuration is intended for sandbox testing only and should not be used for real patient data.

  • How do I test the MCP server?

You can test the MCP server using the MCP inspector tool after setting it up.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vlcosent
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