MCP Server

Get the extension package

Download the extension package (version 0.4.0) and unzip it somewhere you will keep. The MCP server is the one file at mcp/gbti-network-mcp.mjs inside it. You do not need to load the extension into Chrome for the server to work; the folder is enough.

Register it with your agent

You need Node 20 or newer on the machine. Do this inside a project workspace of its own in VS Code or a similar editor, so the server and the agent's configuration stay with that project. For Claude Code, one line, with the path filled in:

claude mcp add gbti-network -- node <path-to-the-unzipped-extension>/mcp/gbti-network-mcp.mjs

For an agent that reads a configuration file (Claude Desktop, Cursor and others), add this entry:

{
  "mcpServers": {
    "gbti-network": {
      "command": "node",
      "args": [
        "<path-to-the-unzipped-extension>/mcp/gbti-network-mcp.mjs"
      ]
    }
  }
}

Sign in through the agent

Ask the agent to call the login tool. It gives you a GitHub device URL and a code; open the URL, enter the code, and approve. Then the agent calls login_confirm, and whoami shows your account. Your token stays on your own machine, the same as the browser extension.

Or paste this prompt and let the agent do the steps

Set up the GBTI Network MCP server in Claude Code so you can publish and maintain my GBTI content.

1. Register it as an MCP server. The server ships inside the GBTI extension package; from the unzipped folder run:
     claude mcp add gbti-network -- node <path-to-the-unzipped-extension>/mcp/gbti-network-mcp.mjs

2. Sign me in: call the login tool, give me the GitHub device URL and code, and after I authorize, call login_confirm. Confirm with whoami.

3. Show what I can work on with list_my_content, then use publish_content to publish or update a post, project, or prompt.

Important: publishing needs an active paid GBTI membership. publish_content only works when my GitHub account holds one, and without it the gate declines the pull request, so check whoami first.
What I publish reaches members first. It becomes public after editorial review, so do not tell me an item is live on the public site the moment the pull request merges.