Cursor rule

1---
2description: "MCP (Model Context Protocol) server configuration guidance for Cursor IDE."
3alwaysApply: false
4---
5 
6# MCP Integration Guidelines
7 
8Cursor supports the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) natively. MCP servers provide additional tools and context to AI sessions, enabling interaction with external services.
9 
10## Configuring MCP Servers in Cursor
11 
12MCP servers are configured in Cursor's settings. Navigate to:
13 
14**Settings > Features > MCP Servers**
15 
16Or add them to your project-level `.cursor/mcp.json`:
17 
18```json
19{
20  "mcpServers": {
21    "linear": {
22      "command": "npx",
23      "args": ["-y", "@linear/mcp-server"],
24      "env": {
25        "LINEAR_API_KEY": "your-api-key"
26      }
27    },
28    "filesystem": {
29      "command": "npx",
30      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/project"]
31    }
32  }
33}
34```
35 
36## Common MCP Servers for SAFe Workflow
37 
38| MCP Server | Purpose | When to Use |
39|------------|---------|-------------|
40| Linear | Ticket management, comments, status updates | All workflow (TDM, QAS, RTE agents) |
41| Confluence | Documentation publishing | Tech Writer agent, BSA specs |
42| GitHub | PR management, issue tracking | RTE agent, code review |
43| Filesystem | Extended file access | Background agents needing broad access |
44| PostgreSQL | Direct database queries | Data Engineer agent |
45 
46## SAFe Agent MCP Usage
47 
48Different agent roles use different MCP capabilities:
49 
50- **TDM**: Linear MCP for ticket coordination and status updates
51- **QAS**: Linear MCP for posting validation evidence as comments
52- **RTE**: GitHub MCP for PR creation and CI monitoring
53- **Tech Writer**: Confluence MCP for publishing documentation
54- **BSA**: Linear MCP for creating tickets, Confluence MCP for specs
55 
56## Security Considerations
57 
58- Never commit API keys or tokens to the repository
59- Use environment variables for MCP server credentials
60- Review MCP server permissions before granting access
61- Prefer read-only access where write access is not needed
62- MCP servers in background agents use the repository-level config only
63 
64## Cross-Provider MCP Compatibility
65 
66MCP servers configured for Cursor also work with other providers in this harness:
67 
68| Provider | MCP Config Location |
69|----------|---------------------|
70| Claude Code | `.claude/settings.local.json` (mcpServers key) |
71| Gemini CLI | `.gemini/settings.json` (mcpServers key) |
72| Codex CLI | Native MCP support via `codex --mcp-server` flag |
73| Cursor IDE | `.cursor/mcp.json` or Cursor settings UI |
74 
75All providers use the same MCP protocol, so servers are interchangeable. Configure once, describe in your project docs, and each provider picks up its own config.
76