Gtmos
FreeNot checkedRead-only CRM audit for HubSpot that scores data integrity and finds duplicate clusters and stalled revenue using your own token.
About
Read-only CRM audit for HubSpot that scores data integrity and finds duplicate clusters and stalled revenue using your own token.
README
Read-only CRM audit for Claude: score data integrity, find duplicate clusters and stalled revenue, in your environment through your own token.
An MCP (Model Context Protocol) server that lets Claude Desktop, Claude Code, or any MCP host audit your HubSpot CRM. It runs in your environment, reads with your own HubSpot token, and no new vendor touches your data. Every tool is read-only by construction: nothing in this package writes to a CRM, sends mail, or calls any network API other than your own HubSpot endpoint.
- Zero dependencies. Pure Python stdlib (
dependencies = []). Nothing to vet transitively. - Read-only. Four tools, all audits. No write scopes needed on your token.
- Deterministic scoring. No LLM in the score path; the model reads results, it does not invent them.
- Works offline. Point the tools at a JSON export instead of a live portal and no network call happens at all.
Tools
| Tool | What it does |
|---|---|
audit_crm |
Scores contacts for data-integrity leaks: completeness, validity, freshness, ownership, consistency. Returns a portal integrity score, grade, duplicate clusters, and the weakest dimensions. Writes a full Markdown report. |
funnel_leak |
Analyses deals by stage to find stalled pipeline and where revenue leaks out of the funnel. Returns the dollar total leaking and the stalled deals behind it. |
cortex_scorecard |
Scores GTM ops health across five dimensions: data quality, lifecycle, routing, automation, reporting. Returns a weighted composite score, grade, verdict, and severity-ranked fixes sequenced into week 1 / weeks 2-4 / quarter. Writes a full Markdown report. |
ops_signals |
Terse severity-tagged signals on the GTM stack itself, not the buyer: routing SLA breaches, property drift, lifecycle integrity breaks, sync-failure proxies, with counts and top offenders. |
Install
Requires Python 3.11+.
pip install gtmos-mcp
Or from source:
pip install git+https://github.com/Kai8karma/gtmos-mcp.git
Verify:
gtmos mcp --dry-run
Expected output:
[dry-run] gtmos mcp would serve 4 tools on stdio (protocol 2025-06-18)
- audit_crm: Score a CRM export or live HubSpot portal for data-integrity leaks.
- funnel_leak: Analyse deals by stage to find stalled pipeline and where revenue leaks out of the funnel.
- cortex_scorecard: Score GTM ops health across five dimensions (data quality, lifecycle, routing, automation, reporting) from a CRM export or live HubSpot portal.
- ops_signals: Terse severity-tagged signal list on the GTM stack itself, not the buyer: routing SLA breaches, property drift, lifecycle integrity breaks, and sync-failure proxies, with counts and top offenders.
Connect to Claude
Generate the config block (always matches the installed code):
gtmos mcp --config
Then paste it into your MCP host config. For Claude Desktop that is ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
{
"mcpServers": {
"gtmos": {
"command": "gtmos",
"args": [
"mcp"
],
"env": {
"GTMOS_HUBSPOT_TOKEN": "<your-hubspot-private-app-token>"
}
}
}
}
For Claude Code:
claude mcp add gtmos --env GTMOS_HUBSPOT_TOKEN=<your-hubspot-private-app-token> -- gtmos mcp
Restart the host, then ask: "Audit my CRM and show me the weakest dimension."
Getting a HubSpot token
Create a private app in your HubSpot portal with read-only scopes: crm.objects.contacts.read for audit_crm, crm.objects.deals.read for funnel_leak. cortex_scorecard and ops_signals reuse both fetch paths, so they need whichever of those two scopes matches the inputs you give them. The token stays in your host config on your machine; this package never stores or forwards it.
No token? Use an export
Both tools accept a file instead of a live portal:
audit_crm { "contacts_file": "./contacts.json", "acv": 9000 }
funnel_leak { "deals_file": "./deals.json" }
cortex_scorecard { "contacts_file": "./contacts.json", "deals_file": "./deals.json" }
ops_signals { "contacts_file": "./contacts.json" }
contacts.json is a JSON array of contact objects (HubSpot export shape: properties.email, properties.firstname, ...). See tests/fixtures/contacts_sample.json and tests/fixtures/deals_sample.json for the exact shapes.
Marketing Cortex
cortex_scorecard is a GTM Ops Health Scorecard: it grades data quality, lifecycle, routing, automation, and reporting into one weighted composite score with severity-ranked, sequenced fixes, so you get a single number and a punch list instead of five separate reports. ops_signals is its sibling read, a terse list of what is currently breaking in the stack itself (SLA breaches, property drift, sync-failure proxies) rather than a graded score. Both are read-only and work fully offline against a contacts/deals export - no HubSpot token required.
What a run looks like
Scored 25 records.
Portal integrity score: 77.5 (B).
Duplicate clusters found: 2.
Dimension averages (worst first):
- freshness: 55.0
- ownership: 88.0
- validity: 91.9
- consistency: 93.6
- completeness: 94.6
Full report written to: ./audit-out/integrity-report.md
CLI without MCP
The same engines run directly from the shell:
gtmos audit --input contacts.json --acv 9000 # contact integrity audit
gtmos cortex --input contacts.json --deals deals.json # GTM ops health scorecard
gtmos calibrate --scores s.json --outcomes o.json # grade the scorer against real outcomes
Architecture
Newline-delimited JSON-RPC 2.0 over stdio, per the MCP stdio transport. The protocol handler (handle_message) is a pure function, message in, response out, so the whole surface is testable without spawning a process. The scoring engines are deterministic and network-free; the only network code is the optional HubSpot fetch, using your token, from your machine.
gtmos/
mcp/ stdio server + tool definitions
audit/ contact integrity engine, fetch, report
funnel/ deal-stage leak engine, fetch, report
cortex/ GTM ops health scorecard + signals engine, fetch, report
calibrate/ scorer-vs-reality grading
Tests
python -m pytest tests/
74 tests, all offline, no token required.
License
mcp-name: io.github.Kai8karma/gtmos-mcp
Installing Gtmos
This server has no published package — it is built from source. Open the repository and follow its README.
▸ github.com/Kai8karma/gtmos-mcpFAQ
Is Gtmos MCP free?
Yes, Gtmos MCP is free — one-click install via Unyly at no cost.
Does Gtmos need an API key?
No, Gtmos runs without API keys or environment variables.
Is Gtmos hosted or self-hosted?
Self-hosted: the server runs locally on your machine via the install command above.
How do I install Gtmos in Claude Desktop, Claude Code or Cursor?
Open Gtmos on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.
Related MCPs
GitHub
PRs, issues, code search, CI status
by GitHubFilesystem
Secure file operations with configurable access controls.
Memory
Knowledge graph-based persistent memory system.
Template MCP Server
A CLI tool to create a new Model Context Protocol server project with TypeScript support, dual transport options, and an extensible structure
by mcpdotdirectAmap Maps Mcp Server
MCP server for using the AMap Maps API
by duxiaohuiSupabase
Database, auth and storage
by SupabaseEverything
Reference / test server with prompts, resources, and tools.
Git
Tools to read, search, and manipulate Git repositories.
Sequential Thinking
Dynamic and reflective problem-solving through thought sequences.
Time
Time and timezone conversion capabilities.
Compare Gtmos with
Not sure what to pick?
Find your stack in 60 seconds
Author?
Embed badge for your README
Browse similar
All development MCPs
