Skip to main content
Glama
misternay

Background AI Chat MCP Server

by misternay

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BAC_HOSTNoHTTP/SSE bind address127.0.0.1
BAC_PORTNoHTTP/SSE port3456
BAC_AUTH_KEYNoBearer token for HTTP/SSE mode
BAC_DATA_DIRNoRoot data directory~/.bagidea
BAC_TRANSPORTNoTransport mode (stdio or http-sse)stdio
BAC_REDACT_PIINoOpt-in PII redactionfalse
BAC_SAKANA_URLNoSakana chat URLhttps://chat.sakana.ai/
BAC_MAX_SESSIONSNoMax concurrent sessions5
BAC_IDLE_TIMEOUT_MSNoIdle timeout before auto-close (15 min)900000
BAC_BROWSER_HEADLESSNoRun Chrome headlesstrue
BAC_ALLOWED_USE_CASESNoComma-separated use casespersonal,internal

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
session_openA

Open a persistent Sakana chat session backed by headless Chrome. First call requires tosAccepted:true (machine-wide ack thereafter). Returns sessionId + rate limit. Anonymous mode only in P1.

session_closeA

Close a Sakana chat session and release its browser context. keepHistory:true (default) retains state.json + cookies for reuse.

session_listA

List all known Sakana chat sessions (active and idle).

chat_sendA

Send a message to an open Sakana chat session and receive the streamed reply. Incremental tokens are emitted as MCP logging notifications; the tool result carries the final answer. Pass signal:"abort" to interrupt.

chat_interruptA

Interrupt an in-flight Sakana chat send. Clicks the page stop button and returns partial text. The stream also terminates via the AbortSignal on the original chat_send call.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a distinct purpose: chat_interrupt interrupts a send, chat_send sends a message, session_close closes a session, session_list lists sessions, and session_open opens a session. No overlapping functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, with 'chat_' and 'session_' prefixes clearly grouping related operations.

Tool Count5/5

Five tools cover the essential operations for managing chat sessions and messages, making the surface well-scoped without unnecessary redundancy.

Completeness5/5

The tool set provides complete CRUD-like lifecycle for sessions (open, close, list) and chat interactions (send, interrupt), leaving no obvious gaps for the intended domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues