Skip to main content
Send messages and manage contacts through the XMPP MCP server. Endpoint: https://<NEURON_HOST>/MCP/XMPP. Use the host supplied by your provider.

​
What you need

You need an account the server can connect on your behalf. If account details are missing, the server requests them through the client. Your application communicates through MCP.

​
Scopes and privileges

The server advertises these OAuth scopes:
Request the categories you need. The provider must also grant the corresponding role privileges; see Scopes and permissions. For the tables below, prepend OAUTH.Scope.MCP.XMPP. to each suffix. When a row lists multiple privileges, all are required. For example, OAUTH.Scope.MCP.XMPP.Tools.Presence.Accept is a complete privilege name.

​
Tools

Select a tool name for its complete arguments, defaults, and return values in the original reference. Discover tools in your client to check what your session can use.

​
Use this server

List resources to inspect contacts and queued messages. Use a bare JID, such as name@example.net, for contact identifiers. Request a presence subscription before exchanging messages with a new contact. SendChatMessage takes To and Message, with optional IsMarkdown and Language. GetMessage can remove a message when Remove is true; PopMessage also removes the retrieved message. Both use the Tools.Message.Get privilege.

​
Resources and prompts

Resources expose contacts and received messages. Use returned resource URIs for reads and subscriptions. No custom prompts are documented. See the original Messaging and contacts reference for complete schemas and response types, or return to MCP servers.