Skip to main content

ChatGPT documentation plugin

Use your Biel.ai MCP endpoint to give ChatGPT access to your indexed documentation. You can connect it for your own use, then package a plugin for public distribution.

Before you start​

  • Index your content in Biel.ai and enable hosted MCP on a plan that includes it.
  • Copy your project's MCP server URL from the widget's Connect menu. Use the complete URL, including its path and any project configuration.
  • Use a ChatGPT account and workspace that allow custom MCP connections.

For a public documentation project, the connection does not need a Biel.ai API key. For a private project, review MCP configuration and access before sharing the connection. Biel's API-key configuration does not provide an OAuth sign-in flow.

1. Connect the MCP server in ChatGPT​

  1. Open ChatGPT Plugins.
  2. Select +, then Add custom MCP server.
  3. Enter a name such as Your Product Docs and a description of the documentation it covers.
  4. Enter the complete Biel.ai MCP URL under Connection.
  5. Configure authentication for the endpoint. Use no authentication for a public Biel.ai project.
  6. Review the connection notice and select Create as a plugin.
  7. Confirm that ChatGPT discovers biel_ai, biel_search, and biel_get_document.

Install the plugin, start a new chat, and select it with @. Account and workspace policies can restrict these options. See OpenAI's connection guide for the current interface.

2. Test answers and source retrieval​

Ask a question whose answer is in your documentation:

Use Your Product Docs to explain how authentication works and cite the sources.

For source retrieval, ask:

Use Your Product Docs to search for SDK authentication. Retrieve the sources without generating a Biel answer, then explain them with citations.

The server exposes biel_ai for Biel-generated answers, biel_search for hybrid keyword and semantic retrieval, and biel_get_document for complete indexed document text. Normally the assistant searches, reads relevant documents, and writes its own answer. Use biel_ai when you specifically want Biel to answer. See tools and limits.

Test a follow-up, an uploaded document, a question with no matching source, and private access if your project requires it. Check that citations identify the actual source and that failures are reported as errors.

After an MCP tool-schema update, open the connection in ChatGPT Plugins, select Refresh, and test again in a new conversation.

3. Package a distributable plugin​

For directory distribution, create a folder containing a portable plugin.json manifest and an mcp.json connection file. Start with these examples and replace the project URL with the public connection you tested.

plugin.json:

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "your-product-docs",
  "version": "1.0.0",
  "description": "Search Your Product documentation and answer questions with source references."
}

mcp.json:

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "your-product-docs": {
      "type": "streamable-http",
      "url": "https://app.biel.ai/mcp/YOUR_PROJECT_SLUG?metadata=chatgpt"
    }
  }
}

The URL is an example. Copy the endpoint from your own project, since hosted endpoint formats can differ. Keep API keys out of public packages. Add publisher metadata and assets required by the submission portal, then ZIP the plugin contents. OpenAI's packaging guide covers optional skills and complete metadata.

4. Submit to the plugin directory​

Open Plugins in the OpenAI platform, upload the ZIP, and complete publisher verification. Connect and scan the MCP endpoint, resolve required findings, and supply the requested test cases, reviewer access, walkthrough and release notes. Submit for review and publish after approval. Follow OpenAI's submission guide for the current requirements.

The portal requires domain verification for the MCP endpoint. Biel.ai controls the domain of its hosted endpoint: contact Biel.ai support to coordinate verification, or use a supported self-hosted endpoint on a domain you control. Connecting a hosted server privately does not complete public-directory verification.

Existing custom GPTs​

The Custom GPT Actions guide is archived for existing configurations. Use this MCP plugin guide for new documentation connections. Archiving the guide does not disable existing GPTs.