Compare the surfaces
| Surface | Best for | Access | Auth | Wiki identifier | File upload |
|---|---|---|---|---|---|
| CLI | People, coding agents, shell automation | Read + write | Browser session or API key | Handle | Files and recursive folders |
| Python SDK | Python services and scripts | Read + write | Reused CLI session or API key | Handle | Individual file paths |
| REST API | Services in any language | Key permissions | API key | Resource IDs | Prepare, upload to signed storage, complete |
| MCP | Remote AI clients that need context | Read-only | Browser-approved OAuth | Explicit handle on every call | None |
A practical default
- Start with the CLI when a person or agent can use a terminal. It is the only surface that recursively discovers local folders.
- Use the Python SDK when Python code should work with validated models and a resolved wiki handle.
- Use the REST API for non-Python services or direct control over
/v1. - Use MCP when an AI client only needs to search and read existing knowledge.
Use the CLI
Work interactively or automate with JSON and stable exit codes.
Use the Python SDK
Search, upload, and follow jobs from Python.
Call the REST API
Authenticate, discover IDs, and make a direct request.
Connect through MCP
Give an AI client read-only wiki context.