Sajel·سجل
Learn Sajel
Claude Connector

Claude Connector

Connect Claude to your Sajel data by pasting one address and signing in, then let it read and build boards.

What the connector is

Sajel hosts an MCP (Model Context Protocol) endpoint. Claude connects to it the way it connects to any other service you own: you paste the address, sign in to Sajel, and approve what it is asking for. There is no key to copy, store or keep out of sight.

All three Claude clients work the same way: claude.ai, Claude Desktop and Claude Code.

Once connected, Claude can list your workspaces, read board schemas and records, create bases, boards, fields and records, link records, run views, and inspect automations. It acts as you and can reach exactly what you can reach, never more.

The connector exposes 18 tools plus built-in skills, and they load by themselves. Nothing else to install.

Get an API key

1

Copy your Sajel address

Go to Settings, then Connections. The address at the top is the only thing you need to copy.

2

Paste it into Claude

In Claude, open Settings, Connectors, Add custom connector, and paste it. Claude Code users run the one command shown on the same page instead.

3

Sign in and approve

Sajel opens in your browser. Sign in if you are not already, read what the app is asking for, and press Connect.

You can withdraw access at any moment under Settings, Connections, Connected apps. It takes effect immediately.

Connect from Claude Code

In your terminal (not the Claude chat window), run:

claude mcp add --scope user --transport http sajel <your Sajel address>

The address is shown in Settings, Connections. Then, inside Claude Code, type /mcp, pick sajel, and choose to authenticate — your browser opens on Sajel, you approve, and you are connected. Type /mcp again to confirm.

--scope user makes Sajel available in every project you open, rather than only the folder you happened to be in.

If you use Claude on your phone with /remote-control, it inherits this connection from your desktop session — there is no separate mobile setup.

Connect from claude.ai and Claude Desktop

Both are the same three steps.

1

Open the connector screen

Settings, then Connectors, then Add custom connector.

2

Paste the address

Name it Sajel and paste your Sajel address from Settings, Connections. That is the only field to fill in.

3

Sign in

A Sajel page opens in your browser. Sign in, check what is being granted, and press Connect. Claude picks it up on its own — with Desktop there is nothing to quit and reopen.

claude.ai runs in the cloud, so it needs your public Sajel address, not a local one.

On a Claude Desktop old enough to have no Connectors screen, install the Sajel extension from Settings, Connections instead: download it, double-click it, and Desktop asks for an API key in a form and keeps it in your operating system's keychain.

What Claude can do

AreaTools
Workspaces and baseslist_workspaces, create_workspace, list_bases, create_base
Boards and fieldslist_boards, create_board, get_board_schema, create_field, create_view, list_views
Recordslist_records, get_record, create_record, create_records, update_record, delete_record
Relationslink_records, unlink_records, get_linked_records
Automations and fileslist_automations, read_attachment
Everything elsesajel_request, a scoped passthrough for any supported endpoint

Four skills arrive as slash commands the moment you connect: build_app scaffolds a full working app, seed_data fills boards with realistic sample data, summarize_board reports on a board's contents, and use_attachments works with files on records.

Security model

Connecting by sign-in:

Claude acts as you and reaches exactly what you can reach, never more
You approve a named app and see what it is asking for before anything is granted
A connection approved as read-only cannot write, on any route
Nothing reusable is ever shown to you, so there is no credential to leak or paste by mistake
Disconnecting under Settings, Connections stops it immediately
Access tokens are short-lived and refresh in the background; a refresh token that is used twice revokes the whole connection

API keys, for scripts and tools that cannot sign in:

Hashed with SHA-256 and shown once, at creation
Scoped per resource and per action, down to read only
Limitable to specific workspaces or bases, and to one account
Expiry dates supported, revocable at any time

Both are confined to the data API. Neither can reach account, billing or admin routes, and neither can create or list API keys — only a signed-in person can.

Read about security across Sajel

Troubleshooting

Questions