Host your own Claude connector.

From idea to a connector in Claude

1. Ask Claude Code to build an MCP server with the tools you need, using defineMcp from @denkopsai/sdk/mcp or the official MCP SDK.
2. Add "connector": true to denkops.json so DenkOps puts OAuth sign-in in front of it.
3. Say "deploy on DenkOps". You get an HTTPS URL ending in /mcp.
4. In claude.ai or Claude Desktop, open Connectors, add a custom connector and paste the URL. Claude sends you through the sign-in page and the tools appear.

The same URL works in Claude Code with claude mcp add --transport http. The config generator prints the exact command and config for each client.

What makes a connector feel finished

• Clear tool names and descriptions. Claude picks tools by their description. Run your tool list through the MCP tool linter to catch vague descriptions, schema mistakes and missing safety annotations before users see them.
• Annotations. Mark read-only tools with readOnlyHint and dangerous ones with destructiveHint, so Claude can ask before it changes something.
• Your brand. Set an icon and colours in denkops.json and the sign-in and consent pages carry them.
• Your domain. Point a custom domain at the connector when you share it with customers, see a connector on your own domain.

One connector per customer

Agencies often deploy the same connector once per client, each with its own slot, secrets, sign-in list and logs. See MCP connectors for clients.