Developers

Build with Owlect

Two ways to work with Owlect collections from outside the app. Both act on behalf of a signed-in user, with their permission, and see only that user's data.

REST API

Plain HTTPS and JSON for scripts, automations, apps and Custom GPTs.

11 endpoints for collections and items
OpenAPI 3.1 spec, generated from the code
OAuth 2.1 with PKCE

Read the API docs →

MCP server

Connect Owlect to Claude, ChatGPT, Claude Code and other MCP clients, then manage collections by chatting.

11 tools, no code needed
Works as a custom connector
Sign in with Google, click Allow

Set up MCP →

Shared by both

The same sign-in: Owlect's OAuth 2.1 server, with Google as the identity provider.
The same permissions, chosen per app when the user connects it: read (always), create (on by default), update and delete (off by default). Users see and disconnect every app in Settings -> Connected apps.
The same operations, validation, plan limits and rate limits. A connection using both shares one budget.
No access to other users' data, sharing settings, account settings or billing.

Machine-readable

OpenAPI 3.1 spec (JSON)/api/v1/openapi.json
REST API docs as Markdown/developers/api.md
MCP docs as Markdown/developers/mcp.md
llms.txt/llms.txt

Questions, higher limits or a client with a secret for a Custom GPT: support@owlect.app