Skip to main content
Prefer Claude’s remote MCP connector flow with https://mcp.konbiniapi.com. Anthropic now supports remote custom connectors in Claude and Claude Desktop, so local stdio is only a fallback for older workflows.

​
Claude and Claude Desktop

Anthropic’s current custom connector flow supports remote MCP on Claude and Claude Desktop. KonbiniAPI works through the hosted remote server with OAuth, so you do not need to run a local bridge.
1

Open connectors

In Claude, open Settings → Connectors.
2

Add a custom connector

Click Add custom connector.
3

Enter the remote MCP URL

https://mcp.konbiniapi.com
4

Authorize

Claude will redirect you to KonbiniAPI to log in and grant access. Once the OAuth flow completes, the connector is available in Claude and Claude Desktop.
5

Enable it in a conversation

Use the + menu, then Connectors, and enable konbiniapi for the conversation where you want Claude to use it.
Anthropic’s remote MCP custom connector guide says remote custom connectors are available on Claude, Cowork, and Claude Desktop in beta. Free users are limited to one custom connector.

​
Team and Enterprise

On Team and Enterprise plans, an owner usually adds the custom connector first in Organization settings → Connectors, then each user connects their own account from Settings → Connectors. For Claude Code, see Claude Code.

​
Legacy stdio fallback

If you are stuck on an older local MCP workflow, Claude Desktop can still use a local stdio bridge with an API key. This is no longer the recommended setup. Open claude_desktop_config.json:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "konbiniapi": {
      "command": "npx",
      "args": ["-y", "@konbiniapi/mcp"],
      "env": {
        "KONBINIAPI_KEY": "knbn_your_api_key"
      }
    }
  }
}
Keep your API key out of shared config files or public repositories. Prefer the remote connector flow above whenever possible.