37soul Mcp

37Soul

English · 简体中文 · 日本語

Give your agent a lasting identity, with long-term preferences and experience that travel across sessions and tools.

The local runtime connects Claude Code, Codex, OpenCode, Hermes, and Pi. You can start using a Soul on your machine alone. Only after you log in and explicitly authorize sync do the selected categories of long-term assets sync to 37Soul.

Install

You need macOS or Linux, Node.js 18 or later, and at least one supported host that can already use a model successfully. Linux also needs a working systemd user session (systemctl --user); containers or servers without one cannot start the background service this way.

curl -fsSL https://37soul.com/install.sh | bash

The installer downloads and verifies the runtime, installs managed configuration for detected hosts, configures and attempts to start the background service, and creates a local profile. Run 37soul doctor to confirm that the service started successfully. Installation contacts download servers; it does not sign you in or upload conversations. To preview the changes first, run:

curl -fsSL https://37soul.com/install.sh | bash -s -- --plan

Already have a Soul on the website?

37soul login

1. Open the authorization link shown in your terminal and sign in to your own account.
2. Check the short code, select an existing Soul, then approve the device.
3. Once the terminal shows Soul restored:, complete the setup for your host below and open a new session.

If you did not select a character, logging in does not mean a Soul has been restored. Select your own Soul and run 37soul login again.

Create a Soul locally first

Confirm the name, sex (male/female/other), age (16–65), character (at least 50 characters) and photo with the human. Replace all variables with those confirmed choices; do not invent a persona. Replace /path/to/photo.jpg with the actual local image path before running:

Every NEW local Soul requires a real local image passed with --avatar: JPEG, PNG or WebP, at most 5 MiB; no default avatar is accepted. The CLI copies the selected file into the managed local profile, so moving or deleting the original does not break the photo. On the website, upload your own photo or generate an AI photo. Sign up and confirm your email: the existing signup bonus is 18 credits = 3 images at 6 credits each; this is not an additional grant. Fully offline creation cannot spend cloud credits. If you have no image, use the website to generate and download one after signup and email confirmation, then pass that actual local file to --avatar. Ask the human to confirm the image and all profile choices. Cloud sync remains optional: login, explicitly authorize identity, then sync. Initial registration sends the profile and photo together. Restoring an existing website Soul that already has a real photo via login does not require a new photo.

SOUL_NAME='<confirmed name>'SOUL_SEX='<confirmed male, female or other>'SOUL_AGE='<confirmed integer 16–65>'SOUL_CHARACTER='<confirmed character of at least 50 characters>'37soul soul create \  --avatar '/path/to/photo.jpg' \  --name "$SOUL_NAME" \  --sex "$SOUL_SEX" \  --age "$SOUL_AGE" \  --character "$SOUL_CHARACTER"37soul soul list

Copy the Soul UID from the creation result and replace the variable value below:

SOUL_UID='paste the actual Soul UID here'37soul soul select "$SOUL_UID"

Complete your host's setup and open a new session to start using the Soul locally. When you want to sync to the website or another machine:

37soul login37soul soul select "$SOUL_UID"37soul soul authorize "$SOUL_UID" --categories identity,relationship,experience37soul sync

Authorization publishes that Soul's character profile on the website; it does not make private chats or personal memories public. --categories replaces this device's complete authorization set for the Soul. It does not add categories incrementally.

Complete your host's setup

Each host still needs working model authentication or configuration. 37Soul does not supply or automatically replace your host's model credentials.

Check that it is working

37soul status37soul doctor37soul soul list

In a new session, explicitly state a stable collaboration preference, such as “In future, when giving me implementation advice, list actionable steps before explaining the reasons.” The runtime extracts long-term assets after a completed turn. Temporary requests and one-off tasks do not necessarily belong in long-term memory.

37soul recall "collaboration"

Local use does not require sync. After logging in and authorizing this Soul, run 37soul sync to check cloud synchronization.

Extraction uses the host model and may retry after a failure, consuming additional host quota. Completion time also depends on the model and network. In doctor, “installed,” “waiting for the host to load,” and “local events observed” are different states. Follow the guidance shown beside each status; a file being written does not prove the host has loaded it.

After changing an identity or long-term asset on the website, run this first if you want the correction available in your next session immediately:

37soul sync

Confirm there are no sync errors, then open a new host session. Background sync runs periodically, but website changes do not instantly rewrite an already open session. Content already included in an old session's context cannot be remotely withdrawn either.

Data and authorization

• The local runtime does not upload raw sessions, code, or tool logs to 37Soul's cloud. The local runtime reads a bounded range of session source material and uses the host's configured model to extract long-term assets. Model-service data handling follows your host's and model provider's settings; this does not mean the entire process is offline.
• Only explicitly authorized identity, relationship, and experience assets sync to 37Soul. Logging in does not automatically authorize uploads of local content that has not been authorized.
• Login credentials are bound to the server, profile, account, device, and host. Changing servers requires a fresh login and a separate profile. Accounts with the same identifier on two servers are not automatically merged.
• After you revoke a device on the website, its next connection to the server is rejected and downloaded private caches are cleared. Locally created Souls, unsynced assets and original session files are retained; confirmed synced asset copies are cleared. An offline device cannot immediately learn about a change that just happened on the server.

Troubleshooting

37soul pause37soul resume37soul uninstall

These commands pause, resume, and uninstall the local runtime. Uninstall removes managed integrations while preserving local Souls, assets, and unsynced data.

Remote MCP

Clients that cannot run the local runtime can connect to https://37soul.com/mcp to operate their own platform account. This is a separate integration path from automatic capture through local hooks.

Development and distribution

User installation is distributed only through GitHub Releases and the website's install.sh, not npm. See the developer documentation for build, test, version, and release evidence. Release checks do not automatically publish a release.