Skip to main content
Glama

Lumis — Life Sciences CRM Migration Intelligence

PyPI Python License

Lumis is an MCP server that delivers expert-level intelligence for life sciences CRM migrations. It equips AI assistants with a curated knowledge base covering module mapping, regulatory compliance, integration architecture, sync troubleshooting, performance guidance, data validation, decision trees, and operational gotchas — so every recommendation is grounded in domain expertise, not guesswork.

Quick Start

pip install lumis-mcp

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "lumis": {
      "command": "lumis-mcp"
    }
  }
}

Restart Claude Desktop. You'll see the Lumis tools in the tool picker.

Claude Code CLI

pip install lumis-mcp
claude mcp add lumis -- lumis-mcp

uvx (no install)

{
  "mcpServers": {
    "lumis": {
      "command": "uvx",
      "args": ["lumis-mcp"]
    }
  }
}

Remote (Claude.ai / OpenAI)

Connect to the hosted API at https://api.lumis-lifesciences.com/mcp with your API key in the X-Api-Key header. Sign up at lumis-lifesciences.com.

Related MCP server: Medical Billing MCP

What You Get

Tool

What it does

Free?

assess_migration_readiness

Complexity score, module mappings, gaps, risks, timeline

Yes

get_taxonomy

Browse the value chain taxonomy — phases, areas, categories

Yes

get_terminology

Map incorrect legacy terms to correct modern platform terms

Yes

search_knowledge

Full-text search across 950+ curated entries

get_module_mapping

Legacy module to cloud equivalent with field-level gaps

get_gotchas

Non-obvious pitfalls for a module or country

traverse_decision_tree

Interactive decision trees for module selection, migration paths

get_country_rules

GDPR, APPI, FDA 21 CFR Part 11, EU sample limits, US state rules

run_validation

Diagnose configuration issues from reported symptoms

get_agent_workflow

Structured workflows for migration, implementation, audit, ops

plan_multi_country_rollout

Wave-based rollout — country clustering, sequencing, timelines

compare_entities

Side-by-side: countries, modules, regulatory frameworks

plan_system_validation

CSV/CSA validation plan — GAMP, Part 11, Annex 11, deliverables

Example Prompts

Try these after connecting:

  • "Assess migration readiness for a company using CLM, Samples, Events, and Approved Email across 6 countries with 2,000 users."

  • "What are the top gotchas when migrating sample management?"

  • "Get the country rules for Germany — GDPR constraints on consent management and sample distribution limits."

  • "Plan a 35-country rollout for CLM, Samples, and Events including US and Japan."

  • "What does 21 CFR Part 11 require for electronic signatures in sample management?"

  • "Compare Germany vs. France — which has stricter sample management requirements?"

Knowledge Base

Lumis ships with 950+ curated knowledge entries spanning the pharma value chain:

  • Module Mapping — Legacy CRM to cloud platform with field-level gaps

  • Regulatory Compliance — 21 CFR Part 11, EU GDPR, Japan APPI, EU sample limits, US state HCP rules

  • Sync Engine Architecture — Offline-first patterns, conflict resolution, delta sync

  • Integration Patterns — REST API, MDM feeds, SSO/OAuth, ERP, middleware

  • Performance & Scale — Data volume planning, governor limits, mobile sync benchmarks

  • Multi-Country Rollout — Country clustering, wave sequencing, anti-patterns

  • Decision Trees — Module selection, migration path, regulatory compliance

  • Gotchas — 65+ non-obvious pitfalls and edge cases

  • Validation Rules — Symptom-based diagnostic rules

  • System Validation (CSV/CSA) — GAMP 5, Part 11 mapping, risk assessment framework

Pricing

Tier

Price

Access

Free

$0

Migration assessment + terminology + taxonomy

Starter

$49/mo

Full knowledge base — individual consultants

Professional

$199/mo

Full KB + priority support — implementation teams

Enterprise

Contact sales

Custom knowledge overlays + SLA

The free tier requires no API key.

Architecture

lumis-mcp/
├── server.py              # MCP server with 13 tools
├── knowledge/             # 950+ entries across 280+ files
│   ├── _foundation/       # Org strategy, regulatory, terminology, validation
│   ├── _meta/             # Value chain taxonomy
│   ├── commercialization/ # CRM, safety, regulated content, market access
│   └── clinical/          # Clinical development (expanding)
├── agents/                # 4 agent workflow definitions
├── prompts/               # Agent persona system prompts
└── lumis_mcp/             # PyPI package wrapper

Requirements

  • Python 3.10+

  • mcp>=1.0,<3.0

  • pyyaml>=6.0

License and Intellectual Property

This software and its knowledge base are proprietary and copyright Lumis AI 2024-2026. All rights reserved.

  • Software: Licensed for use via MCP clients only. See LICENSE.

  • Knowledge Base: 950+ curated entries are trade secrets. Extraction, scraping, reproduction, or use for training ML models is prohibited.

  • Third-party notices: See NOTICE.

Unauthorized copying or redistribution will be pursued under applicable law.


Built by Lumis AI — migration intelligence for life sciences.

Available Tools

13 tools
assess_migration_readinessB

Run a migration readiness assessment for any commercialization area.

Args: source_platform: Current platform (e.g. 'Legacy CRM', 'Argus Safety', 'Veeva Vault') modules_in_use: Comma-separated list of modules currently in use country_count: Number of countries in scope user_count: Approximate number of users area: Commercialization area — 'crm', 'safety-pv', 'regulated-content' (default 'crm')

Inputs: user_count (required), country_count (required), modules_in_use (required), source_platform (required), +1 more. Returns: result

compare_entitiesA

Compare two entities side-by-side — countries, modules, regulatory frameworks, or any knowledge base entries.

Args: entity_a: First entity to compare (e.g. 'Germany', 'CLM', 'Argus') entity_b: Second entity to compare (e.g. 'France', 'Events', 'Vault Safety') dimension: Optional focus dimension (e.g. 'sample rules', 'field mapping', 'regulatory') phase: Value chain phase filter (default 'all') area: Area filter (default 'all')

Inputs: entity_a (required), entity_b (required), area, phase, +1 more. Returns: result

get_agent_workflowA

Get the workflow, phases, and checklists for a specific Lumis agent.

Args: agent: Agent name — 'migration', 'implementation', 'audit', or 'operations'

Inputs: agent (required). Returns: result

get_country_rulesA

Get regulatory and configuration rules for a specific country.

Foundation rules (GDPR, APPI, data residency) are always included. Use area to add domain-specific rules (e.g. 'safety-pv' for adverse event reporting timelines).

Args: country: Country name or code (e.g. 'Germany', 'DE', 'Japan') module: Optional module filter (e.g. 'Sample Management', 'AE Reporting') phase: Value chain phase filter (default 'all') area: Area filter (default 'all')

Inputs: country (required), area, phase, module. Returns: result

get_gotchasC

Get non-obvious pitfalls and gotchas for a module, country, or domain area.

Args: module: Filter by module name (optional) country: Filter by country (optional) phase: Value chain phase filter (default 'all') area: Area filter — 'crm', 'safety-pv', etc. (default 'all')

Inputs: area, phase, module, country. Returns: result

get_module_mappingA

Get the target platform equivalent for a source module.

Args: source_module: The source module name (e.g. 'CLM', 'Legacy Events', 'AE Reporting') area: Which area to search — 'crm', 'safety-pv', 'regulated-content', etc. (default 'crm')

Inputs: source_module (required), area. Returns: result

get_taxonomyA

Get the Lumis value chain taxonomy — phases, areas, and available knowledge categories.

Call this first to understand what domains Lumis covers and how knowledge is organized.

Inputs: no named parameters. Returns: result

get_terminologyB

Look up correct vs incorrect terminology to avoid hallucinations.

Args: term: Term to look up (e.g. 'CLM', 'Approved Email', 'ICSR', 'CIOMS')

Inputs: term. Returns: result

plan_multi_country_rolloutA

Plan a wave-based multi-country rollout for any commercialization area.

Args: country_count: Total countries in scope modules: Comma-separated list of modules to deploy regions: Comma-separated regions in scope (e.g. 'EU, Americas, APAC, LATAM') includes_us: Whether the US is in scope (adds regulatory complexity) includes_japan: Whether Japan is in scope (requires standalone wave) area: Commercialization area — 'crm', 'safety-pv', 'regulated-content' (default 'crm')

Inputs: modules (required), regions (required), country_count (required), area, +2 more. Returns: result

plan_system_validationA

Plan a computer system validation (CSV/CSA) for a life sciences system.

Returns applicable regulations, methodology recommendation, GAMP classification, deliverables list, effort estimate, gap assessment areas, and decision tree guidance.

This tool supports planning for 21 CFR Part 11, EU Annex 11, GAMP 5, and related regulatory requirements across CRM, clinical, safety, and manufacturing systems.

Args: system_name: Name of the system being validated (e.g. 'Salesforce CRM', 'Veeva Vault', 'SAP QM') system_type: Type of system — 'saas', 'cots', 'configured', 'custom', 'hybrid' platform: Platform vendor if applicable (e.g. 'Salesforce', 'Veeva', 'SAP', 'Oracle') regulatory_geography: Jurisdiction — 'US', 'EU', 'Japan', 'Global', 'WHO' (default 'US') gxp_context: GxP context — 'GMP', 'GCP', 'GLP', 'GPvP', 'GDP', or comma-separated combo modules_in_use: Comma-separated modules (e.g. 'Sample Management, Events, Consent') has_mobile: Whether mobile/offline is in scope (adds validation complexity) has_integrations: Whether system integrations are in scope has_custom_code: Whether custom code (e.g. Apex, custom middleware) exists user_count: Approximate number of users country_count: Number of countries in scope

Inputs: system_name (required), system_type (required), platform, has_mobile, +7 more. Returns: result

run_validationB

Run a validation rule or find rules matching a reported symptom.

Args: rule_id: Specific rule ID to run (optional) symptom: User-reported problem to match against rules (optional) area: Area to validate — 'crm', 'safety-pv', etc. (default 'crm')

Inputs: area, rule_id, symptom. Returns: result

search_knowledgeA

Search the Lumis knowledge base across the life sciences value chain.

Foundation knowledge (org strategy, regulatory, terminology) is always included. Use phase and area to narrow scope.

Args: query: Natural language search query phase: Value chain phase — 'discovery', 'clinical', 'commercialization', 'foundation', or 'all' area: Area within phase — e.g. 'crm', 'safety-pv', 'regulated-content', 'market-access', or 'all' category: Knowledge category — 'modules', 'decision-trees', 'gotchas', 'country-rules', 'validation-rules', 'terminology', 'org-strategy', or 'all' limit: Maximum results to return (default 5)

Inputs: query (required), area, limit, phase, +1 more. Returns: result

traverse_decision_treeB

Walk a decision tree given user inputs to produce a recommendation.

Args: tree_name: Name of the decision tree (e.g. 'module-selection', 'migration-path', 'org-strategy') inputs: JSON string of input parameters for the tree phase: Value chain phase filter (default 'all') area: Area filter (default 'all')

Inputs: inputs (required), tree_name (required), area, phase. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct jobs: retrieval (get_country_rules, get_terminology, get_module_mapping, get_gotchas), action-oriented planning (assess_migration_readiness, plan_multi_country_rollout, plan_system_validation), and generic utilities (search_knowledge, compare_entities, traverse_decision_tree). The main blur is that search_knowledge exposes category filters ('country-rules', 'gotchas', 'terminology', 'decision-trees') that substantially overlap with four specialized tools, so an agent could plausibly reach for the wrong one. Descriptions suggest the specialized tools return structured/filtered output, which mitigates but does not eliminate the overlap.

    Naming Consistency5/5

    All 13 names follow a consistent snake_case verb_noun pattern (get_*, run_*, search_*, traverse_*, assess_*, plan_*, compare_*). Verbs are chosen meaningfully rather than arbitrarily, and there are no mixed conventions or versioned/suffixed outliers.

    Tool Count5/5

    Thirteen tools is squarely in the well-scoped range for a knowledge-plus-advisory server, with each tool mapping to a distinct knowledge category or planning task. Nothing feels like filler, and the surface is not so large that selection becomes a burden.

    Completeness4/5

    The read-only advisory surface is well covered: taxonomy discovery, knowledge search, rules/terminology/gotchas retrieval, decision trees, comparison, and three substantive planning tools (migration readiness, rollout waves, CSV). Minor gaps exist — analytical tools default to commercialization areas ('crm', 'safety-pv', 'regulated-content') with no equivalent depth for discovery/clinical, and there is no way to enumerate available decision trees or agent workflows other than via get_taxonomy/get_agent_workflow. These are workable-around rather than blocking.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers