# `io.github.shashwatgtm/revenue-enablement-mcp` on anlyon.dev

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by anlyon.dev. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://anlyon.dev/servers/io.github.shashwatgtm/revenue-enablement-mcp
- JSON: https://anlyon.dev/api/v1/servers/io.github.shashwatgtm/revenue-enablement-mcp
- Version: 1.2.30 (active)
- Publisher: io.github.shashwatgtm (GitHub account)
- Runs: remote (streamable-http), local (npm)
- Sign-in to list tools: none
- Repository: https://github.com/shashwatgtm/revenue-enablement-mcp
- Metadata from the official MCP Registry, synced 2026-10-21T18:49:16.374Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Revenue Enablement: 12 deal and sales enablement tools by Helix GTM Consulting
```

Scanned 2026-10-21T19:33:07.682Z over streamable-http.

**12 tools: 10 change things and 2 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 10 | ask |
| Only reads | read | 2 | allow |

## Findings

- **warn** Annotations that disagree with the tool in `account_plan_builder` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "account_plan_builder" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
```

- **warn** Annotations that disagree with the tool in `discovery_question_bank` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "discovery_question_bank" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "write": a word for a change.
```

- **warn** Annotations that disagree with the tool in `mutual_action_plan_generator` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "mutual_action_plan_generator" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "generate": a word for a change.
```

- **warn** Annotations that disagree with the tool in `win_loss_analyzer` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "win_loss_analyzer" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "write": a word for a change.
```

- **warn** Annotations that disagree with the tool in `proposal_section_writer` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "proposal_section_writer" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "write": a word for a change.
```

- **warn** Annotations that disagree with the tool in `email_sequence_generator` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "email_sequence_generator" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "write": a word for a change.
```

- **warn** Annotations that disagree with the tool in `demo_script_builder` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "demo_script_builder" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "write": a word for a change.
```

- **warn** Annotations that disagree with the tool in `champion_enablement_kit` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "champion_enablement_kit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "write": a word for a change.
```

- **warn** Annotations that disagree with the tool in `competitive_trap_setter` ([annotation-conflict](https://anlyon.dev/methodology#annotation-conflict))

```untrusted-server-text
The server marks "competitive_trap_setter" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "write": a word for a change.
```


## Changes things (10)

Creates or changes something that can be changed back. Claude Code: ask.

### `account_plan_builder`

- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Generate strategic account plans with power mapping (one row per contact you name), whitespace analysis, competitive questions and an answer for each objection. Builds a 90-day plan from the contacts, products, threats and notes you give it; it does not look the account up.
```

### `champion_enablement_kit`

- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Writes an internal selling asset for your champion, such as an executive brief, an internal business case, objection responses or presentation talking points, built from your solution, the customer's situation and the objections you expect. Returns the asset in the champion's voice with the recommendation, the answers to likely questions, the decision requested, a note on the reader and sector notes. It invents no figure or quote.
```

### `competitive_trap_setter`

- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Writes landmine questions and positioning tactics against a named competitor, so the buyer's own criteria expose its weak points without negative selling. Returns the set-up, your strengths and the competitor's weak points as you gave them, discovery questions, criteria to establish, reference call questions, requirement and scenario traps, commercial terms and stage-specific tactics, with sector notes. Every line comes from your inputs and the sector, and none from an invented fact about the competitor.
```

### `demo_script_builder`

- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Writes a demo script for the demo type, persona and use case you choose. Returns a timed run from opening to close, with spoken lines and a step for each feature you must show, tied to the pains you name, then discussion, close and follow-up lines and sector notes. The steps come from the parts of your solution and your pains, and the answer says where they came from and what it did not get.
```

### `discovery_question_bank`

- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Writes a discovery question list from the framework you choose (MEDDPICC, BANT, SPICED, Challenger, Gap Selling or all five) and what you already know about the prospect. Returns an opening for the conversation, questions in the language of the prospect's sector and on what your solution covers, the questions for each part of the framework, a closing for the call and what to say to an objection. It uses only the inputs you give and says which it did not get.
```

### `email_sequence_generator`

- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Writes a multi-email sequence by persona, stage and objective, such as prospecting, nurture, follow-up or re-engagement. Returns each email with its subject, send day and body, built from your solution, the pain point, the value proposition, your proof and the ask, and a note on what you did not give. No placeholder is left in a body, and no result or statistic is invented.
```

### `mutual_action_plan_generator`

- The description's first verb is "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Generate collaborative close plans with milestones, owners, and dates. Creates alignment between buyer and seller on path to decision.
```

### `proposal_section_writer`

- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Writes the proposal section you choose, such as an executive summary, solution overview or pricing justification, for a named buyer. Returns the section as sentences built from your solution, the buyer's challenges, your differentiators, pricing and success measures, with sector notes. It invents no figure, customer or date, and says once which inputs were not given.
```

### `roi_business_case_builder`

- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

Description, as the server wrote it:

```untrusted-server-text
Build an ROI business case from the buyer's own figures: annual_value_estimate, or current_annual_cost with expected_improvement_percent. With them it calculates the ROI, payback, three-year value and sensitivity. Without them it shows no ROI: it names the inputs to add and gives the structure of the case (the cost lines to price, your quoted results as reference points, the questions to ask).
```

### `win_loss_analyzer`

- The description's first verb is "write": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
Writes a short win/loss review of one deal, a competitor pattern or a set of deals from the details you give. Returns a write-up in plain sentences that names the outcome, the stated reason in the buyer's words, what the reason points to and what the buyer weighed, then the questions for the review call and sector notes. It adds no figure or reason you did not give, and says plainly what the outcome or reason would add when it is missing.
```

## Only reads (2)

Looks things up and changes nothing. Claude Code: allow.

### `deal_strategy_coach`

- The description's first verb is "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Get deal-specific winning strategies based on deal stage, competitive dynamics, and stakeholder positions. Provides tactical next steps and risk mitigation.
```

### `pricing_negotiation_guide`

- The description's first verb is "get": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
Get value-based pricing defense strategies and negotiation tactics. Helps maintain deal value while addressing discount requests.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `revenue-enablement`:

```json
{
  "permissions": {
    "allow": [
      "mcp__revenue-enablement__deal_strategy_coach",
      "mcp__revenue-enablement__pricing_negotiation_guide"
    ],
    "ask": [
      "mcp__revenue-enablement__account_plan_builder",
      "mcp__revenue-enablement__discovery_question_bank",
      "mcp__revenue-enablement__roi_business_case_builder",
      "mcp__revenue-enablement__mutual_action_plan_generator",
      "mcp__revenue-enablement__win_loss_analyzer",
      "mcp__revenue-enablement__proposal_section_writer",
      "mcp__revenue-enablement__email_sequence_generator",
      "mcp__revenue-enablement__demo_script_builder",
      "mcp__revenue-enablement__champion_enablement_kit",
      "mcp__revenue-enablement__competitive_trap_setter"
    ],
    "deny": []
  }
}
```