Developer API access

Choose an approved way to connect an application or agent to a Novaplan AI workspace.

Novaplan AI provides integration options for an existing, managed workspace. The API contract available to your organization depends on its Enterprise configuration and the permissions approved for your integration. Confirm the endpoints and authentication method with Novaplan Support before building against the REST API.

Choose an integration path

Need	Start here
Connect a coding agent or another MCP client to company knowledge	MCP server overview and tool reference
Authenticate a personal script or client as one user	Personal access tokens
Let multiple users authorize an application separately	OAuth 2.0 applications
Understand the workspace and its components	System overview

MCP clients normally connect to the workspace’s /mcp endpoint. A personal access token acts as its owner and remains limited by that person’s permissions and the token’s scopes. OAuth authorization code is appropriate when each person must sign in and consent separately. Do not use OAuth client_credentials for an integration that must respect a particular user’s access.

REST API access

The detailed service API catalog is not part of this first public documentation release. Some internal and administrative routes described by the underlying platform may not be enabled or supported for customer integrations in the deployed Novaplan AI Enterprise workspace. Do not infer a supported contract from an internal route or a code example.

Tell Novaplan Support what your application needs to read or change, which users it will act for, and whether MCP meets the use case. Novaplan can confirm the supported interface, permissions, and any SDK options for your workspace.