ChatGPT supports MCP through ChatGPT Apps (workspace feature) and the OpenAI Agents SDK. Git Mind MCP works with both.
- ChatGPT Business, Enterprise, or Edu (for workspace Apps)
- Node.js 22+ (for running Git Mind)
- A Git repository (your project)
ChatGPT Apps let workspace admins add MCP servers for the whole workspace.
- Workspace admin access
- Developer mode enabled: Workspace Settings → Permissions & Roles → Developer mode
- MCP server reachable (see below)
Git Mind runs as a local stdio server. To use it with ChatGPT Apps you need to expose it over HTTP. Options:
- Streamable HTTP — Run a bridge that speaks MCP over HTTP (e.g. mcp-http-bridge or similar)
- Self-hosted MCP over HTTP — Wrap Git Mind in an HTTP transport
ChatGPT Apps expect an HTTP endpoint. For local stdio servers like Git Mind, you typically run a local HTTP proxy that spawns the stdio process and forwards requests.
- Go to Workspace Settings → Apps → Create
- Configure the app with:
- MCP server URL (your HTTP endpoint)
- Authentication (if required)
- Publish the app for the workspace
See OpenAI’s MCP documentation for current details.
The OpenAI Agents SDK supports MCP servers, including stdio-based ones like Git Mind.
import { McpClient } from "@openai/agents";
const client = await McpClient.fromProcess({
command: "npx",
args: ["-y", "git-mind-mcp", "/path/to/repo"],
});
// Use client to call Git Mind tools
const result = await client.callTool("get_status", {});Use the SDK when building custom agent applications that need Git operations.
For the simplest setup, use Cursor or Claude Desktop with Git Mind:
- Cursor Setup —
.cursor/mcp.jsonor UI settings - Claude Desktop Setup —
claude_desktop_config.json
Both support local stdio MCP servers directly, with no HTTP bridge.
- Safety Model — Config, protected branches, guardrails
- OpenAI MCP Docs