Account Namespace

Integration Identityaccount · core

Category: core
Namespace: account

Change your own Oddlynew account, the person this connection acts for, without opening the web app. Today that is one thing: the name other people see on your documents, comments and memberships.

Integration CapabilityupdateMyName · write

Access: write
Method: updateMyName
Side Effect: Yes

Sets your account name and returns the stored name as { name }. Leading and trailing spaces are removed first; the result must have 1 to 100 characters and no NUL character. The name belongs to your account, not to an organization, so it changes in every organization you belong to, even when this connection is granted for only one. Setting the name you already have is safe and returns it again.

Limitations

There is one method. It renames only the account behind the connection: it takes no user id and cannot rename another member, an agent or an organization. Your email address, sign-in methods and API keys are not part of this namespace. An organization's automation or site key acts as an account the organization manages and is refused with personal_account_required. A connection without mcp:write is refused with missing_write_scope. A name outside the rule is refused by parameter validation before anything is written, and the message names the broken rule (Expected string, Expected a value with a length of at least 1, at most 100, No NUL character). Other failures are answered with a generic line that tells you to retry later, never with the reason, because a database error could repeat the submitted name. The comment lists of up to 500 documents in which you wrote comments are refreshed with the new name at once; beyond that, and where a refresh fails, a document's comment list shows the old name until it is next loaded.

Usage

Inside run, call account.updateMyName({ name }) with the full new name as a string; there is no operationId, no organizationId and no pagination. The call is idempotent: repeating it with the same name is safe. Read the current name first with orientation.whoami(), whose name field is the same value, and read it again afterwards if you want to show the person the result. Pass exactly one field: an extra field such as userId fails as an unknown parameter.

Authorization

Needs mcp:write and a person's own connection: an OAuth connection or a personal API key. Being a member of an organization is not required and no organization role is checked, because the account belongs to the person, not to an organization. An organization's automation or site key cannot use it, whatever scopes it carries.

Composition

orientation.whoami returns the name before and after the change. Documents, comments and member lists in every organization show the new name. The same change is available over the HTTP API as PUT /v1/orgs/{orgId}/me/name with a personal key that has read and write access to that organization and the API feature; the organization in the path only admits the call, and the name still changes everywhere. A person can also change it in the web app: account menu, Account settings, Profile.

Account

What it does

Use account.updateMyName when a person asks their agent to fix how they appear, for example after signing up with an email address as their name, or after a name change. The agent does not need to know which organization the person is working in: the name lives on the account, so it changes in every organization at once.

Change the name

Inside run:

const before = (await orientation.whoami()).name

const { name } = await account.updateMyName({ name: "  Ada Lovelace  " })
// name === "Ada Lovelace": leading and trailing spaces are removed

return { before, after: name }

The returned name is what was stored, after trimming. Show that value to the person rather than the string you sent.

When the call is refused

Validation runs before anything is written, so a refused call changed nothing.

Expected string: the name was not a string. Pass it as text.
Expected a value with a length of at least 1 or at most 100: the name is empty after trimming, or longer than 100 characters. Ask the person for a shorter or non-empty name.
No NUL character: the name contains a NUL character, usually from a copied or generated string. Remove it.
McpAuthorizationError (missing_write_scope): the connection can only read. The person reconnects with write access.
McpAuthorizationError (personal_account_required): the connection is an organization's automation or site key. Those keys act for an account the organization manages and have no person behind them. Use the person's own OAuth connection or personal API key.

Any other failure comes back as a generic line asking you to retry later. Retry once; repeating the same name is safe.

When account is not the answer

To see who you are acting as, call orientation.whoami. There is no separate name per organization: members appear under their own account name everywhere. To manage an organization's members or their roles, use the organizations namespace. For exact parameters, live server validation inside run is authoritative.