What do REST and MCP expose?

REST and MCP are two ways for a client to call selected Python capabilities. They adapt the same retained function contract to different protocols.

Interface	Client action	Generated description
REST	Send an HTTP request to a selected operation.	OpenAPI contract and server adapter.
MCP	Discover tools and call a selected tool from an MCP client.	Tool descriptions, input schemas and server adapter.

The Quickstart makes real calls through both interfaces. Use the REST guide or MCP guide for a single source file or notebook, and the repository guide when local helpers span several files.

What the adapter establishes

The adapter validates supported input shapes and invokes the selected function under its configured execution mode. Private helpers remain private. A declared return annotation is descriptive evidence; it does not establish scientific correctness or add runtime return enforcement.

An MCP tool does not by itself choose an AI model, grant the model authority or guarantee a useful answer. A REST endpoint does not provide deployment, identity management or application authorization. Your application and infrastructure remain responsible for those decisions.

Read the REST generator and MCP generator contracts for their exact supported shapes and limitations.

Watch Part III: REST · Watch Part IV: MCP

Next step: Make your first calls or continue with the experiment path.