Attrove

com.attrovePublished by attrove.comOfficial publisherv0.6.0Updated Oct 24, 2026

Catch conversations going quiet — watch outcomes and search Gmail, Slack, and meetings. One MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Attrove MCP lets an assistant watch outcomes that are going quiet and search Gmail, Slack and meetings from one connection.

What you can do
  • Watch outcomes and catch conversations that have gone quiet.
  • Search Gmail, Slack and meeting content for related context.
  • Connect either to the hosted Attrove endpoint or run the local npm package over stdio.
When to use it
Useful when you want an assistant to keep an eye on stalled conversations or deals and pull the relevant email, chat and meeting history together without switching tools.
Requirements
Either the remote endpoint at api.attrove.com with OAuth, or the local npm package @attrove/mcp over stdio. Requires an Attrove account with a secret key in ATTROVE_SECRET_KEY and a user ID in ATTROVE_USER_ID to scope API calls.
Before you install
The server needs a secret key (ATTROVE_SECRET_KEY) that grants access to your Attrove data; keep it out of shared configs. It reads email, chat and meeting content, which is sent to Attrove's API, so review what data leaves your accounts. Tool-level write or send behavior is not documented.

Installation

In SourceWeft

  1. Open Attrove 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.attrove%2Fmcp/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": {
    "attrove": {
      "type": "http",
      "url": "https://api.attrove.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

1
  1. v0.6.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.