althea-mcp

althea-mcp

Connects your personal Althea AI assistant to MCP-compatible tools like Codex and Claude, allowing you to send messages and retrieve conversation history.

Category
Visit Server

README

<p align="center"> <a href="https://www.python.org/"><img src="https://img.shields.io/badge/Python-3.11%2B-3776AB?logo=python&logoColor=white" alt="Python 3.11+" /></a> <a href="https://modelcontextprotocol.io/"><img src="https://img.shields.io/badge/MCP-server-7C3AED" alt="MCP server" /></a> <a href="https://github.com/tiptreesystems/althea-mcp/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-green.svg" alt="MIT license" /></a> </p>

Althea MCP

Bring your personal Althea into Codex, Claude, and other MCP-compatible tools.

Althea MCP talks to the main Althea application. It uses your existing account and canonical Althea—with the same dossier and long-term memory you use through the web, email, SMS, and other channels. It creates a dedicated MCP conversation thread, just as each other channel has its own thread.

It does not use the retired Platform API, create an account in a parallel auth database, or spin up a separate blank agent.

Setup

Run one command:

uvx --from git+https://github.com/tiptreesystems/althea-mcp.git althea-mcp setup

The command asks for your email and lets the Althea frontend determine the correct journey:

  • Existing account: Althea emails a verification code.
  • Eligible new account: the CLI asks for your name, creates the account, and emails a verification code.
  • Access still required: the CLI opens the existing Althea access-request page. Complete that journey, then rerun the same setup command.

After verification, setup creates a dedicated, 90-day MCP API key and stores it at ~/.config/althea-mcp/credentials.json with user-only file permissions where the operating system supports them. The key is scoped to the Althea MCP frontend channel; it is not a general-purpose Althea or ACTX credential. Setup also schedules the same idempotent dossier setup used after web sign-in. It does not persist the interactive login token or print the API key. Optional onboarding details can still be completed in the Althea web app.

Once the package is on PyPI, the setup command becomes:

uvx althea-mcp setup

Connect an MCP client

Run setup once before adding the server.

Codex

codex mcp add althea -- uvx --from git+https://github.com/tiptreesystems/althea-mcp.git althea-mcp

Or add this to ~/.codex/config.toml:

[mcp_servers.althea]
command = "uvx"
args = ["--from", "git+https://github.com/tiptreesystems/althea-mcp.git", "althea-mcp"]

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

Claude Code

claude mcp add --scope user althea -- uvx --from git+https://github.com/tiptreesystems/althea-mcp.git althea-mcp

Or add this under the top-level mcpServers object in ~/.claude.json:

{
  "mcpServers": {
    "althea": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/tiptreesystems/althea-mcp.git",
        "althea-mcp"
      ],
      "env": {
        "ALTHEA_THREAD_KEY": "claude-code"
      }
    }
  }
}

Claude Desktop and other local MCP clients

Use the same stdio command:

{
  "mcpServers": {
    "althea": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/tiptreesystems/althea-mcp.git",
        "althea-mcp"
      ]
    }
  }
}

Use a distinct ALTHEA_THREAD_KEY for each MCP client if you run several clients concurrently.

Tools

  • ask_althea(message) Sends a real message to your Althea and waits for her response.
  • send_message_to_althea(message) Sends a message without waiting, for asynchronous requests or context.
  • get_althea_messages(sender=None, limit=10) Retrieves recent messages from the configured MCP thread.

Configuration

  • ALTHEA_API_KEY Overrides the API key in the credentials file.
  • ALTHEA_APP_URL Defaults to https://althea.tiptreesystems.com.
  • ALTHEA_THREAD_KEY Stable conversation-thread identifier. Defaults to mcp.
  • ALTHEA_MCP_CREDENTIALS_FILE Overrides ~/.config/althea-mcp/credentials.json.
  • ALTHEA_MCP_HTTP_TIMEOUT HTTP timeout in seconds. Defaults to 60.
  • ALTHEA_MCP_POLL_INTERVAL Response polling interval in seconds. Defaults to 2.
  • ALTHEA_MCP_POLL_TIMEOUT Maximum time ask_althea waits for a response. Defaults to 120.
  • ALTHEA_MCP_LOG_LEVEL Defaults to WARNING.

Environment variables are useful for automation, but the normal user journey is simply althea-mcp setup; no API key needs to be pasted into an MCP config.

Architecture

This repository is intentionally independent of the private tiptree-clients package. It is a thin public adapter over frontend-owned routes:

Capability Frontend route
Unified sign-in/sign-up detection POST /otp/signin
CLI OTP verification POST /mcp/auth/otp/signin/verify
Idempotent profile/dossier setup POST /create_dossier
Create and manage MCP-scoped keys /mcp/api-keys
Send to the user's Althea POST /mcp/threads/{thread_key}/messages
Read the MCP conversation GET /mcp/threads/{thread_key}/messages

The stored key goes only to the frontend MCP routes. The frontend authenticates it through a service-only auth-server exchange and receives a two-hour delegated user token. That delegated token—not the MCP key—is sent to ACTX. The duration covers queued wakes and code-assistant work. The frontend uses the token to resolve the main user, provision or find that user's canonical Althea, and own the MCP ChannelSession.

Creating, listing, or revoking MCP keys requires an interactive login token; an MCP key cannot mint or manage keys. Revoking the key deactivates the usage session behind both the key and any delegated token. The MCP package does not know about ACTX internals.

Local development

git clone https://github.com/tiptreesystems/althea-mcp.git
cd althea-mcp
uv sync --extra dev
uv run pytest
uv run ruff check .
uv run althea-mcp setup --app-url http://localhost:8080

Running althea-mcp with no subcommand starts the stdio MCP server. The equivalent explicit command is althea-mcp serve.

Distribution

Althea MCP is a local stdio server. It can be published to PyPI and submitted to the official MCP Registry. Anthropic's connectors directory is for remote MCP servers, so this local package is not a fit for that directory unless a hosted transport is added later.

License

MIT. See the license.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured