MCP Server Setup Guide: Let AI Assistants Push Messages Automatically

This page explains how to connect the OnePass MCP Server to popular AI clients (Cursor, Kiro, Claude Desktop, Claude Code, VS Code, JetBrains IDEs, Trae, Gemini CLI, OpenAI Codex CLI, Grok, OpenClaw and more) so your AI assistant can call the push API and deliver messages to WeChat, DingTalk, Feishu, email and mobile clients automatically.

Why MCP for message push

Model Context Protocol (MCP) is an open standard that lets AI tools call external services. Once a remote MCP server is configured, your AI assistant gains a new capability: sending push notifications. Typical uses include sending task results to your phone after long-running coding jobs, alerting on build or deployment failures, and pushing AI-generated reports to group chats.

Three things every MCP config needs

• Server URL: the streamable HTTP endpoint of the push service.
• Authorization header: most clients require Authorization: Bearer <code> or a custom header.
• Channel code: a 32-character code that identifies your push channel. Replace ****** in every config sample with your own code after signing in.

Each editor tab above provides a ready-to-copy JSON/TOML snippet with the correct root key (mcpServers, servers, context_servers, mcp_servers or mcp.servers) for that client.

Verify the connection

After saving the config, use the client's MCP list command (for example grok mcp list or the servers panel in your IDE) to confirm the server is connected, then ask the assistant to send a test message. If it fails, double-check the channel code and the header name.