Documentation
Setup, authentication, tool reference, and enterprise connector guides.
Contents
Quick Start
NovoMCP is a remote MCP server with OAuth support that works with any MCP-compatible AI client: Claude, ChatGPT, Cursor, Windsurf, GitHub Copilot, and more.
Prerequisites: A NovoMCP API key (request access) and an MCP-compatible AI client (Claude, ChatGPT, Cursor, etc.).
Claude Desktop / Web / Mobile (GUI)
- Go to Settings > Connectors
- Click "Add custom connector"
- Enter URL:
https://ai.novomcp.com/mcp - Click Connect — a login page opens in your browser
- Enter your NovoMCP API key (
nmcp_...) - Click Authorize Access — done!
NovoMCP uses OAuth 2.0 for authentication. No config files or headers needed—just add the URL and authenticate in your browser.
Claude Code (Terminal)
- Add the server:
claude mcp add --transport http novomcp https://ai.novomcp.com/mcp - Start a session:
claude - Authenticate: type
/mcp— browser opens for OAuth login - Enter your API key and authorize — 27 tools now available!
Auth tokens are stored in your system keychain and refresh automatically on future sessions.
Team Setup (.mcp.json)
For teams, add NovoMCP to your repo's .mcp.json so every team member gets it automatically:
Each team member still authenticates individually via /mcp on first use.
Cursor / Windsurf
- Open Settings → MCP (or equivalent)
- Add server URL:
https://ai.novomcp.com/mcp - Authenticate with your API key
- Done — all 27 tools available in chat
Other MCP Clients
Any MCP-compatible client can connect using:
Claude Desktop (Config File Alternative)
If you prefer manual configuration:
Config file locations:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop after saving.
Supported clients: Claude (web, desktop, mobile, terminal, API), ChatGPT, Cursor, Windsurf, GitHub Copilot, and any client that implements the Model Context Protocol.
Try it
Once connected, ask your AI:
Your AI calls get_molecule_profile automatically and returns toxicity predictions, drug-likeness scores, regulatory status, and more. See the Examples section for full response format.
Authentication
NovoMCP supports two authentication methods:
OAuth 2.0 (Recommended)
When you add NovoMCP as a connector, your client automatically uses OAuth. You'll be redirected to a login page where you enter your API key. This is the simplest setup—no headers or config files needed.
API Key Header (Direct Access)
For programmatic access or config file setup, pass your API key in the X-API-Key header or Authorization: Bearer header.
Getting a Key
Request access via email. Keys are provisioned within 24 hours. Each key includes an organization ID and name.
Key Format
Keys follow the format nmcp_[random]. Store securely — keys cannot be retrieved after creation.
Tool Reference
NovoMCP exposes 27 tools, 5 resources, and 4 prompts via the Model Context Protocol. Your AI client invokes these automatically.
Molecular Intelligence
identifier (SMILES, CID, or name)smilessmilessmiles, include_coordinatessmiles, threshold (0.0-1.0), limitfilters (object), limitidentifiers (array)smiles, target_qed, target_logp, num_variantsADMET & FAVES Compliance
FAVES (Fairness, Accountability, Validity, Ethics, Safety) is NovoMCP's inline compliance layer. It screens every molecule against eight regulatory jurisdictions—DEA, FDA, EPA, CWC, EU REACH—as part of the prediction, not as a separate step. Profiles, optimizations, and library screens all include FAVES results automatically.
smilessmiles, contextidentifiers (array), filters, full_favesStructure Prediction
target (name, PDB ID, or UniProt ID), sequence (optional), include_ligands (default true)sequence, namejob_idLiterature & Data Search
query, top_kquery, top_kquery (e.g., "BRAF inhibitors"), server (biorxiv/medrxiv), top_k, days_backquery (e.g., "Osimertinib"), search_type (compound/target/activity), top_kquery (e.g., "obesity treatment"), status, phase, top_kTip: Use search_literature, search_patents, search_biorxiv, and search_clinical_trials together to build a comprehensive landscape analysis for a specific target or compound.
Platform & Account
info_type (all, tiers, database, admet, compliance, usage)job_idtype (summary or detailed)Data Connectors
action (preview/pull/estimate_pipeline/execute_pipeline), connection_id, table, filters, processing_tools, confirmation_tokenconnector_type, connection_idtool_name, connector_type, target_tableconnector_type, connection_id, data, target_tableResources
NovoMCP exposes 5 resources that provide static and dynamic data. Access via GET /mcp/resources.
Prompts
NovoMCP provides 4 pre-defined prompts for common workflows. Access via GET /mcp/prompts.
smiles (required)smiles (required)smiles (required), min_similarity (optional, default 0.7)query (required), max_results (optional, default 10)Enterprise Connectors
Export molecular intelligence data directly to your data warehouse or collaboration tools. 4 connector adapters with OAuth sign-in, dynamic schema discovery, AI-assisted field mapping, and full governance.
Available Connectors
- Snowflake
- Databricks
- BigQuery OAuth
- Supabase
How It Works
The export workflow follows three steps:
- Discover:
discover_schemaintrospects the target system—tables, columns, types—and normalizes everything to 5 standard types (string, number, boolean, datetime, json). - Map:
preview_mappingaligns NovoMCP tool output fields to target columns. Uses template mapping for common combos, auto-matching by name, or AI-assisted mapping via Azure OpenAI with confidence scores. - Export:
export_resultswrites data to the target system through the appropriate connector adapter.
Governance
Enterprise exports are secured by novomcp-auth—an identity and governance service implementing RFC 8693 token exchange. Your nmcp_ API key is exchanged for a scoped JWT with connector-specific permissions. All export operations are audit-logged with full traceability.
Credentials: All connector credentials are stored in Azure Key Vault—never in the database. Each connector supports test_connection to verify credentials before any data export.
Connector Setup Guides
Each connector has its own authentication method. Follow the guide for your target system.
Click "Connect with Google" in the connections dashboard. You'll be redirected to Google's consent screen to authorize BigQuery access. No API keys or service accounts needed—your Google account credentials are used directly. Tokens refresh automatically.
Alternative: You can also connect using a Google Cloud service account JSON key for server-to-server access without user interaction.
Provide your Snowflake account identifier (e.g. xy12345.us-east-1), username, and password. You'll also need to specify a warehouse, database, and schema in the connection config.
Find your account identifier in Snowflake under Admin > Accounts.
Generate a personal access token in Databricks: User Settings > Developer > Access Tokens > Generate New Token. Provide the token along with your workspace URL (e.g. https://adb-1234567890.1.azuredatabricks.net) and target catalog/schema.
Find your connection details in your Supabase project dashboard under Settings > Database > Connection String. Use the service_role key for full table access, or the anon key for RLS-restricted access.
Examples
Ask in natural language. NovoMCP tools are selected and invoked automatically—no tool names or parameters needed.
Basic Profiling
Your AI invokes get_molecule_profile with identifier "ibuprofen" and receives:
Additional Examples
Each query maps to specific tools, selected automatically based on your prompt.
→ optimize_molecule — generates variants targeting QED and LogP thresholds
→ get_molecule_profile — returns DEA, FDA, structural alert status
→ search_literature + search_clinical_trials — parallel search across sources
→ search_similar — similarity search with property and compliance filters
→ pull_from_source — preview → estimate → execute pipeline
Combining search tools: search_literature, search_patents, search_biorxiv, and search_clinical_trials can be combined in a single prompt for landscape analysis. Example: "Give me a complete landscape analysis of KRAS inhibitors."
Novel molecules: Compounds not in the pre-computed database are processed on-the-fly via RDKit with FAVES screening. Response times: ~500ms vs ~50ms for indexed compounds.