Actively
by Actively
Read per-account sales intelligence — agent memory, decisions and recent signals — from an AI agent. Anthropic lists 13 tools; Actively's docs describe 11 and call them read-only. OAuth 2.1 via WorkOS, identity scopes only.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Actively via MCP
https://api.actively.ai/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Actively Tools & Capabilities (13)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Actively's tool list is two shorter than Anthropic's. The docs name 11 public tools; the directory names 13.
generate_smart_fieldsandget_smart_field_schemasappear only in the directory, and the vendor's "read-only, non-destructive, idempotent, and closed-world" sentence is written about the 11 it enumerates. - No application scopes exist. Actively's authorization server advertises
openid,profile,emailandoffline_access, all identity claims, and the RFC 9728 resource descriptor declares noscopes_supportedat all. Nothing at the OAuth grant separates one account from your whole book, and no boundary falls between reading an account summary and reading every contact strategy your role can see. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here. A parameter is one of the four places an outbound capability hides, and it is the one we could not inspect.
- Bulk reads cap at 10 accounts. Actively's documentation directs callers to use the bulk tools "for up to 10 accounts" per call.
- Account intelligence is not instant. Actively's troubleshooting page states new accounts take one to two days to process, that small or private companies may have limited public data, and that agents re-evaluate accounts within 24 hours of a Business Context change.
- Read scope follows CRM routing, not the connector. Actively's troubleshooting page attributes a missing account to routing rules, volume limits or ownership sync, so what an agent can see depends on configuration made elsewhere in your workspace.
- The MCP surface reads; the outbound surface is elsewhere. Enrolment into Outreach, Salesloft or Gong Engage and contact creation in Salesforce run through the sequencing engine and the separate Agent API. Reviewing the MCP tool list tells you nothing about what your Actively workspace is already sending.
- Actively's docs are published
noindex, nofollow. The pages are served publicly at the exact documentation URL Anthropic's directory nominates, but they carry a robots meta tag asking not to be indexed. We read the nominated pages and linked rather than mirrored them. - Whether these tools cost against enrichment credits is unresolved. Actively's API specification notes that prospecting search consumes enrichment credits from ZoomInfo or Apollo unless restricted to CRM sources. We found no equivalent statement about the MCP tools and did not test it.
Frequently asked questions
No tool in the listing sends one. Actively's platform does write outreach and enrol contacts into Outreach, Salesloft or Gong Engage, but that runs on the sequencing engine, not on these 13 tools. The enrolment endpoint lives in Actively's separate REST API behind a different key. Treat the MCP surface as reading intelligence, not dispatching it.
Not by default, and not through a tool that names the write. Actively's FAQ states writes happen only if an admin explicitly configures Sync to Salesforce, after which Smart Field answers sync to a chosen CRM field every 24 hours. That sync is an admin setting on the platform, so an agent reading a Smart Field does not itself trigger a CRM write.
Anthropic's directory lists 13. Actively's own documentation enumerates 11 under the heading Public Tools and omits generate_smart_fields and get_smart_field_schemas. Neither list is wrong on its face, but the vendor's read-only claim covers only the 11 it names, so the two extra tools sit outside the sentence people will quote.
Only identity ones. Actively's authorization server advertised four scopes on 2026-08-22 — openid, profile, email and offline_access — and the server's own RFC 9728 descriptor declares no scopes_supported at all. Nothing at the consent screen separates reading one account from reading every account your workspace can see.
Contact records and internal conversation text about named people. Actively's documentation states agents synthesise CRM data, call transcripts and emails into per-account memory, and the connector's read tools return that memory. Contact strategy sits inside agent decisions, so an agent reading one account sees who your team plans to approach and how.
Actively says its public tools carry readOnlyHint, are non-destructive, idempotent and closed-world, which is what a client needs to auto-approve. We could not read those annotations ourselves because the endpoint requires authentication, and the claim is written about the 11 tools the docs name rather than all 13 Anthropic lists.
Yes. Sign-in is OAuth against your Actively workspace identity, and Actively's documentation states tool visibility and returned data are scoped to your organization permissions. Actively sells to revenue teams through a demo request rather than self-serve signup, so there is no free tier that yields an authenticated MCP session.
Memory is the facts, decisions are the opinion. Actively's API documentation defines agent memory as the agent's objective understanding — activity history, relationship context, call history, firmographics and web research. Agent decisions is the current view formed over that memory: an account summary, an account strategy with recommended actions, and a contact strategy.
Sources
- Actively MCP server documentation (retrieved 2026-08-22). Rendered client-side; extracted from the Next.js RSC flight payload in the same response. · retrieved 2026-08-22
- Actively documentation, Emails & Sequencing (retrieved 2026-08-22) · retrieved 2026-08-22
- Actively documentation, Smart Fields (retrieved 2026-08-22) · retrieved 2026-08-22
- Actively documentation, Workflows (retrieved 2026-08-22) · retrieved 2026-08-22
- Actively documentation, Rules of Engagement (retrieved 2026-08-22) · retrieved 2026-08-22
- Actively documentation, FAQs and Troubleshooting — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Actively API Cookbook (retrieved 2026-08-22) · retrieved 2026-08-22
- Actively Agent API OpenAPI 3.1 specification, version 2.0.0 (retrieved 2026-08-22), reached from the Scalar viewer configuration on · retrieved 2026-08-22
- Actively security page (retrieved 2026-08-22) · retrieved 2026-08-22
- Actively MCP product page (retrieved 2026-08-22) · retrieved 2026-08-22
- Live OAuth posture check: anonymous
initializereturned 401 with aWWW-Authenticatechallenge naming the RFC 9728 descriptor athttps://api.actively.ai/.well-known/oauth-protected-resource/mcp; authorization server metadata athttps://auth.actively.ai/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Actively support — <mailto:support@actively.ai> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Sales & CRM
- Developer
- Actively
- Tools
- 13
- Domain
- api.actively.ai
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.