One-click MCP server installation for Claude Desktop

[aborruso]

Problem / Use case

Currently, users need to manually configure Claude Desktop to use this MCP server by:

1. Finding the Claude Desktop config file location
2. Manually editing the JSON configuration
3. Adding the correct command and args for the server
4. Restarting Claude Desktop

This process is error-prone and creates friction for users who want to quickly try out the CKAN MCP server.

Proposed solution

Implement one-click installation support as described in Anthropic's Desktop Extensions announcement.

This would involve:

1. Create a claude:// installation link on the project website and README:

   claude://install-mcp-server?name=ckan-mcp&config=<base64-encoded-config>
   

2. Provide the server configuration in the correct format:

   {
     "command": "npx",
     "args": ["-y", "@ondata/ckan-mcp-server"]
   }

3. Add installation button to:

   • README.md
   • Project website (https://ondata.github.io/ckan-mcp-server/)
   • npm package page

User experience:

• User clicks "Install in Claude Desktop" button
• Claude Desktop opens with installation prompt
• User confirms installation
• Server is immediately available in Claude Desktop

Alternatives considered

1. Continue with manual installation: Works but creates friction
2. Provide installation script: Still requires manual execution
3. Docker container: Adds complexity for simple use cases

The claude:// protocol is the official recommended approach from Anthropic and provides the best user experience.

References

• Anthropic Desktop Extensions announcement
• MCP Specification

[aborruso]

Proposal: Two Installation Options

After further consideration, we could offer two one-click installers to serve different use cases:

🚀 Option 1: Instant Try (HTTP Worker)

Button: "Try CKAN MCP Now"

claude://install-mcp-server?name=ckan-mcp-demo&config=<base64>

Config:

{
  "transport": "http",
  "url": "https://ckan-mcp-server.andy-pr.workers.dev"
}

Benefits:

• ✅ Zero installation (no Node.js, no npm required)
• ✅ Works immediately on any OS
• ✅ Always up-to-date (maintained by project team)
• ✅ Perfect for quick evaluation and demos

Limitations:

• ⚠️ 100k requests/day shared quota across all users
• ⚠️ Depends on external service availability
• ⚠️ Not recommended for heavy production use

---

💪 Option 2: Full Install (Local)

Button: "Install CKAN MCP Locally"

claude://install-mcp-server?name=ckan-mcp&config=<base64>

Config:

{
  "command": "npx",
  "args": ["-y", "@ondata/ckan-mcp-server"]
}

Benefits:

• ✅ Unlimited requests
• ✅ No dependency on external services
• ✅ Better privacy (no data through third-party servers)
• ✅ Production-ready

Requirements:

• Node.js 18+ installed

---

Recommended User Journey

On website/README:

1. First-time users → "Try it now" button (HTTP worker)

   • No friction, instant gratification
   • Can explore features immediately

2. After evaluation → "Install locally" button (npx)

   • Prompted when they hit quota limits or want unlimited access
   • Clear upgrade path from demo to production

UI Mock:

┌─────────────────────────────────────────────┐
│ 🚀 Try CKAN MCP Now                         │
│ [Install Demo] ← HTTP Worker (instant)      │
│                                             │
│ 💪 Install for Production Use              │
│ [Install Locally] ← npx (unlimited)         │
└─────────────────────────────────────────────┘

This approach:

• Lowers barrier to entry (try before install)
• Provides clear upgrade path
• Serves both casual testers and serious users
• Maximizes adoption while promoting local install for production

Does this dual-installer approach sound good?