Welcome to GBTI Network. Download and install the extension below to start authoring and join the community.
Install the GBTI extension
The extension is how you sign in, edit your work in place, and publish through the network. It runs in your browser and keeps your GitHub sign-in on your own machine.
One click from the Chrome Web Store, and it updates on its own.
Open a new tab and land on the network: the latest activity, your work, and everything members are shipping, without leaving your browser.
Your sign-in only says who you are
The extension keeps your GitHub sign-in in your browser and sends it only to GBTI's own service, which uses it to confirm who you are. It cannot change your GitHub account, and you can sign out or remove the extension at any time.
Building the extension from source? The steps are in the extension README.
What it does
Three things, once it is installed
Sign in with GitHub
Click the GBTI icon in your toolbar and sign in with GitHub. There is no code to copy, and it signs you in on the website too.
Edit in place
Open any page you can edit and change it where it lives. No separate dashboard, no copy-paste between tabs.
Publish through the network
Save a draft or publish straight to the network. Your changes go through the same review flow as everyone else.
Publish with your AI agent
It ships with a GBTI MCP server
Paid members can also run the GBTI MCP server. Connect it to Claude Code or any MCP client and your agent can publish new content and maintain what you have already shipped, through the same gated flow you use in the browser. The MCP guide has the download and the setup steps.
- Author from your agent
Your agent can draft, validate, and publish posts, projects, and prompts, and check the status of your pull requests, all through the managed GBTI tools.
- Signs in as you
A GitHub device-flow login signs the MCP server in as you. Your token stays on your own machine, the same as the browser extension.
- Same content, both ways
Edit in the browser or hand it to your agent. Both write to the same files and go through the same review, so nothing drifts.
Publishing is a members-only feature of the extension. The MCP server signs in as you, but the gate still applies: only active paid members can publish. Without the right privileges the publish tools are rejected, so an agent cannot push content for a non-member.
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.Questions
Good to know
How do I update it?
Is my GitHub sign-in safe?
Do I need to be a member?
Can my AI agent publish for me?
Edit and publish your work in place
Install the free extension, then sign in to start drafting and publishing through the GBTI Network.