Skip to content
REST API

The engine, as an API.

One call pattern for every tool. Call the engine's in-silico tools over HTTP from a script or your own AI agent. The REST API ships in the open engine: install it and it serves on localhost:8018, the same engine behind the MCP surface.

Install the engineRead the docs
69
MCP tools
1
call pattern
3.1
OpenAPI spec
BYO
bring your own agent
Quickstart

One pattern, every tool.

Every tool is POST /mcp/tools/{name} with a JSON body. In local mode any bearer token works. Plain HTTP, no SDK.

curl
curl -s -X POST http://localhost:8018/mcp/tools/get_molecule_profile \
  -H 'Authorization: Bearer local' \
  -H 'Content-Type: application/json' \
  -d '{"arguments": {"smiles": "CC(=O)Oc1ccccc1C(=O)O"}}'

Responses come back as { result, usage }. The tool's payload, plus the tool name and the funnel ID the call was logged under in the local audit trail. Full curl, Python, and JavaScript examples are in the API docs.

The headline use case

Bring your own AI agent.

NovoMCP is the engine. You supply the model. Expose Novo's tools to your own agent (Claude API, GPT, anything) and let it call them in its loop, with live tool schemas from GET /mcp/tools.

python
# Expose Novo's tools to your own model and let it call them in its loop.
def call_novomcp(tool, arguments):
    r = requests.post(
        f"http://localhost:8018/mcp/tools/{tool}",
        headers={"Authorization": "Bearer local"},   # local mode accepts any token
        json={"arguments": arguments},
    )
    return r.json()   # { "result": {...}, "usage": {...} }
Three hostnames

Each hostname, one job.

localhost:8018 is the open engine over plain HTTP. localhost:8018/mcp is the same engine as an MCP surface for any MCP-compatible assistant. api.novomcp.com hosts the two closed services: the FAVES compliance API and FEP.

localhost:8018Local REST surface, the open engine over plain HTTP, any bearer token in local modeself-host
localhost:8018/mcpLocal MCP surface, the same engine for any MCP-compatible AI assistantself-host
api.novomcp.comHosted closed services: the FAVES compliance API (POST /v1/tools/check_compliance) and FEPhosted · FAVES + FEP
One engine, every surface

Novo is the engine. Reach it the way you work.

Chat, your own code, the desktop, the browser, your editor, the terminal. One engine and one audit trail, whichever door you use.

See how the surfaces connect →
Build on the engine

Wire 69 in-silico tools into your stack.

Self-host the engine on your own hardware, including an NVIDIA DGX Spark. FAVES compliance and FEP are the hosted services.

Install the engineFAVES API