Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/bybren-llc/a-safe-pulse/31-mcp-integration)<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/31-mcp-integration"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/31-mcp-integration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/31-mcp-integration"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/31-mcp-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.00606 |
| Opus 5 | $0.00007 | $0.00303 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
31-mcp-integration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to 31-mcp-integration — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Integration Guidelines
Cursor supports the Model Context Protocol (MCP) natively. MCP servers provide additional tools and context to AI sessions, enabling interaction with external services.
Configuring MCP Servers in Cursor
MCP servers are configured in Cursor's settings. Navigate to:
Settings > Features > MCP Servers
Or add them to your project-level .cursor/mcp.json:
{
"mcpServers": {
"linear": {
"command": "npx",
"args": ["-y", "@linear/mcp-server"],
"env": {
"LINEAR_API_KEY": "your-api-key"
}
},
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/project"]
}
}
}
Common MCP Servers for SAFe Workflow
| MCP Server | Purpose | When to Use |
|---|---|---|
| Linear | Ticket management, comments, status updates | All workflow (TDM, QAS, RTE agents) |
| Confluence | Documentation publishing | Tech Writer agent, BSA specs |
| GitHub | PR management, issue tracking | RTE agent, code review |
| Filesystem | Extended file access | Background agents needing broad access |
| PostgreSQL | Direct database queries | Data Engineer agent |
SAFe Agent MCP Usage
Different agent roles use different MCP capabilities:
- TDM: Linear MCP for ticket coordination and status updates
- QAS: Linear MCP for posting validation evidence as comments
- RTE: GitHub MCP for PR creation and CI monitoring
- Tech Writer: Confluence MCP for publishing documentation
- BSA: Linear MCP for creating tickets, Confluence MCP for specs
Security Considerations
- Never commit API keys or tokens to the repository
- Use environment variables for MCP server credentials
- Review MCP server permissions before granting access
- Prefer read-only access where write access is not needed
- MCP servers in background agents use the repository-level config only
Cross-Provider MCP Compatibility
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 76 lines · 14 tokens per session scan A 67f1cf90a0fc
31-mcp-integration is a cursor rule published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 606 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to 31-mcp-integration, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.