@squirex.dev/mcp-server
Official# @squirex.dev/mcp-server
> **SquireX MCP Server** ā Agentforce Capability Scanner for AI Coding Agents
[](https://www.npmjs.com/package/@squirex.dev/mcp-server)
[](LICENSE.md)
Model Context Protocol server exposing the SquireX Agentforce Capability Scanner to AI-powered developer tools. Works with **Claude Code**, **Gemini**, **GitHub Copilot**, and any MCP-compatible IDE.
---
## Why SquireX?
Salesforce Agentforce agents use LLMs to autonomously execute Apex, Flows, and external services. Without guardrails, this creates **OWASP LLM Top 10** vulnerabilities:
- š“ **Excessive Agency** ā Agents that modify data without user confirmation
- š“ **Prompt Injection** ā User input that hijacks agent instructions
- š“ **Privilege Escalation** ā Actions running in system context without sharing
- š **Supply Chain** ā Stale API versions that silently skip metadata types
SquireX scans your Agentforce metadata with **61+ SAST rules across 27 categories** and integrates directly into your AI coding workflow.
---
## Quick Start
Add to your AI IDE configuration (Claude Code, Gemini, VS Code, JetBrains):
```json
{
"mcpServers": {
"squirex": {
"command": "npx",
"args": ["-y", "@squirex.dev/mcp-server"],
"env": {
"SQUIREX_PROJECT_DIR": "/path/to/your/salesforce/project"
}
}
}
}
```
That's it. Your AI agent now has access to the Agentforce Capability Scanner.
---
## MCP Surface
### Tools (16)
#### Core Scanning (Primary Value)
| Tool | Description |
|------|-------------|
| `scan_agentforce` | Run all 61+ SAST rules against the project. Returns SARIF. |
| `scan_agentforce_file` | Scan a single metadata file (`.genAiFunction-meta.xml`, `.agent`, etc.) |
| `scan_agentforce_rule` | Run a specific rule (e.g., `AGENTFORCE-1.1`) |
#### Rule Intelligence
| Tool | Description |
|------|-------------|
| `list_scan_rules` | List all 61+ rules with ID, category, severity |
| `get_rule_details` | Deep dive: description + remediation guidance |
| `explain_violation` | Root-cause analysis for a specific violation |
| `suggest_fix` | Generate a code/metadata fix suggestion |
#### Apex Testing & Schema
| Tool | Description |
|------|-------------|
| `run_tests` | Execute Apex tests locally using the Go interpreter |
| `get_coverage` | Extract line-level code coverage data |
| `analyze_schema` | Aggregate inferred SObject schema from the codebase |
| `predict_conflicts` | Predict merge conflicts between branches |
| `generate_sarif_report` | Generate SARIF for CI/CD pipeline integration |
#### Testing Center Bridge
| Tool | Description |
|------|-------------|
| `generate_dx_tests` | Convert scan violations ā Agentforce DX test YAML for Testing Center |
| `validate_dx_tests` | Validate DX test spec syntax and schema |
| `push_to_testing_center` | Push test spec to Salesforce via `sf agent test run` |
| `get_testing_center_results` | Get status/results of a Testing Center test run |
### Resources (6)
| URI | Description |
|-----|-------------|
| `squirex://scan/rules` | Complete 51+ rule catalog |
| `squirex://scan/rules/{id}` | Rule detail with remediation |
| `squirex://scan/results/latest` | Latest scan results (SARIF) |
| `squirex://schema/objects` | Inferred SObject schema |
| `squirex://test-results/latest` | Latest Apex test results |
| `squirex://coverage/latest` | Latest code coverage |
### Prompts (4)
| Prompt | What It Does |
|--------|-------------|
| `review-agentforce-security` | Full 51+ rule scan ā prioritized remediation plan |
| `fix-agentforce-violation` | Diagnose + fix a specific violation |
| `harden-agent-metadata` | Proactive defense-in-depth review |
| `generate-test-evaluation` | Generate Agentforce DX test YAML specs for Testing Center |
---
## Agentforce Capability Scanner ā 61+ Rules
| # | Category | Rules | Severity |
|---|----------|-------|----------|
| 1 | **Action Configuration** | Mandatory Confirmation, Schema Sync, Privilege Analysis | š“ Critical / š High |
| 2 | **Agent Script Safety** | Validation Guards, Transition Integrity, Prompt Injection Defense | š“ Critical / š High |
| 3 | **Grounding Security** | Hardcoded Secrets, FLS Masking Alignment | š“ Critical / š High |
| 4 | **Structural Dependency** | Planner Completeness, Deactivation Collision, Evaluation Governance | š High / š” Medium |
| 5 | **Flow Security** | Flow Context/Silent State/Injection, API Injection, PT Poisoning/Activation | š“ Critical / š High |
| 6 | **Supply Chain Security** | API Downgrade, Schema Desync, Managed Package Origin | š High / š” Medium |
| 7 | **Agentic Architecture** | Topic Bloat, Skill Semantics, Orphaned Bot Evaluation | š High / š” Medium |
| 9 | **Instruction Integrity** | Metadata Instruction Poisoning, Cross-Topic Boundary | š“ Critical / š High |
| 10 | **Operational Reliability** | Validation Conflict | š” Medium |
| 11 | **Autonomous Scheduling** | Unguarded Scheduled Action, Time-Window Privilege Drift | š“ Critical / š High |
| 12 | **Copilot Studio Config** | Memory Poisoning, API Version Drift | š“ Critical |
| 13 | **Data Cloud Grounding** | RAG Without Schema Classification | š“ Critical |
| 14 | **Slack Integration** | Slack Bot Without DLP Guard | š High |
| 15 | **External Service Security** | Certificate Pinning, Dynamic Cloaking RAG | š High |
| 16 | **Custom Permission** | Agent Action Without Permission Gate | š High |
| 17 | **Commerce** | Idempotency Key, Amount Bounds Check | š“ Critical |
| 18 | **Multi-Agent Orchestration** | Compositional Fragment Trap, Sybil Identity | š“ Critical / š High |
| 19 | **Platform Event / CDC** | Sub-agent Spawning Loop, CDC Field Filter | š“ Critical / š High |
| 20ā24 | **OWASP LLM Top 10** | Excessive Agency, Data Exfil, SSRF, DoS, MCP Auth | š“ Critical / š High |
| 30ā34 | **Enterprise Graph** | PII Graph, Privilege Graph, Blast Radius, MCP Scope, XSS Graph | š“ Critical / š High |
---
## Supported Metadata Types
- `.genAiFunction-meta.xml`
- `.genAiPlugin-meta.xml`
- `.genAiPlannerBundle-meta.xml`
- `.genAiPromptTemplate-meta.xml`
- `.genAiPromptTemplateActv-meta.xml`
- `.agent` files
- `.cls` (Apex classes)
- `.trigger` (Apex triggers)
- `.namedCredential-meta.xml`
- `.connectedApp-meta.xml`
- `.field-meta.xml`
- `.aiEvaluationDefinition-meta.xml`
- `.flow-meta.xml`
- `schema.json`
- `sfdx-project.json`
- `package.xml`
- LWC components (`.js` in `lwc/` dirs)
---
## How It Works
```
AI Coding Agent (Claude / Gemini / Copilot)
ā
ā MCP Protocol (stdio)
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāā
ā @squirex.dev/mcp-server ā ā This package
ā 16 tools, 6 resources ā
ā 4 prompts ā
āāāāāāāāā¬āāāāāāāāāāāāāāāāāā
ā spawn
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāā
ā squirex CLI ā
ā scan / generate-tests ā ā Testing Center bridge
āāāāāāāāā¬āāāāāāāāāāāāāāāāāā
ā JSON IPC
ā¼
āāāāāāāāāāāāāāāāāāāāāāāāāāā āāāāāāāāāāāāāāāāāāāāāāā
ā squireinterp ā ā sf agent test run ā
ā Go Execution Engine ā ā (Salesforce CLI) ā
ā 61+ SAST Rules ā ā ā Testing Center ā
āāāāāāāāāāāāāāāāāāāāāāāāāāā āāāāāāāāāāāāāāāāāāāāāāā
```
The Testing Center bridge tools delegate to `squirex generate-tests`, which:
1. Runs a capability scan (or reads existing SARIF)
2. Converts violations to Agentforce DX test YAML (all 61+ rules, normalized `AGENTFORCE-X.Y` IDs)
3. Optionally validates and pushes to the Salesforce Testing Center via `sf agent test run`
---
## Requirements
- Node.js ā„ 18
- `squirex` CLI installed (or available via npx)
- A Salesforce project with Agentforce metadata
---
## GitHub App Integration
For automated PR scanning, install the [SquireX GitHub App](https://github.com/apps/squirex) ā one-click setup, 51+ rule scan on every pull request, SARIF in your Security tab.
| Plan | Public Repos | Private Repos | Price |
|------|-------------|---------------|-------|
| Free | Unlimited | ā | $0 |
| Pro | Unlimited | 1 | $49/repo/month |
| Enterprise | Unlimited | Unlimited | $299/org/month |
---
## License
Proprietary ā See [LICENSE.md](LICENSE.md)
Copyright Ā© 2026 SquireX. All Rights Reserved.
---
<sub>ā” Built by <a href="https://squirex.dev">SquireX</a> ā Securing the AI Agent Pipeline</sub>
TDQS
Scored across 16 tools
Most tools have clear, distinct scopes (scan whole project vs. specific file vs. specific rule; explain vs. suggest fix). The only minor overlap is between scan_agentforce and generate_sarif_report, both of which output SARIF, which could cause an agent to pick the wrong one when a report artifact is needed.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (scan_agentforce, list_scan_rules, generate_sarif_report, push_to_testing_center). The verbs are predictable and clearly indicate the action, making the set easy to navigate.
With 16 tools, the server is slightly over the typical 3-15 well-scoped range, but each tool serves a distinct purpose within the two main workflows (scanning and testing). The count feels justified and not bloated, so it earns a 4 rather than a 3.
The tool surface covers the full scanning lifecycle (run scans, list rules, get details, generate reports, explain and suggest fixes) and the testing workflow (run tests, get coverage, generate/validate/push test specs, retrieve results). Minor gaps include no direct way to apply suggested fixes or retrieve historical scan results, but these are workable.