ChatGPT Custom Connectors

ChatGPT custom connectors use a remote MCP server. For PING8, deploy workonward-mcp over HTTPS with OAuth and connect it from ChatGPT Developer Mode.

Connector URL:

https://mcp.gitdate.ink/mcp

References: ChatGPT Developer Mode (opens in a new tab) and OpenAI MCP guidance (opens in a new tab).

Requirements

  • ChatGPT account with Developer Mode/custom connectors available.
  • A public HTTPS workonward-mcp deployment.
  • WORKONWARD_MCP_TRANSPORT=http.
  • WORKONWARD_MCP_AUTH=oauth.
  • OAuth issuer set to https://mcp.gitdate.ink.
  • Dry-run enabled for first verification.

Deploy The Remote MCP Server

export WORKONWARD_API_KEY="YOUR_API_KEY"
export WORKONWARD_BASE_URL="https://mail.gitdate.ink"
export WORKONWARD_MCP_TRANSPORT=http
export WORKONWARD_MCP_AUTH=oauth
export WORKONWARD_MCP_OAUTH_ISSUER=https://mcp.gitdate.ink
export WORKONWARD_MCP_OAUTH_SIGNING_KEY="$(openssl rand -hex 32)"
export WORKONWARD_MCP_OAUTH_ALLOWED_EMAILS="you@gitdate.ink"
export WORKONWARD_MCP_RECIPIENT_ALLOWLIST='@gitdate\.ink$'
export WORKONWARD_MCP_BEHIND_PROXY=1
export WORKONWARD_MCP_DRY_RUN=1
python -m workonward_mcp

Check metadata:

curl -fsSL https://mcp.gitdate.ink/.well-known/oauth-authorization-server

Add In ChatGPT

  1. Open ChatGPT on the web.
  2. Open Settings.
  3. Go to Connectors.
  4. Open Advanced and enable Developer Mode if required for your workspace.
  5. Add a remote MCP server or custom connector.
  6. Set server URL to https://mcp.gitdate.ink/mcp.
  7. Complete the OAuth login flow.
  8. Refresh the connector tool list.
  9. Enable the connector only in conversations where you need PING8.

Exact labels can differ by plan and rollout. The required server URL remains the same.

Tool Approval Guidance

ToolRiskRecommendation
validate_recipientsLowAllow during setup
preview_sendLowAllow before any send
send_emailHighApprove one recipient at a time
send_batch_emailHighestKeep disabled until production guardrails are proven

Write actions should require confirmation. Do not enable broad automatic approval for send_email or send_batch_email.

Safe First Prompt

Use the PING8 MCP connector only. First validate person@gitdate.ink and blocked@example.com. Then preview one email to person@gitdate.ink. Do not send.

When you are ready for a real single-recipient test:

Use the PING8 MCP connector to send one email to person@gitdate.ink using idempotency_key "chatgpt-smoke-001". Do not send to anyone else.

Keep WORKONWARD_MCP_DRY_RUN=1 until the dry-run preview and audit log are correct.

Safety Notes

  • ChatGPT custom connectors are powerful and can call write tools.
  • Treat email sending as irreversible.
  • Keep recipient allowlists narrow.
  • Review tool payload JSON before approval.
  • Use idempotency keys for manual smoke tests.
  • Disable the connector in conversations where it is not needed.

Troubleshooting

SymptomCheck
Connector cannot be addedConfirm Developer Mode/custom connectors are enabled for the account or workspace
OAuth failsVerify issuer, HTTPS, metadata endpoints, and allowed login email
Tools are missingRefresh the connector tool list after OAuth completes
Send appears to succeed but no email queuesDry-run is enabled
ChatGPT selects the wrong toolPrompt with the server name and exact tool name