ego

dog.egoPublished by ego.dogOfficial publisherv1.0.1Updated Oct 24, 2026

Write LinkedIn posts in your own voice. Drafts only, ego never publishes for you.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that lets an assistant write LinkedIn post drafts in your own voice, leaving publishing to you.

What you can do
Draft LinkedIn posts in your own voice, based on the server's description of its purpose. Drafts only: the server states it never publishes on your behalf, so posting stays a manual step. No tool list is published, so the exact drafting actions are not documented here.
When to use it
Useful if you want an assistant to help compose LinkedIn posts that sound like you, while you keep control of what actually gets published.
Requirements
A remote endpoint at ego.dog over streamable HTTP, with OAuth authentication. A bearer token created in your ego account settings must be supplied in the Authorization header.
Before you install
The Authorization header carries a secret bearer token; keep it private and revoke it if exposed. The server receives whatever content you give it for drafting, so avoid pasting sensitive material. Publishing is not performed by the server, so review drafts before posting them yourself.

Installation

In SourceWeft

  1. Open ego 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/dog.ego%2Fego/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": {
    "ego": {
      "type": "http",
      "url": "https://ego.dog/api/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

1
  1. v1.0.1LatestSep 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.