Issue Category
Suggestion for existing article
Affected Documentation Page URL
https://docs.continue.dev/customize/deep-dives/mcp-examples
Issue Description
Hi Continue maintainers, I maintain and operate Baizhi Agent Toolkit and am proposing this documentation addition on behalf of Baizhi Cloud through ct-jaryn.
Would a short Baizhi Agent Toolkit recipe fit the existing Example MCP Servers article? Its remote, user-managed Bearer authentication can use Continue's existing streamable-http, apiKey, and secret-reference support. We are not requesting a new protocol, native credential UI, automatic installation, or Hub listing.
Agent Toolkit is a hosted commercial tool service, not a model provider. Users need their own Baizhi account and API key; tool calls may consume service credits. The public integration repository contains configuration, documentation, and tests, not the hosted backend source.
The proposed example would give readers a clearly scoped remote-service configuration without embedding a key in a shared file, and explain the service boundary before they enable it in agent mode.
Expected Content
A concise entry, subject to maintainer approval and compatibility verification, using the existing article's format:
mcpServers:
- name: Baizhi Agent Toolkit
type: streamable-http
url: https://agent-toolkit.app.baizhi.cloud/mcp
apiKey: ${{ secrets.BAIZHI_API_KEY }}The accompanying text would explain how to supply the secret through Continue's documented secret mechanism, account and credit requirements, and that queries, selected webpage URLs, and extraction instructions are sent to Baizhi's hosted service. It would not claim unverified retention or privacy guarantees, change tool approvals, or describe all discovered tools as read-only. Search, webpage reading, and extraction would be example uses, not a configured three-tool allowlist.
This is a documentation-scope request only. We have reviewed the configuration and transport code but have not completed authenticated Continue CLI/IDE or production-tool verification. A later documentation PR would disclose actual test coverage and require the responsible human contributor to handle the project's CLA; no agreement is being signed here.
Product overview · Service console
We also note the scope feedback on the earlier FIXGRAPH documentation request #11683. This suggestion is only about the existing examples article, not a request for a default MCP server. If service-specific recipes are outside the article's intended scope, we will keep this in our own documentation. Thank you for considering it.
Issue Category
Suggestion for existing article
Affected Documentation Page URL
https://docs.continue.dev/customize/deep-dives/mcp-examples
Issue Description
Hi Continue maintainers, I maintain and operate Baizhi Agent Toolkit and am proposing this documentation addition on behalf of Baizhi Cloud through
ct-jaryn.Would a short Baizhi Agent Toolkit recipe fit the existing Example MCP Servers article? Its remote, user-managed Bearer authentication can use Continue's existing
streamable-http,apiKey, and secret-reference support. We are not requesting a new protocol, native credential UI, automatic installation, or Hub listing.Agent Toolkit is a hosted commercial tool service, not a model provider. Users need their own Baizhi account and API key; tool calls may consume service credits. The public integration repository contains configuration, documentation, and tests, not the hosted backend source.
The proposed example would give readers a clearly scoped remote-service configuration without embedding a key in a shared file, and explain the service boundary before they enable it in agent mode.
Expected Content
A concise entry, subject to maintainer approval and compatibility verification, using the existing article's format:
The accompanying text would explain how to supply the secret through Continue's documented secret mechanism, account and credit requirements, and that queries, selected webpage URLs, and extraction instructions are sent to Baizhi's hosted service. It would not claim unverified retention or privacy guarantees, change tool approvals, or describe all discovered tools as read-only. Search, webpage reading, and extraction would be example uses, not a configured three-tool allowlist.
This is a documentation-scope request only. We have reviewed the configuration and transport code but have not completed authenticated Continue CLI/IDE or production-tool verification. A later documentation PR would disclose actual test coverage and require the responsible human contributor to handle the project's CLA; no agreement is being signed here.
Product overview · Service console
We also note the scope feedback on the earlier FIXGRAPH documentation request #11683. This suggestion is only about the existing examples article, not a request for a default MCP server. If service-specific recipes are outside the article's intended scope, we will keep this in our own documentation. Thank you for considering it.