SprooveSproove's remote MCP lets compatible AI assistants become a controlled entry point into your Sproove communication — while Sproove remains the delivery, mediation and protection layer.
Example: “Sproove Anna that I'll be 20 minutes late.”
Your AI assistant finds your accepted Sproove contact and hands the message to Sproove. Sproove then applies the same agent mediation, translation, safety, rights and entitlement logic used by the native app before delivery.
Example: “Send this picture to Anna via Sproove.”
Compatible clients can hand a user-selected JPEG, PNG, WebP or PDF to Sproove. Images and PDFs use Sproove's existing media safety pipeline before delivery. An optional caption is sent separately through Sproove mediation, translation, safety and rights checks.
PDFs are delivered as the original file. Business users can analyze or translate PDF content in Sproove. ChatGPT can pass a user-selected file directly to the connector. Sproove does not read Claude chat uploads; with Claude, use an explicit HTTPS source URL when appropriate or send the file from the Sproove app.
Example: “Invite Anna to Sproove.”
Sproove creates a secure invite link you can share. If the invited person is eligible, the Invite Trial is activated when they accept the invitation in Sproove.
On MCP Apps-compatible hosts, Sproove can render an interactive send card directly inside the AI conversation. The card lets the human review the recipient, message or attachment and explicitly press Send with Sproove. The UI itself does not send anything until the human confirms.
If Sproove detects a message that requires an explicit Rights approval, the same card changes to Confirm & send. If the person is not yet a Sproove contact, the card can create a secure invite instead.
This interactive interface uses the open MCP Apps standard, so the same Sproove UI is designed to work in compatible hosts such as ChatGPT and Claude rather than maintaining separate product-specific send screens.
get_capabilities, search_contact, create_invite, share_with_sproove, send_message, send_attachment and confirm_message.
https://sproove.me/sproove-mcp
Use this URL when adding Sproove as a compatible remote MCP/custom web connector. Authentication is handled through Sproove OAuth.
Read: capability information and discoverable people/contact status needed to address a message. Write: create an invite, send a message, or send a user-provided image/PDF through Sproove. The connector does not expose a general chat-history read capability.
Attachment support: ChatGPT can pass a user-selected file directly to the MCP tool. Other clients can use attachment handoff only where their connector surface permits it, or through an explicit HTTPS source supplied by the user.
If connection or authentication fails, disconnect Sproove from the AI client and reconnect it, then sign in to your Sproove account again. The MCP requires an active internet connection and a valid Sproove account. To send to someone, that person must already be an accepted Sproove contact; otherwise create an invite first.
For connector, privacy or security questions, contact office@getreturnos.com.