Knock リモートMCPを Gemini CLI にMCP接続する方法(設定手順)
Knock のリモートMCPサーバーを Gemini CLI に約1分でMCP接続。OAuth / 401 の問題は先に OAuth 2.1 デバッガーで確認できます。
Streamable HTTPhttps://mcp.knock.app/mcp
Install in Cursor →
Or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"knock": {
"url": "https://mcp.knock.app/mcp"
}
}
}claude mcp add --transport http knock https://mcp.knock.app/mcp
Install in VS Code →
Or add to .vscode/mcp.json:
{
"servers": {
"knock": {
"type": "http",
"url": "https://mcp.knock.app/mcp"
}
}
}- Open Settings → Connectors (Integrations) → Add Custom Connector.
- Paste the endpoint URL:
https://mcp.knock.app/mcp - Complete the browser OAuth 2.1 login flow when prompted.
Bridge the remote endpoint into stdio with mcp-remote in claude_desktop_config.json:
{
"mcpServers": {
"knock": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.knock.app/mcp"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"knock": {
"serverUrl": "https://mcp.knock.app/mcp"
}
}
}Add to ~/.kiro/settings/mcp.json (or .kiro/settings/mcp.json in your workspace), then reopen Kiro's Agent panel to pick up the server:
{
"mcpServers": {
"knock": {
"url": "https://mcp.knock.app/mcp"
}
}
}Add to ~/.codex/config.toml — Codex reads remote HTTP servers from [mcp_servers.*] tables:
[mcp_servers.knock] url = "https://mcp.knock.app/mcp"
Add to cline_mcp_settings.json (Cline → MCP Servers → Configure), or paste it via Cline's MCP marketplace file:
{
"mcpServers": {
"knock": {
"type": "streamableHttp",
"url": "https://mcp.knock.app/mcp"
}
}
}Add to ~/.gemini/settings.json under mcpServers — httpUrl for Streamable HTTP, url for legacy SSE:
{
"mcpServers": {
"knock": {
"httpUrl": "https://mcp.knock.app/mcp"
}
}
}接続手順
- 設定ファイルを編集 —
~/.gemini/settings.jsonを開きます。 - サーバーを追加 —
mcpServersに"knock": { "httpUrl":https://mcp.knock.app/mcp}を追加します。 - 認証を完了 — 初回呼び出し時に Knock の OAuth 認可画面が開きます。許可するとツールが有効になります。
- 検証 — オンライン Inspector に
https://mcp.knock.app/mcpを貼り付け、initialize と tools/list を実行して接続を確認します。