Remix MCP Server

A Model Context Protocol (MCP) server for transferring conversation context between AI chat sessions. This server maintains a tree structure of conversations with their message history, allowing you to branch conversations and search through them.

Features

- Conversation Branching: Create new conversations that branch from existing ones, forming a tree structure
- Message Storage: Save chat messages with proper ordering (using a linked list with prev/next message IDs)
- Tree Navigation: View the entire conversation tree or subtrees
- Full-Text Search: Search messages across parent or child conversations using PostgreSQL's powerful text search
- Persistent Storage: Uses PostgreSQL for reliable, scalable storage

Installation

``bash
npm install
npm run build
`

Configuration

The server connects to PostgreSQL using connection parameters that can be specified in three ways (in order of precedence):

1. Command-line arguments
2. Environment variables
3. Default values

$3

| Parameter | CLI Argument | CLI Short | Environment Variable | Default |
|-----------|--------------|-----------|---------------------|---------|
| Host | --host | - | PGHOST | localhost |
| Port | --port | -p | PGPORT | 5432 |
| User | --user | -U | PGUSER | postgres |
| Password | --password | -W | PGPASSWORD | (empty) |
| Database | --database | -d | PGDATABASE | remix_mcp |
| Connection String | --connection-string | - | - | - |

Note: If --connection-string is provided, it takes precedence over individual parameters.

Security Warning: Passing passwords via command-line arguments (--password) or connection strings can expose them in process listings, shell history, and configuration files. For production deployments:
- Use environment variables (PGPASSWORD) instead
- Use PostgreSQL's .pgpass file for secure credential management
- Ensure configuration files with passwords have restricted permissions (chmod 600)

$3

`json
"servers": {
"remix": {
"command": "npx",
"args": [
"remix-mcp",
"--host", "localhost",
"--port", "5432",
"--user", "myuser",
"--password", "mypassword",
"--database", "remix_mcp"
]
}
}
`

Or using a connection string:

`json
"servers": {
"remix": {
"command": "npx",
"args": [
"remix-mcp",
"--connection-string", "postgresql://myuser:mypassword@localhost:5432/remix_mcp"
]
}
}
`

$3

`json
{
"mcpServers": {
"remix": {
"command": "npx",
"args": [
"remix-mcp",
"--host", "localhost",
"--port", "5432",
"--user", "myuser",
"--password", "mypassword",
"--database", "remix_mcp"
]
}
}
}
`

Or using a connection string:

`json
{
"mcpServers": {
"remix": {
"command": "npx",
"args": [
"remix-mcp",
"--connection-string", "postgresql://myuser:mypassword@localhost:5432/remix_mcp"
]
}
}
}
`

$3

You can also set environment variables:

`bash
export PGHOST=localhost
export PGPORT=5432
export PGUSER=myuser
export PGPASSWORD=mypassword
export PGDATABASE=remix_mcp
npx remix-mcp
`

Tools

$3

Save chat messages to create a new conversation or branch from an existing one.

Parameters:
- new_conversation_id (required): Unique ID for the new conversation
- title (required): Title for the conversation
- task_description (required): Description of the task or context
- messages (required): Array of message objects with:
- author: Either "User" or "Copilot"
- payload: The message content
- old_conversation_id (optional): Parent conversation ID to branch from

Example:
`json
{
"new_conversation_id": "conv-123",
"title": "Implementing User Authentication",
"task_description": "Discussing best practices for OAuth2 implementation",
"messages": [
{
"author": "User",
"payload": "How do I implement OAuth2 in Node.js?"
},
{
"author": "Copilot",
"payload": "Here are the steps for implementing OAuth2..."
}
],
"old_conversation_id": "conv-100"
}
`

Quick prompt (usage guide):

- Remix this conversation: “remix this conversation, Save all the messages in this chat that you remember. New id: , task_description: , title: