Chatgpt Mcp Connector Setup

# ChatGPT MCP Connector Setup

## Purpose and Boundary

This guide describes how to connect ChatGPT to the existing local Journal Mirror MCP server for cautious private testing. The public repository remains the reusable control plane; the initialized private vault remains the user-controlled data plane outside Git.

This is setup documentation only. It does not add a connector configuration, reachable endpoint, tunnel profile, hosted deployment, credentials, or private data. ChatGPT cannot connect directly to this repository's local stdio command. It needs a supported reachable MCP transport supplied by a separately reviewed bridge, tunnel, or deployment.

ChatGPT product availability and labels change. Current OpenAI guidance says full write-capable MCP is rolling out to Business and Enterprise/Edu on the web, while Pro custom MCP access is limited to read/fetch. Workspace administrators may also restrict Developer mode. Verify the controls visible in the current account before relying on any write workflow. See OpenAI's [Developer mode guide](https://platform.openai.com/docs/guides/developer-mode) and [current ChatGPT help article](https://help.openai.com/en/articles/12584461-developer-mode-and-full-mcp-connectors-in-chatgpt-beta).

## Prerequisites

- A supported Python environment with `python -m pip install -r requirements.txt` completed.
- A private vault initialized outside this repository with `scripts/init-private-vault.py`.
- The minimal MCP server starts locally against a placeholder or user-supplied private path.
- Developer mode/custom app access is available and allowed by the ChatGPT plan and workspace.
- The tester understands that Developer mode can expose private reads and consequential writes, and that model or prompt-injection errors remain possible.
- A separately configured reachable MCP path is available:
  - preferred: Secure MCP Tunnel, when available to the account/workspace;
  - alternative: an intentionally reviewed, temporary HTTPS development tunnel; or
  - future/advanced: an authenticated private or hosted deployment after security review.

Do not put a real vault path, URL, tunnel identifier, profile, token, or connector export in this repository.

## 1. Check the Local Server

Use a private vault outside the repository. These commands contain generic placeholders; do not copy a real user path into public documentation or issues.

PowerShell: