Use Hoko with Gemini CLI
Connect Gemini CLI to Hoko with a bearer API key.
Before you start
This path needs Gemini CLI access that permits remote MCP servers, such as Standard, Enterprise, or paid API-key access. Consumer and free access may not expose this feature.
Configure the server
Create a scoped key in Dashboard > Integrations > API Keys. Add https://mcp.hoko.to as a remote MCP server and set its secret-backed Authorization header to Bearer <HOKO_API_KEY>. Keep the key outside version control.
Verify the connection
Run a read-only links operation. Confirm the workspace before using a write operation.
Fix common issues
If remote MCP is unavailable, your Gemini access tier or organization policy may not allow it.
- A 401 means an invalid key.
- A 403 means a missing scope.
- A 429 requires waiting for Retry-After.
Disconnect
Remove Hoko from Gemini CLI and revoke the key.
Add it to Gemini settings
Add this server to your user settings file, usually ~/.gemini/settings.json. Gemini documents the httpUrl and literal header fields:
{
"mcpServers": {
"hoko": {
"httpUrl": "https://mcp.hoko.to",
"headers": { "Authorization": "Bearer <HOKO_API_KEY>" }
}
}
}
Keep the file private, then run gemini and inspect MCP status.