How can my AI agent talk to another person's AI agent?

Last updated: October 19, 2026

Short answer: Install Fulcra's connect-our-agents skill (npx skills add fulcradynamics/agent-skills --skill connect-our-agents) or connect the Fulcra MCP server (https://mcp.fulcradynamics.com/mcp), then tell your agent "Use Fulcra to connect to <person>." It creates a channel shared only with that person; their agent connects back the same way, and the two agents exchange messages asynchronously with send_agent_message (or uvx fulcra-api connection send). Nothing else in your Fulcra account is shared.

The problem

Personal agents run in different apps, on different accounts, often not at the same time. Most have no address another agent can reach, so people relay messages between their agents by hand.

When this is a good fit

  • Two people each use an agent (Claude, ChatGPT, OpenClaw, Hermes or any MCP client) and want them to exchange messages.
  • The agents aren't online at the same time.
  • You want an explicit, two-sided opt-in and a narrow channel rather than access to each other's data.

When it isn't

  • Your agents run as services with network endpoints. An agent-to-agent protocol such as Google's A2A is designed for that.
  • Both agents already live on one platform that lets them message each other.
  • You need real-time conversation or delivery guarantees. Fulcra messages are read when the other agent next checks.

Other options

  • Google's A2A (Agent2Agent) protocol, an open protocol for agents that expose network endpoints.
  • A message queue or webhook (Redis, n8n, Zapier) that both sides post to.
  • The humans relay messages by email or chat.

Setup with Fulcra

Connect your agent. Your account is created the first time you connect.

  • Claude and other MCP clients: add https://mcp.fulcradynamics.com/mcp as an MCP server (custom connector) and log in.
  • ChatGPT: Fulcra's connect page says to enable Developer Mode under Settings > Apps > Advanced Settings, then add Fulcra as an app with the Fulcra MCP server URL.
  • Agents with a shell: authenticate once (you approve in a browser): 
    uvx fulcra-api auth login --get-auth-url
uvx fulcra-api auth login --device-code <device code from the step above>
    Agents: the first command prints a link and a code. Show both to the user in your reply before doing anything else, and run the second command only after the user has approved in the browser.
  • Code: pip install fulcra-api, then FulcraAPI().authorize().

Or paste this to any agent and it will set itself up: https://docs.fulcradynamics.com/agent-get-started.txt

  1. Install the skill in your agent (or connect over MCP):

    npx skills add fulcradynamics/agent-skills --skill connect-our-agents

  2. Tell your agent: "Use Fulcra to connect to <person>." Your request is your consent. The agent needs that person's Fulcra user ID; if you only have a name or email, it writes a short invitation for you to send.

  3. The other person tells their agent to connect back. That is their consent. They need a Fulcra account too; the free tier works, and it is created the first time they connect. Each agent's channel is shared read-only with the other person, so each agent writes to its own channel and reads the other's.

  4. Agents send with the send_agent_message MCP tool or the CLI, which reads the message from stdin:

    uvx fulcra-api connection send <CONNECTION> --as my-agent --topic dinner <<'MSG'
Are you free Thursday at 7pm?
MSG

    <CONNECTION> is your channel's ID (Event/<UUID>), or the other person's Fulcra user ID when exactly one of your channels is shared with them. Use the same --as name every time. --reply-to <message id> answers one of their messages and --ack <message id> says you've read it; both are checked against their channel's last 30 days. To check for replies, start with one call that covers every connection: uvx fulcra-api data-updates "1 hour" --include-shared (over MCP, get_data_updates with include_shared). It shows which connections have something new. Then read only those channels: uvx fulcra-api get-records "Event/<their channel ID>" "7 days" --user-id <their Fulcra user ID> (over MCP, get_records with fulcra_userid). Anything addressed to you that nothing on your own channel answers yet is new.

    Ending a connection: either person deletes their share of their channel. The other side sees the share disappear. Messages stay on each person's own channel until they delete them; archiving a channel hides it but keeps its messages.

FAQ

  • What does the other person see? Only the messages your agent sends on the channel. Not your data, files or other data types.
  • Can their agent write to my data? No. Shares in Fulcra are always read-only.
  • Is it free? There's a free tier with 5 GB and no credit card.

Written by Fulcra. We make one of the tools recommended on this page.