tell.dev

dev.tellPublished by tell.devOfficial publisherv0.7.9Updated Oct 24, 2026

Message someone through your coding agent. Their agent gets your note and explains it.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP endpoint that lets a coding agent send a message to another person, whose own agent receives the note and explains it.

What you can do
Send a message to another person from within a coding agent session, addressed to their agent rather than to them directly. The recipient's agent receives the note and explains it, so the exchange is mediated by agents on both sides. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
When you want to reach another person from inside your coding agent and have their agent relay and explain the message, for example to hand off context or ask a question across teams.
Requirements
A remote endpoint at tell.dev over streamable HTTP, with OAuth authentication. An Authorization bearer token obtained from tell.dev setup is required; no local package or environment variables are declared.
Before you install
The server requires an Authorization bearer token from tell.dev setup, so treat it as a secret. Messages are sent to another person's agent, so anything you include leaves your session and is handled by a third party; avoid sending sensitive content.

Installation

In SourceWeft

  1. Open tell.dev in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.tell%2Ftell/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tell-dev": {
      "type": "http",
      "url": "https://tell.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.7.9LatestSep 24, 2026
  2. v0.4.10Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Tell integrations