# Actively
ID: 05-actively
Page: https://gtmmcps.com/tools/05-actively
JSON: https://gtmmcps.com/data/tools/05-actively.json
Documentation references: https://gtmmcps.com/docs/05-actively/
Category: Signals & Intent
MCP support: official
Testing: RESEARCHED
API access: unknown
Last checked: 2026-09-07
Endpoint check: not-probed; date: Not recorded

A sales platform that runs an always-on "per-account agent" for every account in a seller's book, synthesising CRM data, call transcripts and external signals into account research, risk flags and recommended next actions for the rep.

## MCP links
- https://app.actively.ai/docs/mcp
- https://app.actively.ai/mcp
- https://claude.com/connectors/actively

## Sources
- https://app.actively.ai/docs/mcp
- https://claude.com/connectors/actively
- https://actively.ai

## Research notes
Probed 2026-09-07: POST of an MCP initialize to https://app.actively.ai/mcp returned HTTP 307 with a JSON body redirecting to api.workos.com/user_management/authorize; the control POST to /zzz-not-a-route on the same host returned the same 307 to WorkOS. An identical redirect on both paths is an auth wall in front of the whole app domain, not proof that /mcp answers as an MCP server; the vendor's docs page is the evidence for the server and the endpoint is recorded on the docs' statement. The candidate row's proposed alternative was ai-sdr-agents; it lands in signals because the product's output is account intelligence for a human rep, not autonomous outreach. Listed in the Claude connector directory with "Capabilities: Read". 2026-09-07: https://app.actively.ai/mcp returned 307 to an MCP initialize POST (https://app.actively.ai/mcp).

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: none-found

Read current vendor documentation before configuring or running commands.