Fulcra Context MCP vs Mymedi AI MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
Fulcra Context MCP vs Mymedi AI MCP Server
In-depth architectural comparison of the Fulcra Context MCP and Mymedi AI MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Fulcra Context MCP
Biology, Medicine and Bioinformatics · Local stdio
Quality: 61/100 (Good) | Auth: OAuth 2.0
Mymedi AI MCP Server
Biology, Medicine and Bioinformatics · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Fulcra Context MCP if you need specialized Biology, Medicine and Bioinformatics tools running via a local process. Choose Mymedi AI MCP Server if your workspace requires Biology, Medicine and Bioinformatics integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Fulcra Context MCP when:
You need dedicated capabilities in the Biology, Medicine and Bioinformatics domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (BYOK (Pay Provider Direct)).
You have access to required keys: FULCRA_ENVIRONMENT.
MCP server for accessing personal health and biometric data including sleep stages, heart rate, HRV, glucose, workouts, calendar, and location via the Fulcra Life API with OAuth2 consent.
Healthcare billing AI for agents: ICD-10/CPT/HCPCS code lookup (81,769 codes with RVU + OPPS pricing), prior auth prediction, medical NER, claims validation, denial-risk scoring, HIPAA compliance auditing, and NPI/drug enrichment. 20 tools, 10 free credits then pay-per-call via credits or anonymous USDC (x402). npx @mymedi-ai/mcp-server
Category & Scope
Tools & Capabilities Breakdown
Fulcra Context MCP Tools (25)
get_workouts
Get details about the workouts that the user has done during a period of time.
Result timestamps will include time zones. Always translate timestamps to the user's local
time zone when this is known.
annotations_catalog
Get the list of all annotation data types the user has defined.
This does not get the actual values the user has recorded; for that, use the `get_records` tool.
Use this tool to get the IDs and types to pass to `get_records`.
create_data_type
Create a user-defined data type so the user can track something new.
Choose base_type by what gets recorded: "moment" (a point in time),
"duration" (a time range), "boolean" (yes/no), "numeric" (a number,
optionally with a unit), or "scale" (a 1-5 rating with labels).
The new type appears in get_data_catalog, and recorded values are readable
with get_records. Creation is reversible with archive_data_type.
archive_data_type
Archive (soft-delete) a user-defined data type.
The type and its recorded data are recoverable with restore_data_type.
Only user-defined types (created via create_data_type or the Context app)
can be archived.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Fulcra Context MCP is categorized under Biology, Medicine and Bioinformatics and uses a local stdio subprocess. In contrast, Mymedi AI MCP Server belongs to Biology, Medicine and Bioinformatics using local stdio subprocess. Select Fulcra Context MCP when you need capabilities focused on biology, medicine and bioinformatics and Mymedi AI MCP Server when you require tools for biology, medicine and bioinformatics.
Record a single record for a recordable data type.
Use get_data_catalog to find data types; user-defined ones use the
"<BaseType>/<uuid>" ID form (create new ones with create_data_type).
Recorded data can be read back with get_records.
get_data_catalog
Get all data types available for this user, grouped by relevant MCP tool.
Includes health and sensor measurements,
location, events, and user-defined annotation types.
Call this before requesting time-series data or raw records, and only use a
data type with the tools named in its group.
get_time_series
Get calculated per-interval time-series values for a single data type.
Only data types that `get_data_catalog` lists as usable with this tool are
supported; other types can be read with `get_records`. Result timestamps
include time zones; translate them to the user's local time zone when known.
get_records
Retrieve the raw records of any data type during a time period.
Works with every type listed by `get_data_catalog`, including user-defined
ones ("<BaseType>/<uuid>" IDs); the correct API endpoint is chosen
automatically. Records that cover a time range are included when any part
of it intersects the requested window. Results are raw samples — they may
come from multiple sources and can overlap; for calculated per-interval
values of numeric data types, prefer `get_time_series`. Result
timestamps include time zones; translate them to the user's local time
zone when known.
get_data_updates
Summarize the data that arrived in the user's account during a period of time.
The time range filters on when records were processed/synced into Fulcra,
NOT on the records' own timestamps — e.g. last night's sleep records
typically arrive this morning. Use this to find out what new data exists
since a previous check, then query the changed types with the appropriate
tools.
get_sleep
Return the user's sleep data at a chosen level of detail.
Pick the coarsest level that answers the question — results grow with detail:
- "aggregate": stage totals per period (default 1 day), one row per period
per stage. Best for multi-day questions ("how did I sleep this month").
- "cycles": one row per sleep session.
- "stages": every stage interval (the full hypnogram); single-night detail.
Sleep spans midnight (starts day N, ends day N+1) — extend the time range
accordingly. Stage integers: 0=In Bed, 1=Asleep/Unknown, 2=Awake, 3=Light,
4=Deep, 5=REM. Result timestamps include time zones; translate them to the
user's local time zone when known.
get_location_at_time
Gets the user's location at the given time.
If no sample is available for the exact time, searches for the closest one up to
window_size seconds away.
Result timestamps will include time zones. Always translate timestamps to the user's local
time zone when this is known.
+13 more tools listed on main page
Mymedi AI MCP Server Tools (32)
pa_required_check
Check whether a HCPCS code is on the CMS Required Prior Authorization List (42 CFR 414.234). Returns paRequired flag, category, nationwide-since date, and list version. Original Medicare FFS scope. Free, no API key required.
denial_code_info
Explain a DME claim denial code (CARC). Returns title, meaning, common DME causes, fixes, appealability, and related codes. Free, no API key required.
code_lookup_basic
Look up basic metadata for a medical code: code, codeType, description, category, isActive. Basic metadata only — the paid code_lookup adds full metadata. Free, no API key required.
reimbursement_basic
Look up Medicare payment for a code. Returns the national PFS facility and non-facility payment (CMS RVU × conversion factor) for professional services, plus DMEPOS fee-schedule ranges (rental/purchase, min–max across state fees) for DME items like E/K/L codes. Free, no API key required.
order_readiness_checklist
Blank pre-delivery checklist for a HCPCS DMEPOS code: the universal standard written order (SWO) elements (42 CFR 410.38(d)), whether the code requires a face-to-face encounter and written order prior to delivery (F2F/WOPD), and whether it is on the Medicare Required Prior Authorization List. Requirement definitions only — PHI-free, never send patient data. Free, no API key required.
modifier_advisor
Editorial guidance on DMEPOS billing modifiers: the KX/GA/GY/GZ medical-necessity and liability family, RR/NU/UE rental-vs-purchase, capped-rental month markers (KH/KI/KJ), and RT/LT laterality. Pass a HCPCS code to scope guidance to that item's DMEPOS category, or a category directly; add a scenario phrase (e.g., "ABN on file", "bilateral") to surface the relevant modifiers. Original editorial content, not payer policy. PHI-free. Free, no API key required.
code_lookup
Look up a medical code (ICD-10, CPT, HCPCS). Returns description, category, active status, and related codes. For DMEPOS (HCPCS) codes it also returns a labeled fee schedule: per-modifier (RR/NU/UE) national min–max ranges, or — when a state is given — that state's exact non-rural and rural rates. Source: CMS DMEPOS Fee Schedule (DME26-B).
code_lookup_batch
Look up a list of medical codes (ICD-10, CPT, HCPCS) in one call. Per-item results mirror code_lookup (description, category, active status, related codes, DMEPOS fee schedule with optional state filter). Priced per code — $0.001 × number of codes, max 25 per call; the full charge is refunded automatically when every code misses.
code_suggest
Suggest ICD-10/CPT/HCPCS codes from a clinical description. Term-based search over the 90K-code CMS database, ranked by matched-term coverage and relevance. Works with natural sentences ("patient with obstructive sleep apnea prescribed CPAP"). Automatically refunds the call when nothing matches.
code_validate
Validate a medical code for correctness, active status, and context. Returns warnings and errors.
code_validate_batch
Validate a list of medical codes for correctness, active status, and optional date-of-service context in one call. Per-item results mirror code_validate (valid, active, warnings, errors, codeDetails). Priced per code — $0.005 × number of codes, max 25 per call. An invalid code is a billable answer (valid:false), same as the single validate.
pa_predict
Prior-authorization outlook for a procedure code. When a historical cohort of decided PAs exists (≥10), returns a data-driven approval rate with cohort size and confidence. When no cohort exists, returns the verifiable facts instead — CMS Required Prior Authorization List status, category, and published review timeframes — and explicitly reports that no probability was computed (the call is refunded on this path). Never fabricates a probability. Original Medicare FFS scope.