DescriptionIn trying to get the MCP API working with Claude Desktop, I cannot get an automatic or manually created connector to connect to the MCP API. Claude Desktop itself gives a generic error, but in testing (with Claude) I found that Homepage's /api/mcp endpoint gives a homepage versionv2.0.0 (17456f2) Installation methodDocker ConfigurationEnvironment: Homepage version v2.0.0 (17456f2) deployed via Docker Compose behind Caddy (however this is reproducible when using CURL against the container's port directly as well.) Claude Desktop for Linux version 1.32885.1 (a757f5).
Related environment settings:
`HOMEPAGE_MCP_ENABLED: "true"`
`HOMEPAGE_MCP_TOKEN: ${HOMEPAGE_MCP_TOKEN}`
`HOMEPAGE_MCP_ALLOW_WRITE: "false"`Container LogsNo logs from the container or the service itself are relevant, even with Browser LogsNo response TroubleshootingReproduce:
Expected: |
Replies: 2 comments 1 reply
|
I think the issue is you're (understandably) trying to use a Claude "connector". Unfortunately that requires oauth and doesnt work with homepage's token auth. I'll update the docs but you can still get this to work as an MCP with See https://gethomepage.dev/configs/mcp/#connecting-claude-desktop |
|
This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details. |
I think the issue is you're (understandably) trying to use a Claude "connector". Unfortunately that requires oauth and doesnt work with homepage's token auth. I'll update the docs but you can still get this to work as an MCP with
claude_desktop_config.jsonSee https://gethomepage.dev/configs/mcp/#connecting-claude-desktop