# Xactly: MCP server status, API access gate and what it does > Revenue platform combining incentive-compensation management (Xactly Incent) with pipeline/revenue... MCP unknown, Enterprise only. Checked 2026-09-02. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Forecasting & Revenue](../categories/forecasting-revenue.md) / Xactly # Xactly [MCP unknown](../mcp/unknown.md) [Enterprise only](../gates/enterprise-only.md) [Forecasting & Revenue](../categories/forecasting-revenue.md) RESEARCHED Checked 2026-09-02 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1. Vendor: [xactlycorp.com](https://xactlycorp.com) · entry id 12-xactly · source 12-forecasting-revenue.md line 169 **What it does** Revenue platform combining incentive-compensation management (Xactly Incent) with pipeline/revenue forecasting (Xactly Forecast), using compensation-plan and rep-behavior data as a forecasting input. **AI features, separated from automation with an AI label on it** "Xactly Intelligence" claims bias/sandbagging detection using 20+ years of rep-behavior data, compensation-dissatisfaction signals as an early attrition-risk indicator, and deal-health scoring incorporating email sentiment and meeting frequency - more specific than most vendor "AI" claims in this file because it's tied to Xactly's genuinely unusual comp-plus-forecasting data combination, though the methodology itself isn't published. Superlative claims ("99.6% forecasting accuracy," "$7B in monthly commissions processed") are vendor-stated, not independently verified. **RevOps role** Incentive-compensation-plus-forecasting platform, differentiated from pure CRM-based forecasting tools by tying comp-plan behavior directly to forecast risk. **MCP server** - **Status bucket**: MCP unknown - **Auth**: unknown - not disclosed on the vendor pages found - **Parsed URLs**: 2 found in the mcp_url field The check could not settle it either way. Unknown is a legal answer and it is published rather than guessed. The status was established on 2026-09-02. mcp_status, verbatim from the file: unknown mcp_url, verbatim from the file: none published. Xactly's own pages name an MCP server without any endpoint, docs or setup guide: https://www.xactlycorp.com/products/xactly-intelligence/agents and https://www.xactlycorp.com/company/press-room/Xactly-releases-fleet-of-agents - [https://www.xactlycorp.com/products/xactly-intelligence/agents](https://www.xactlycorp.com/products/xactly-intelligence/agents) - [https://www.xactlycorp.com/company/press-room/Xactly-releases-fleet-of-agents](https://www.xactlycorp.com/company/press-room/Xactly-releases-fleet-of-agents) **Command line** No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence. **Access gate** - **Gate bucket**: Enterprise only - **Can a solo operator reach it**: Not without a contract api_gate, verbatim from the file: enterprise-only. Xactly's own pricing page states plainly: "We don't offer a self-service trial because sales comp is usually too unique for a 'one-size-fits-all' test." Three tiers exist (Core, Plus, Ultimate) but no published rates - quote-only. **API documentation** No documentation URL recorded. 727 of 1252 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **On GitHub** [github.com/xactlycorp](https://github.com/xactlycorp) tied to the vendor by rule 3, account website https://www.xactlycorp.com/ has the vendor's domain, confidence strong - **Public repositories**: 0, forks excluded, as read on 2026-09-08 - **Mention MCP**: 0 of them - **Look like CLIs**: 0 of them - **Latest push**: not recorded Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08. **Jobs it can do** - [Read the pipeline forecast](../jobs/read-pipeline-forecast.md) - [Model a revenue plan](../jobs/model-revenue-plan.md) - [Score rep performance](../jobs/score-rep-performance.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total. **Sources** - [https://www.xactlycorp.com/products/xactly-forecast](https://www.xactlycorp.com/products/xactly-forecast) - [https://www.xactlycorp.com/products/xactly-incent](https://www.xactlycorp.com/products/xactly-incent) - [https://www.xactlycorp.com/pricing](https://www.xactlycorp.com/pricing) - [https://www.pulsemcp.com/servers?q=xactly](https://www.pulsemcp.com/servers?q=xactly) - [https://www.xactlycorp.com/products/xactly-intelligence/agents](https://www.xactlycorp.com/products/xactly-intelligence/agents) - [https://www.xactlycorp.com/company/press-room/Xactly-releases-fleet-of-agents](https://www.xactlycorp.com/company/press-room/Xactly-releases-fleet-of-agents) 6 source URLs. Raw sources field, verbatim: https://www.xactlycorp.com/products/xactly-forecast, https://www.xactlycorp.com/products/xactly-incent, https://www.xactlycorp.com/pricing, https://www.pulsemcp.com/servers?q=xactly, https://www.xactlycorp.com/products/xactly-intelligence/agents, https://www.xactlycorp.com/company/press-room/Xactly-releases-fleet-of-agents **Notes, verbatim from the file** Xactly's blog has a post titled "Why the Model Context Protocol (MCP) is the Next Enterprise Front Line" - this is thought-leadership commentary about MCP as a concept, not an announcement of a shipped Xactly MCP server; no product, repo, or docs were found to back an official/community MCP claim. 2026-09-02: mcp_status none-found -> unknown. Xactly's Fleet of Agents page states "Xactly's MCP server connects across your entire ecosystem, giving platforms secured, governed access to your live Xactly data", and the 2026-05-14 press release says "Xactly's MCP server enables cross ecosystem Agentic collaboration" and that it was "released last year". Neither page gives an endpoint, docs link, setup guide or auth method, xactlycorp.com has no llms.txt, and the official MCP registry has no xactly entry. A first-party claim without a connectable URL is unknown rather than official under law 1; the earlier thought-leadership-only reading is superseded. **Provenance** - **Entry id**: 12-xactly - **Source file**: 12-forecasting-revenue.md - **Source line**: 169 - **Tier**: RESEARCHED - **last_checked**: 2026-09-02 - **Data baked**: 2026-09-27 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).