Add AffiliateLauncher in Claude as a custom connector.

Claude's custom connector takes a remote MCP URL and a request header. API and MCP access needs the Plus plan.

What you enter

• Remote MCP URL: https://directsales.software/mcp
• Name: something you will recognize, such as AffiliateLauncher.
• Authentication: No sign-in. This server uses an API key, not an OAuth login.
• Request header name: authorization
• Request header value: Bearer, a space, then the company API key. Claude's docs say to include the scheme yourself. Claude does not add Bearer for you.

The key is created under Settings, then Company Config, then API & integrations. API and MCP access needs the Plus plan. Accounts without Plus are refused.

AffiliateLauncher documents Streamable HTTP. Claude's docs say to change Advanced, then Transport, only if the server's documentation says to, and that a URL ending in /sse selects the older SSE transport. This URL does not end in /sse. Leave the transport as Claude sets it.

Steps Claude publishes

Checked on 21 October 2026 against Add a connector that isn't in the directory and the Claude Help Center article. The dialog layout differs by account. If you see one screen with a name, a URL, and Advanced settings, use that. If you see two steps, use the choices below.

Pro, Max, and Free

1. Go to Customize, then Connectors.
2. Click Add custom connector. The Help Center says "+ Add," then "Add custom connector."
3. Enter the name and https://directsales.software/mcp. Continue.
4. Under Authentication, choose No sign-in. The OAuth client settings are hidden for that choice.
5. Under Request headers, add authorization with the value Bearer YOUR_COMPANY_API_KEY. Mark it required if you are offered that choice.
6. Click Add.

On the Free plan, Claude says you can add one custom connector.

Team and Enterprise

1. An Owner (or, on Enterprise, a role that can manage libraries) opens Organization settings, then Connectors.
2. Select Add, then Custom. If Claude asks for a type, choose Web.
3. Enter the name and the MCP URL, then continue.
4. Choose No sign-in, add the authorization header with the full Bearer value, and click Add.
5. Each member then opens Customize, then Connectors, finds the connector marked Custom, and clicks Connect.

A shared API key is the organization's credential. Everyone who uses the connector calls AffiliateLauncher with that key. Use a key you are willing to share with those members. Rotating the key in AffiliateLauncher invalidates the previous key immediately, so the connector has to be removed and added again. Claude says you cannot edit authentication after you add a connector.

Request headers are a limited beta

Claude's docs say request header authentication is in beta and available to a limited set of organizations. If you do not see Request headers, your organization does not have access yet. In that case this connector path cannot send the company API key, and you should use the OpenAPI file from your own HTTP client instead of guessing another field.

Claude also says custom connectors reach your server from Anthropic's cloud, including from Claude Desktop and Cowork. The server has to be on the public internet. directsales.software is.

Turn it on in a chat

Click the + button in the chat, then Connectors, and turn AffiliateLauncher on for that conversation. Claude's docs say to review tool approval requests carefully, to click Always allow only for trusted servers, and that you can set a tool's permission to Blocked under Customize, then Connectors. The published MCP tools are get_company_context, find_distributor, list_distributors, get_sale, get_commission_overview, get_distributor_earnings, explain_workflow, search_help, and get_help_topic.

OpenAPI, if the header field is missing

https://directsales.software/api/v1/openapi.json is the canonical REST contract. Send Authorization: Bearer YOUR_COMPANY_API_KEY on each request. Docs: https://directsales.software/api/v1/docs.