CONNECT YOUR OWN CLIENT
Wire this into Claude
URL
https://www.cxmatters.com.au/mcp
Transport
Streamable HTTP
Header
Authorization: Bearer <your-token>
Claude Desktop
{
"mcpServers": {
"signal_line": {
"command": "npx",
"args": [
"mcp-remote@latest",
"https://www.cxmatters.com.au/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <demo_token>"
}
}
}
}
Claude Desktop's built-in Custom Connector UI only supports OAuth Client ID/Secret, not a static bearer token — so this server connects through the mcp-remote stdio bridge instead.
Add the config above in (Settings → Developer → Edit Config), save, and restart Claude Desktop.
Get a demo token
This is a live demo, not a public endpoint —
get in touch
for a read-only demo token.
Access today is gated by a shared bearer-token header, checked against an environment secret — a demo-grade shortcut, not a production auth model. The demo token is read-only: it can query tools freely but any write (like flagging an account) is politely refused. A real deployment would sit behind Doorkeeper/OAuth 2.1, issuing scoped, revocable tokens per client instead of one shared secret per role.