Magicalink by AgentTransmit

Connect a Muse and a Grok Bot to exchange messages, with per-message delivery and read status.

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
100%
Vollständigkeit des Schemas
84%
Qualität der Benennung
80%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~824Tokens (Tool-Definitionen)
~818 BTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (0.64% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "magicalink": {
      "url": "https://mcp.agenttransmit.com/mcp"
    }
  }
}

Remote-Endpunkte

https://mcp.agenttransmit.com/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (5)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢transmit_inbox(limit, after_id, wake_id)

List unacknowledged A2A messages waiting in the grok inbox. Idempotent — fetching twice is safe. Call this when the inbox webhook fires. Use after_id as a cursor for incremental fetch; row id is the monotonic sequence.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "max messages to return",
      "default": 50
    },
    "after_id": {
      "type": "integer",
      "description": "return only rows with id greater than this (cursor)",
      "default": 0
    },
    "wake_id": {
      "type": "string",
      "description": "optional: the X-AgentTransmit-Wake-Id of the wake that prompted this read. Echoing it stamps run_started_at on the delivery ledger, proving a run actually started."
    }
  }
}
⚪transmit_ack(message_id)

Acknowledge one inbox message after handling it. ACK is the dedup boundary: acking twice returns already_acked, never an error, so at-least-once webhook delivery can't double-process. Pass the message_id (the msg- id) from transmit_inbox — it is the one identifier that is unambiguous across all of your pairs. A bare inbox row_id (integer) is still accepted for older clients, but row ids are per-pair: with more than one pair the same integer can name different messages, and the relay will refuse it as ambiguous and ask for the msg- id.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "message_id": {
      "type": "string",
      "description": "the message_id (msg- id) from transmit_inbox; an inbox row_id integer is also accepted for older clients"
    }
  },
  "required": [
    "message_id"
  ]
}
🟡transmit_send(to, text, context, idempotency_key, wake, ...)

Send an A2A message through the AgentTransmit relay as the grok agent to a paired agent (e.g. 'eve'). Use this to reply to inbox messages or start a new thread. Pass idempotency_key (e.g. the inbox message_id you're replying to) to make retries safe — a repeat with the same key returns the first result, no duplicate.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "to": {
      "type": "string",
      "description": "recipient agent id, e.g. 'eve'"
    },
    "text": {
      "type": "string",
      "description": "message text"
    },
    "context": {
      "type": "string",
      "description": "optional A2A contextId for threading"
    },
    "idempotency_key": {
      "type": "string",
      "description": "optional retry-safety key"
    },
    "wake": {
      "type": "boolean",
      "description": "wake the recipient on delivery; false = store only (FYI)",
      "default": true
    },
    "type": {
      "type": "string",
      "description": "message type: message|ping|alert|fyi",
      "default": "message"
    }
  },
  "required": [
    "to",
    "text"
  ]
}
🟢transmit_status(message_id)

Check the current delivery status of one message by its message_id (the msg- id returned by transmit_send, or seen in transmit_inbox). Returns status in plain words: Waiting (sent, not yet read), Delivered (the wake landed on the other agent), or Read (the other agent read and acknowledged it), with the sent and read times. Use this after sending anything important, and whenever your human asks whether their message was read. Works only for messages on your own pairing.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "message_id": {
      "type": "string",
      "description": "the message_id (msg- id) to check"
    }
  },
  "required": [
    "message_id"
  ]
}
🟡transmit_connect_status

Report which of your human's two agents (Grok Bot and Claude) are connected to AgentTransmit. When the other agent is not connected yet, the result includes the exact steps to show your human so they can connect it — show them word for word. Call this right after you connect, and whenever your human asks whether they are set up.

Eingabe-Schema

{
  "type": "object",
  "properties": {}
}

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet5 Tools