Skip to main content
GBG GO publishes machine-readable documentation metadata that allows AI agents and developer tools to understand GO capabilities programmatically. These integration points can be used by agent frameworks, MCP-compatible tools, IDE extensions, or custom automation.

Available integration options

Depending on your tooling and integration model, use one or more of the following options.

The llms.txt file

The llms.txt file is a structured documentation index. It lists all the available documentation pages so agents can discover relevant content before answering questions. See the llms.txt file at:
https://docs.go.gbgplc.com/llms.txt

Skills CLI

The Skills CLI is a command-line tool that allows you to query the documentation and retrieve relevant information programmatically. If your agent supports the Skills CLI, then you can install the skill using:
npx skills add https://docs.go.gbgplc.com/
During the installation, you’ll be prompted to select an agent to install the skill for. Select the agent you want to integrate with GBG GO documentation. If you don’t see your agent listed, use the Search option to find it. This command loads the GBG GO documentation into the agent’s context. Start with a query like:
based on the gbg .claude skill what is GBG GO?

MCP

When an AI application connects to the GO documentation Model Context Protocol (MCP) server, it can search the documentation and retrieve full page content directly, in response to your prompts. Instead of relying on information from its training data or making a generic web search, your MCP server provides access to all indexed content on the documentation site. GBG GO exposes its documentation through a remote MCP server. This enables MCP-compatible clients to query the documentation dynamically. To connect, register the following URL as a remote MCP server in your client configuration:
https://docs.go.gbgplc.com/mcp

MCP tools

Your MCP server provides two tools that AI applications can use:
  • Search: Searches across the GBG GO documentation to find relevant content, returning snippets with titles and links. Use this when you need to discover information or find pages matching a query.
  • Get page: Retrieves the full content of a specific documentation page by its path. Use this when you already know the page path, such as from search results, and need the complete content rather than a snippet.
AI applications determine when to use each tool based on the context of the conversation. For example, an AI application might first search your documentation to find relevant pages, then use the get page tool to retrieve the full content of the most relevant result.

Use MCP server

The GBG GO documentation provides different options for using the MCP server:
Add the GBG GO MCP server to Claude:
  1. Navigate to the Connectors page in the Claude settings.
  2. Select Add custom connector.
  3. Add the GBG GO MCP server:
    • Name: GBG GO Docs
    • URL: https://docs.go.gbgplc.com/mcp
  4. Click Add.
Access the MCP server in your chat:
  1. When using Claude, click the attachments button (the plus icon).
  2. Navigate to Connectors, you’ll see the GO docs MCP connector you just added automatically enabled.
  3. Ask Claude a question about GBG GO.