Which AI agents and MCP clients can connect? #70
|
What transport and authentication support does an MCP client need to connect to Bicho? Is a particular agent required? |
Replies: 1 comment
|
Bicho uses stateless Streamable HTTP at your installation's 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 do not assume that putting a variable name in the header resolves it securely. The client must send JSON POST requests and accept both For documentation access, connect to |
Bicho uses stateless Streamable HTTP at your installation's
/mcpendpoint. 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 customAuthorizationbearer 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…