Skip to content
Discussion options

You must be logged in to vote

Bicho uses stateless Streamable HTTP at your installation's /mcp endpoint. You do not need a particular model or agent brand. The practical requirement is a client that supports this remote transport, MCP initialization and protocol negotiation, and a custom Authorization bearer header.

Some clients accept a configuration shaped like this:

{
  "mcpServers": {
    "bicho": {
      "url": "https://your-bicho-worker.example/mcp",
      "headers": { "Authorization": "Bearer <admin-token>" }
    }
  }
}

This is a configuration example, not a universal client format. Use your client's remote-server settings and secret storage. Environment-variable substitution inside JSON is client-specific, so…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by zapalblizh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants