Althea MCP

Name: Althea MCP
Author: tiptreesystems

作者：tiptreesystems版本 0.2.1i★ –i在你的电脑上运行

注册名称io.github.tiptreesystems/althea-mcp

安装

概览

作者提供的说明（英文原文）

Connect coding agents to your Althea and, through her, a consent-first network of ML researchers.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "althea": {
      "command": "uvx",
      "args": [
        "althea-mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add althea -- uvx althea-mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "althea": {
      "command": "uvx",
      "args": [
        "althea-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "althea": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "althea-mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 tiptreesystems 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32691 个服务器的 0%
发布到注册中心的时间比此分类中其他 32691 个服务器的 71% 更新
基础检查结果等于或优于此分类中其他 32691 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Althea MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.2.1）于15天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Dialyne

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

Dialyne

作者：dialyne

Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Althea MCP

A direct line from your coding agent to your Althea.

Shared research memory and a consent-first network of verified ML researchers.

Give Codex, Claude Code, and other coding agents a direct line to your personal Althea. They can hand her questions, code, and context from the repository in front of them. Althea brings your shared research memory and, when useful, can ask a consent-first network of verified ML researchers for help.

Agents that can talk to each other. Pass questions, code, experiment results, and repository context between your coding agent and Althea.
Your Althea, with your context. MCP uses your existing account, profile, and long-term research memory.
A route into the researcher network. Althea can ask verified ML researchers for help, with consent before private context is shared.
Client-specific conversations. Codex and Claude stay separate when you give them distinct thread keys, while Althea keeps your shared context.
Work asynchronously. Wait for a reply, leave a message for longer work, or read the thread later.

Setup · Connect a client · First conversation · Tools · Security and privacy · Development

Setup

You need access to Althea and uv. Install Althea MCP from PyPI, then sign in with an emailed verification code:

uv tool install althea-mcp

althea-mcp setup

If the install succeeds but the command is not found, run uv tool update-shell and open a new terminal.

Run setup yourself in an interactive terminal. Enter your email and verification code there, not in an AI chat.

Connect your personal Althea

Email: you@example.com A verification code was sent to you@example.com. Verification code:

Althea MCP is ready. Credentials saved to ~/.config/althea-mcp/credentials.json

Setup follows the same account journey as the Althea web app:

Existing accounts receive a verification code by email.
Eligible new accounts are asked for a name, then receive a verification code.
Accounts that still need access are sent to the Althea application. Complete it, then run setup again.

The installed server starts without fetching code on every launch. Its tools still need a network connection to Althea. Upgrade the package later with:

uv tool upgrade althea-mcp

Connect an MCP client

Complete setup once, then add the local stdio server. Give each client a different thread key.

[!CAUTION]

This server can read private Althea history and send real messages. Register

it only in clients and projects you trust.

Codex

codex mcp add althea \

--env ALTHEA_THREAD_KEY=codex \ -- althea-mcp codex mcp list

codex mcp add writes to your user configuration. Equivalent ~/.codex/config.toml:

[mcp_servers.althea]

command = "althea-mcp"

[mcp_servers.althea.env] ALTHEA_THREAD_KEY = "codex"

Claude Code

claude mcp add althea \

-e ALTHEA_THREAD_KEY=claude-code \ -- althea-mcp claude mcp list

That command uses Claude Code's project-local scope. Add --scope user immediately before althea only if you want the server available in every project you open.

A user-wide manual entry under the top-level mcpServers object in ~/.claude.json looks like this:

"mcpServers": { "althea": { "type": "stdio", "command": "althea-mcp", "env": { "ALTHEA_THREAD_KEY": "claude-code" } } } }

Claude Desktop and other local clients

Find the installed command:

command -v althea-mcp

On Windows PowerShell:

(Get-Command althea-mcp).Source

GUI applications sometimes receive a smaller PATH than your terminal. If althea-mcp is not found, use the absolute path returned above:

"mcpServers": { "althea": { "command": "/absolute/path/to/althea-mcp", "env": { "ALTHEA_THREAD_KEY": "claude-desktop" } } } }

Restart the client after changing its MCP configuration.

Start a conversation

Try one of these prompts in your MCP client:

Ask my Althea whether anyone in the researcher network has worked on this

failure mode. Share only the sanitized summary below: [summary]

Send this context to my Althea without waiting for a reply:

The latest experiment rules out the data-loader hypothesis. The remaining failure starts after gradient accumulation.

Check whether my Althea has replied in the MCP thread.

Messages continue the configured thread. They are real messages to your personal Althea and may cause her to begin work.

Tools

Tool	What it does
`ask_althea(message)`	Sends a message and uses a 120-second polling window by default for the first reply. If the window expires, the work may still continue.
`send_message_to_althea(message)`	Sends a message immediately and returns a receipt without waiting. Use it for context, notes, and longer requests.
`get_althea_messages(sender=None, limit=10)`	Returns 1 to 100 recent messages in chronological order. Optionally filter by `user`, `assistant`, or `system`.
`search_althea_conversations(query=None, limit=10)`	Finds conversations across the user's Althea account by title or topic. With no query, returns recent conversations.
`get_althea_conversation_log(conversation_id, limit=100)`	Returns the last 1 to 100 messages from any owned conversation in chronological order, together with its total message count.

The two send tools are marked as state-changing. Conversation search and message retrieval are read-only. The current tool surface is text-only. It does not expose attachments or other Althea artifacts.

How it works

Codex / Claude Code / another coding agent

│ local stdio ▼ Althea MCP │ HTTPS ▼ your Althea │ ├── your profile and long-term research memory ├── a persisted conversation for this thread key └── a consent-first network of verified ML researchers

Althea MCP is a small public adapter. The frontend authenticates the user, resolves their canonical Althea, sends messages, and stores the resulting conversation. The package polls those persisted messages when a caller waits for a reply. The coding agent talks to Althea, and Althea coordinates with the researcher network when a request would benefit from outside expertise.

Sign-in and sessions

Setup creates a normal Althea usage session:

The access session lasts 7 days.
Its rotating refresh-token family lasts 14 days from sign-in.
Access tokens refresh automatically before expiry.
A cross-process lock lets several local MCP clients share the credential file without racing refresh-token rotation.
When the session expires or is revoked, run althea-mcp setup again in a separate terminal. Running MCP processes reload the replacement credentials.
Signing in again rotates credentials only. It does not replace conversation history when the Althea account and ALTHEA_THREAD_KEY stay the same.

Credentials are stored as plaintext JSON at ~/.config/althea-mcp/credentials.json. On operating systems that support Unix file modes, the credential file is set to 0600. A parent directory created by Althea MCP is requested as 0700; check the permissions yourself when using a pre-existing custom directory.

Security and privacy

Messages sent through these tools are persisted in your Althea account, like messages from Althea's other channels.
The local stdio process sends messages and credentials to Althea over HTTPS. Even with local transport, conversation data leaves your machine.
The connected MCP host and model can see tool arguments and replies. They may retain that data under their own privacy and retention policies.
When Althea asks the researcher network for help, she requests consent before sharing information drawn from a private conversation.
The package sends access credentials only to the Althea origin they were issued for. Changing ALTHEA_APP_URL requires a new setup.
The refresh token is sent only to the session rotation endpoint.
Email verification codes and the credential file are secrets. Never paste them into an AI chat, terminal transcript, issue, or pull request.
To remove the local session, close MCP clients and delete the credential file. This forgets the session on that machine. Contact Tiptree if a copied session must also be revoked.

Please report vulnerabilities using the security policy.

Configuration

Most users only need althea-mcp setup and a client-specific thread key.

Environment variable	Default	Purpose
`ALTHEA_APP_URL`	`https://althea.tiptreesystems.com`	Althea API origin. Saved credentials are bound to it. Plain HTTP is accepted only for loopback development.
`ALTHEA_PUBLIC_SITE_URL`	`https://tiptreesystems.com`	Base URL for terms, privacy, and access requests. Dev Althea selects `https://dev.tiptreesystems.com` automatically.
`ALTHEA_THREAD_KEY`	`mcp`	Stable conversation identifier. Use 1 to 128 letters, digits, dots, underscores, colons, or hyphens, starting with a letter or digit.
`ALTHEA_MCP_CREDENTIALS_FILE`	`~/.config/althea-mcp/credentials.json`	Override the local credential path.
`ALTHEA_MCP_HTTP_TIMEOUT`	`60`	HTTP timeout in seconds.
`ALTHEA_MCP_POLL_INTERVAL`	`2`	Delay between response polls in seconds.
`ALTHEA_MCP_POLL_TIMEOUT`	`120`	Maximum wait for `ask_althea` in seconds.
`ALTHEA_MCP_LOG_LEVEL`	`WARNING`	Python log level.

Setup also accepts --credentials-file to override the credential path and --no-browser to print an access-request URL without opening it.

Troubleshooting

`Althea MCP is not configured`

Run althea-mcp setup in a terminal, then restart the MCP client.

`Your Althea MCP sign-in has expired or was revoked`

Run setup again. The refresh-token family has a 14-day absolute lifetime.

Saved credentials are bound to another URL

Run setup with the same origin the MCP client will use:

althea-mc

只显示了开头部分；其余内容请在仓库中阅读

Althea MCP

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

Dialyne

作者的 README

Setup

Connect an MCP client

Codex

Claude Code

Claude Desktop and other local clients

Start a conversation

Tools

How it works

Sign-in and sessions

Security and privacy

Configuration

Troubleshooting