MCP桌面客户端

Installation

Usage

http4k-mcp-desktop --url http://localhost:3001/<protocol> [OPTIONS]

Examples

Command Line Options

Authentication Options

At time of writing, the MCP auth standards are in flux, but http4k-mcp-desktop has implemented some standard HTTP mechanisms into the http4k-mcp-desktop.

• Basic Auth
• Bearer Token
• API Key
• *OAuth via standardised auto-discovery

* This is the OAuth standard which is currently in the post 2025-03-26 draft specification which uses auto discovery of the authentication token using OAuth Protected Resource and OAuth Client Credentials. This requires:

• The MCP server to list its authentication servers in it's OAuth Protected Resource metadata endpoint (/.well-knwon/oauth-protected-resource)
• The Authentication server to support the OAuth Client Credentials flow and auto discovery endpoint (/.well-knwon/oauth-authorization-server)

MCP servers built using the http4k MCP SDK do support the above, but other servers may not.

Configuring Claude Desktop

To configure Claude Desktop to use the http4k MCP Desktop Client, you'll need to create a JSON configuration file. Note that if you're on mac and installed the app via Brew, it will already be on your path. Here's how to set it up:

1. Create a config.json file with the following structure:

{
    "command": "/path/to/http4k-mcp-desktop",
    "args": [
        "--url",
        "http://your-mcp-server:port/mcp"
    ],
    "env": {}
}

2. Adjust the parameters as needed: - Update the path to where you've installed the http4k-mcp-desktop binary. For brew users it's already on your path so just use http4k-mcp-desktop - Set the correct URL and protocol options for your MCP server (see examples) - Add any authentication options required (see examples)

1. In the Claude Desktop application settings, specify the path to your config.json file.

Example Configurations

Basic MCP Server Connection:

{
    "command": "/usr/local/bin/http4k-mcp-desktop",
    "args": [
        "--url",
        "http://localhost:3001/sse"
    ],
    "env": {}
}

With API Key Authentication:

{
    "command": "/usr/local/bin/http4k-mcp-desktop",
    "args": [
        "--url",
        "http://localhost:3001/sse",
        "--apiKey",
        "your-api-key"
    ],
    "env": {}
}

With OAuth Authentication:

{
    "command": "/usr/local/bin/http4k-mcp-desktop",
    "args": [
        "--url",
        "http://localhost:3001/sse",
        "--oauthTokenUrl",
        "http://localhost:3001/token",
        "--oauthClientCredentials",
        "client:secret"
    ],
    "env": {}
}

JSON-RPC with API Key Auth w

http4k-mcp-desktop --transport jsonrpc --url http://localhost:3001/jsonrpc --apiKey your-api-key

Integration with AI Applications

This client is specifically designed to work with desktop AI applications that use StdIO for communication. It handles:

1. Reading input from the AI application via stdin
2. Sending that input to the MCP server
3. Receiving responses from the server
4. Passing those responses back to the application via stdout

This enables seamless connections between desktop AI applications like Claude and remote MCP servers.

Remote Protocol Comparison

The MCP Standard remote protocol is HTTP Streaming, which superceded the previous standard (SSE) in the 2025-03-26 version. http4k has implemented other standard transports into the http4k-mcp-desktop, as these will be more appropriate for distributed/hosted MCP servers.

FAQ

• Q: I'm using Cursor but I get an error message when installing my MCP connection
• A: Cursor users should currently use HTTP Non-streaming mode (--transport http-nonstream)