I Built the First GTM-Native MCP Server — Here's What I Learned

Alex Boissonneault — Wed, 29 Apr 2026 14:50:15 +0000

When Anthropic released the Model Context Protocol (MCP) spec, most developers immediately saw database connectors, file-system tools, and API wrappers. I saw something different: a direct bridge between an AI assistant and the revenue chaos that kills most SMBs.

I've spent 15 years fixing broken go-to-market operations — seven major enterprise transformations, including work that contributed to $800M in revenue at Québecor's retail network. Every single engagement had the same root problem: the data existed, but no one could turn it into a decision fast enough.

MCP changes that equation. So I built the Artefact MCP Server — the first MCP server purpose-built for GTM revenue intelligence — and published it as open source.

Here's what I learned building it, and why the architecture decisions matter if you're thinking about AI-native revenue operations.

Why GTM Data Is Uniquely Hard for AI
Before I explain what I built, it's worth explaining why this problem is harder than it looks.

Most MCP servers solve a data-access problem: "let the AI read my calendar" or "let the AI query my database." That's valuable, but it's table stakes. The harder problem in GTM is not access — it's interpretation.

When a sales manager asks "how is my pipeline doing?", they don't want a row count. They want to know:

Which deals are at risk of stalling before month-end
Which accounts are showing expansion signals
What constraint is currently limiting revenue growth — traffic, conversion, deal size, or velocity

This requires methodology embedded alongside data access. Raw HubSpot data + an LLM produces hallucinated optimism. HubSpot data + structured analytical frameworks + an LLM produces actual intelligence.

That's the gap I built Artefact MCP to fill.

The 7 Tools: What Each One Does and Why It Exists
The Artefact MCP Server exposes seven structured tools through Anthropic's Model Context Protocol. Each one is a conversation between your AI assistant and a specific revenue framework.

1. Pipeline Signal Detection
What it does: Classifies pipeline activity into 6 signal types with evidence-backed scoring.

The 6 signal types:

Momentum Shift— acceleration or deceleration in deal progress
Stall Pattern — deals not advancing past expected timelines
Conversion Anomaly — unexpected conversion rate changes at any stage
Engagement Spike — sudden increases in prospect or customer activity
Risk Indicator — early warning signs of deal loss or churn
Expansion Signal — indicators of upsell or cross-sell opportunity

Why it exists: Most pipeline reviews are vibes dressed up as data. A rep says a deal is "progressing well" because the prospect replied to an email. This tool turns behavioral signals into scored, categorized intelligence that doesn't depend on rep optimism.

Example query: "Detect signals in my current pipeline and flag anything that needs attention this week."

2. Constraint Analysis
What it does: Uses the Revenue Formula to identify the single dominant constraint limiting your growth.
The Revenue Formula breaks down like this:

Revenue = Traffic × Conversion Rate × Average Deal Size × Velocity

Every company has one bottleneck that, if fixed, would unlock disproportionate growth. This tool identifies whether that bottleneck is:

Traffic (not enough pipeline entering the top)
Conversion (deals not progressing through stages)
Deal size (closing too small)
Velocity (taking too long to close)

Why it exists: I've watched companies spend $200K on lead generation when their real problem was a broken demo-to-proposal conversion rate of 8%. Fix the constraint, not everything.

Example query: "Analyze my pipeline data and tell me what's the primary constraint on my revenue right now."

3. Value Engine Analysis
What it does: Assesses the health of three value engines — Growth, Fulfillment, and Innovation — and reveals which one is underpowered.

The three engines:

Growth Engine — how you acquire and expand customers
Fulfillment Engine — how you deliver value and retain customers
Innovation Engine — how you build new capabilities and stay ahead

Most SMBs over-invest in the Growth Engine and ignore the other two, then wonder why churn is high or why they keep losing deals to better-featured competitors.

Example query: "Evaluate my value engines and tell me where to invest next quarter."

4. GTM Commit Drafting
What it does: Drafts structured GTM change proposals — like version control for your go-to-market strategy.

Each commit includes:

Intent — what you're changing and why
Evidence — the data supporting the change
Impact surface — what parts of the business are affected
Rollback criteria — what would trigger reverting the change

Why it exists: Most GTM changes are made on instinct and reversed on panic. Treating strategy changes like code commits — with explicit evidence requirements and rollback plans — forces rigor and creates an institutional memory.

Example query: "Draft a GTM commit for changing our ICP from SMBs under 50 employees to 50-200 employees, based on our last 6 months of deal data."

5. ICP Triangulation
What it does: Builds an ideal customer profile using three dimensions, and generates a composite fit score per account.

The three dimensions:

Company attributes — firmographics: size, industry, location, revenue band
Behavioral signals — engagement patterns, purchase history, support interactions
Growth indicators — funding rounds, hiring trends, expansion signals

Most ICPs stop at firmographics. That's like hiring based only on job title — you'll miss the best candidates and recruit expensive disappointments.

Example query: "Triangulate my ICP using my last 90 days of closed-won deals and score my current open opportunities."

6. RFM Analysis Engine
What it does: Classifies customers across 11 segments based on Recency, Frequency, and Monetary value, with pre-built retention strategies per segment.

The 11 segments:

Why it exists: Every segment needs a different intervention. Sending a win-back campaign to your Champions is not just wasteful — it's actively damaging. This tool generates segment-specific strategies automatically.

Example query: "Run RFM analysis on my customer base and tell me which segments need attention this month."

7. Pipeline Health Scoring
What it does: Generates a 0–100 pipeline health score by analyzing velocity, stage distribution, conversion rates, and deal aging.

The score factors in:

Velocity through each stage
Distribution balance (too many deals stacked in one stage = a problem)
Conversion rates stage by stage
Deal aging relative to your average sales cycle
Exit criteria compliance

Example query: "Score my pipeline health and tell me what's dragging the number down."

How to Install and Use It
The install is deliberately simple — one command, no dependency management required:

bash
pip install artefact-mcp

Then configure it in your AI assistant's MCP settings:
bash claude mcp add artefact-mcp

It works with Claude Desktop, Claude Code, and Cursor. No API key required to get started — the server ships with sample data so you can explore every tool immediately.
For live HubSpot data, upgrade to Pro (the configuration takes about 2 minutes).

Full documentation and the source code are at: github.com/alexboissAV/artefact-mcp-server

The package is published on PyPI: pypi.org/project/artefact-mcp

What I Got Wrong the First Time
The first version of Artefact MCP was basically a HubSpot API wrapper with some prompts. It was useless. An AI assistant with read access to your CRM is not intelligence — it's just a slower way to look at data you already had.
The breakthrough was embedding the methodology inside the tool definitions. Instead of returning raw pipeline data and hoping the LLM would know what to do with it, each tool returns structured, scored, categorized output that tells the AI what it means — not just what it is.
That shift — from data access to data interpretation — is what makes the difference between a party trick and a revenue advisor.

What's Next
The current release is v0.3. On the roadmap:

Multi-CRM support (Salesforce, Pipedrive) for Enterprise tier
Custom signal configurations — define your own signal taxonomy
Integration with the Artefact CRO Platform for continuous monitoring

If you're building AI-native GTM tooling or working on MCP integrations for revenue operations, I'd genuinely enjoy the conversation. Reach out at alex@artefactventures.com.

FAQ
What is the Artefact MCP Server?
The Artefact MCP Server is an open-source Model Context Protocol server that transforms AI assistants like Claude into revenue intelligence advisors. It provides seven structured tools — Pipeline Signal Detection, Constraint Analysis, Value Engine Analysis, GTM Commit Drafting, ICP Triangulation, RFM Analysis, and Pipeline Health Scoring — accessible through natural language queries.

How do I install the Artefact MCP Server?
Run pip install artefact-mcp to install, then claude mcp add artefact-mcp to configure it with Claude Desktop or Claude Code. No API key is required for sample data mode.

What AI assistants does Artefact MCP work with?
Artefact MCP is compatible with Claude Desktop, Claude Code, and Cursor. It implements Anthropic's Model Context Protocol standard.

Is Artefact MCP free?
Yes. The free tier includes all 7 tools running on sample data. The Pro tier ($149/month) adds live HubSpot data, custom RFM thresholds, and custom ICP mapping. Enterprise ($499/month) adds multi-CRM support and dedicated onboarding.

What is the difference between Artefact MCP and the HubSpot MCP Server?
HubSpot's MCP server (which reached GA in April 2026) handles CRM operations — reading and writing to contacts, deals, companies, and other objects. Artefact MCP handles revenue intelligence — analysis, scoring, signal detection, and strategic frameworks. They are complementary, not competing.

Alex Boissonneault is the founder of Artefact Ventures, a Québec-based consulting and product firm specializing in AI-native GTM systems and revenue intelligence for SMBs.

DEV Community: Alex Boissonneault

I Built the First GTM-Native MCP Server — Here's What I Learned