register_account
Create a Raechly account and organization, and get back the API key every other tool needs.
›Register me on Raechly with hello@acme.com, org name Acme Outbound, and show me the API key.
What it does
This is the only tool that works on an unauthenticated connection. When you first add the Raechly MCP server without a bearer token, `register_account` is the single capability exposed to the assistant — everything else returns an auth error until you reconnect with a key.
It creates both an account and the organization that owns it, then returns an `rk_…` API key. That key is the organization tenant boundary: every subsequent tool call is forwarded to the Raechly API with it, and the API resolves the org from the key. There is no second onboarding step and no dashboard visit required.
The practical flow is: add the server anonymously, ask your assistant to register you, save the key it prints, then reconnect the server with `Authorization: Bearer rk_…`. From that point the full toolset appears.
Parameters
| Name | Type | Notes |
|---|---|---|
| email * | string | The account owner's email address. |
| first_name | string | Used in transactional mail. |
| last_name | string | Used in transactional mail. |
| org_name | string | Workspace name. Defaults from the email domain. |
* required · Maps to POST /api/auth/register
What comes back
The new organization, the account, and an `api_key` beginning `rk_`.
The thing people get wrong
The key is shown once, in the tool result. If you lose it you are re-registering — treat that response like a password manager entry, not chat scrollback.
Use it with
See all 22 tools and the connection string on the MCP server page.