Conduit
Conduit
Docsllms.txtHostingGitHubIntroduction

Getting Started

OverviewInstall ConduitMCP SetupYour First AppStart with AI

Learn

ArchitectureClient vs Admin APIConfiguration

Modules

OverviewAuthenticationAuthorizationDatabaseStorageCommunicationsChatRouterFunctions

Guides

Next.js IntegrationReBAC Team ScopingGitOps State Export

Deployment

Deployment OverviewDocker ComposeKubernetes and HelmLocal from SourceContainer Images

Reference

CLI ReferenceClient APIAdmin APIEnvironment VariablesMCP Tools

Resources

Migration v0.16 → v0.17Legacy DocumentationChangelogFAQGlossaryContributing

Client vs Admin API

Which API to use in apps, MCP, and server-side code — and what never to mix.

Conduit has three API surfaces. Mixing them causes security incidents and broken integrations.

Comparison

Client APIAdmin APIgRPC service API
AddressCLIENT_BASE_URL (router, default :3000)ADMIN_BASE_URL (core, default :3030)CONDUIT_SERVER
ConsumersWeb/mobile apps, Next.js routes acting for usersAdmin panel, MCP, CI scriptsCustom modules, trusted server code
AuthUser bearer tokensmasterkey, admin JWT, cdt_ tokensService identity; DB calls need scope/userId
Database/database/{Schema}, /database/function/{name}Schema/endpoint admin, indexesgrpcSdk.database
MCPNot exposedWrapped as MCP toolsNot exposed

Rules (non-negotiable)

  1. Never embed masterkey, admin JWTs, or cdt_ tokens in app code or browser config.
  2. Never call Admin API from user-facing request paths.
  3. Provisioning (schemas, endpoints, config) happens at dev/deploy time via MCP or admin scripts — not runtime app code.
  4. Never fetch whole collections and filter client-side — use custom endpoints.
  5. Never expose presigned storage URLs to browsers — preview proxy with storageFileId.

MCP vs Client API

Use MCP whenUse Client API when
Creating schemas at dev timeUser CRUD at runtime
Patching module configLogin, register, renew
Admin user/team managementPermission checks with user token
Index creationCalling custom endpoints

For AI agents

This page is the canonical guardrail reference. Plugin rules link here instead of duplicating content.

Architecture

Core, router, modules, Redis, and gRPC service discovery.

Configuration

Module config via Admin API, config bus, and environment variables.

On this page

ComparisonRules (non-negotiable)MCP vs Client API