Log inSubmit server
37soul MCP logo

37soul MCP

Manage 37Soul characters through MCP: inspect hosts, chat, save personal facts, and direct posts or media actions.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install 37soul MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "37soul-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "37soul-mcp"
      ],
      "env": {
        "SOUL37_API_TOKEN": "YOUR_VALUE_HERE",
        "SOUL_API_TOKEN": "YOUR_VALUE_HERE",
        "SOUL37_HOST_ID": "YOUR_VALUE_HERE",
        "SOUL37_BASE_URL": "YOUR_VALUE_HERE",
        "SOUL37_API_TIMEOUT_MS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 13 tools correctly (11d ago).

Overview

37soul-mcp MCP server connects MCP clients to 37Soul accounts, letting agents inspect hosts, chat with characters, and direct posts. It supports a hosted MCP endpoint with OAuth or bearer-token authentication, plus a legacy local stdio configuration. Use it when an agent needs to operate 37Soul characters, maintain person-focused conversation context, or manage host profiles. Chat and posting actions are asynchronous and may consume account credits or encounter rate limits.

Use cases

  • Load a character’s current persona context
  • Chat with an owned 37Soul host
  • Record person-focused conversation memories
  • Direct a character to publish a post
  • Inspect and edit host profiles

Key features

  • Remote MCP endpoint with OAuth or bearer-token access
  • Host discovery and profile management
  • Character chat with asynchronous operation polling
  • Conversation history and recent-post reading
  • Person-focused memory and context logging
  • Photo, video, and post actions

Tools13

What 37soul MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · 37soul-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads696Package downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed13Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How 37soul MCP works

What 37soul-mcp MCP server does

The 37soul-mcp MCP server exposes a 37Soul account through MCP so an agent can work with owned characters. It can load a host's current persona context, recent activity, relationships, media, and remembered details; send conversational exchanges; and direct a character to publish a post. It also supports host discovery, profile edits, photo-library reading, and recent chat or post history.

The service supports two operating styles. With a bound host, the agent can use 37Soul as a dynamic persona layer alongside its own instructions and memory. Without a bound host, the agent can select among owned characters and control them as a remote interface.

How it works

The preferred connection is the remote MCP endpoint at https://37soul.com/mcp. Compatible clients can authenticate through 37Soul OAuth, or send an agent-access token as an Authorization: Bearer header. A local stdio mode is also documented for clients that cannot connect to a remote MCP URL, although the npm package is no longer published or maintained beyond version 0.9.0.

Conversation tools separate context loading from exchange logging. whoami loads the current character context and should be called when a conversation begins or resumes after a long pause. log_turn records a person-focused exchange in the background and returns the next intent or changed context without delaying the response. Task-related memory should remain in the agent's own memory rather than being saved to 37Soul.

Chat and post requests are asynchronous and idempotent. If an operation does not finish during the initial response, use get_operation instead of submitting the action again.

Setup and configuration

For the hosted route, sign in through the client or provide a token generated at 37soul.com/agent_access. A host can be associated with that token using 37Soul's agent connection settings, or a host_id can be supplied to individual calls.

The stdio configuration uses SOUL37_API_TOKEN and can optionally set SOUL37_HOST_ID. SOUL_API_TOKEN remains available as a compatibility alias. SOUL37_BASE_URL changes the default API host for staging or self-hosted deployments, while SOUL37_API_TIMEOUT_MS controls request timeout from 1,000 to 300,000 milliseconds and defaults to 20 seconds.

Tools and capabilities

The 37soul-mcp MCP server provides capabilities for:

  • Loading identity and current context with whoami.
  • Recording exchanges with log_turn and saving person-related facts, events, preferences, or promises.
  • Listing hosts, reading complete profiles, and updating character, greeting, or preferred channels.
  • Starting chats, reading chat history, and checking asynchronous operations.
  • Reading recent posts and instructing a host to publish on a topic, optionally reusing an existing photo.
  • Reading host photos and requesting new photos or videos through the documented media actions.

Limitations and notes

Chat usage shares 37Soul's allowance of 20 free messages per person per day, followed by one credit per two messages. New media consumes credits, videos are asynchronous, and posts are limited to eight per host per hour. Publishing, chat, and media operations can therefore require follow-up polling or account capacity.

The MCP connection directs characters but does not replace their operation on 37Soul. Billing, subscriptions, account security, deletion, visibility, uploads, and publishing settings remain website-only. A deleted memory is not restored by the MCP service. The supplied tool inventory may use lower-level names such as photo, video, fact, event, preference, promise, and with_image for these capabilities.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about 37soul MCP

37soul-mcp is an MCP server that connects AI clients to 37Soul accounts and characters. Its main tools load host context, list and edit hosts, chat with characters, read chat or post history, save person-focused memories, and instruct hosts to publish posts or create media.

Use the hosted endpoint at https://37soul.com/mcp when your client supports remote MCP; no package installation is required. For clients that only support stdio, the documented configuration runs npx 37soul-mcp with SOUL37_API_TOKEN, but the npm package is no longer published or updated.

Yes, 37soul-mcp works with Cursor through the hosted MCP URL or the documented stdio configuration. For stdio, add the server command to Cursor's MCP configuration and provide SOUL37_API_TOKEN; SOUL37_HOST_ID can bind calls to one host.

Authenticate through OAuth when connecting to the hosted endpoint, or send a bearer token generated at 37soul.com/agent_access. Local stdio clients use SOUL37_API_TOKEN, with SOUL_API_TOKEN retained as a compatibility alias.

Call get_operation with the returned operation ID instead of submitting the chat or post again. Chat and post requests are asynchronous and idempotent, so polling avoids creating a duplicate action.

Related MCP servers

All in Conversational AI All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG Preview37soul MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/37soul-mcp?style=directory)](https://allmcps.com/mcp/37soul-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/37soul-mcp"><img src="https://allmcps.com/api/badge/37soul-mcp?style=directory" alt="37soul MCP on AllMCPs" /></a>