engman

com.engmanappPublished by engmanapp.comOfficial publisherv1.0.1Updated Nov 4, 2026

1:1s, feedback and career plans for the people engineering leaders manage.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Engman is a remote MCP server for engineering leaders' one-on-ones, feedback and career plans covering the people they manage.

What you can do
  • The listing gives no tool list, so capabilities are inferred from the description only.
  • It is positioned around managing people as an engineering leader: one-on-one meetings, feedback, and career plans.
  • An assistant connected to it would work with that people-management material for the people a leader manages.
  • No further detail on specific actions is provided.
When to use it
Consider it if you are an engineering manager or lead who keeps one-on-ones, feedback and career plans in Engman and want an assistant to work with that material. It is not aimed at general project or task tracking.
Requirements
A remote MCP endpoint at app.engmanapp.com reached over streamable HTTP. Authentication is OAuth and required, so you need an Engman account and a client that supports OAuth sign-in. No environment variables or headers are declared.
Before you install
The server holds sensitive people data: one-on-ones, feedback and career plans about the people you manage. Access is granted through OAuth, so review the scopes your client requests. The listing does not describe which actions read or change data, so confirm that before use.

Installation

In SourceWeft

  1. Open engman 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/com.engmanapp%2Fengman/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": {
    "engman": {
      "type": "http",
      "url": "https://app.engmanapp.com/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. v1.0.1LatestNov 4, 2026
  2. v1.0.0Oct 29, 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.