Connect GitNative to your agent.

1. 1After publication, open Plugins in ChatGPT Work, Codex, or the Codex CLI plugin browser.
2. 2Search for GitNative, review the requested access, and install the plugin.
3. 3Complete the browser sign-in flow when GitNative asks you to connect a workspace.
4. 4Review or revoke the hosted connection from Settings → API Keys → Connected agents.
5. 5Start a new task, then invoke GitNative directly or ask the agent to use workspace context.

GitNative implements the hosted OAuth connection used by ChatGPT. A local GitNative MCP key cannot configure ChatGPT and should never be pasted into a chat or plugin prompt.

1. 1Export GITNATIVE_MCP_KEY in the shell or secure environment that launches Codex.
2. 2Add the server block to ~/.codex/config.toml for personal use or .codex/config.toml for a trusted repository.
3. 3Restart Codex or start a new session, then confirm the gitnative server and tools are available.

[mcp_servers.gitnative]
url = "https://api.gitnative.dev/mcp"
bearer_token_env_var = "GITNATIVE_MCP_KEY"

Codex reads the environment of the process that launches it. It does not automatically load an arbitrary .env.local file.

1. 1Export GITNATIVE_MCP_KEY before starting Claude Code.
2. 2Add the server to a repository .mcp.json or your preferred Claude Code configuration scope.
3. 3Restart Claude Code, approve the server if prompted, and verify that GitNative tools are connected.
4. 4Add CLAUDE.md beside AGENTS.md so Claude imports the shared repository instructions.

{
  "mcpServers": {
    "gitnative": {
      "type": "http",
      "url": "https://api.gitnative.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${GITNATIVE_MCP_KEY}"
      }
    }
  }
}

The public Claude marketplace package is pending review. Local MCP setup and local plugin testing are separate from marketplace approval.

1. 1Download the canonical GitNative SKILL.md into the skill directory supported by your agent.
2. 2Configure an HTTP MCP server at the production endpoint with Authorization: Bearer followed by your key.
3. 3Keep the key in the client secret store or launch environment, never in the skill or repository.
4. 4Verify the connected workspace before using read or write tools.

{
  "mcpServers": {
    "gitnative": {
      "type": "http",
      "url": "https://api.gitnative.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${GITNATIVE_MCP_KEY}"
      }
    }
  }
}

Configuration filenames and environment-variable expansion differ by client. Follow your client’s documentation instead of assuming it loads this example unchanged.