Adapters Overview
RTMX adapters synchronize your requirements database with external services like GitHub Issues and Jira.
Available Adapters
Section titled “Available Adapters”| Adapter | Description |
|---|---|
| GitHub | Sync with GitHub Issues |
| Jira | Sync with Jira tickets |
| MCP | AI agent integration via Model Context Protocol |
Architecture
Section titled “Architecture”Sync Philosophy
Section titled “Sync Philosophy”RTMX uses CSV as the canonical store:
- Git-friendly: CSV diffs are human-readable
- AI-parseable: Token-efficient for LLM context
- Portable: No vendor lock-in
- Audit-ready: Full history via git
External services receive one-way pushes from the RTM:
rtmx sync github # Push changes to GitHubrtmx sync jira # Push changes to JiraDelta Tracking
Section titled “Delta Tracking”RTMX tracks changes efficiently:
# Only sync requirements that changeddelta = db.compute_delta(previous_state)# Returns: { added: [...], changed: [...], removed: [...] }This minimizes API calls and avoids rate limits.
Configuration
Section titled “Configuration”Enable adapters in rtmx.yaml:
rtmx: github: enabled: true repo: owner/repo jira: enabled: true url: https://your-org.atlassian.net project_key: PROJSecurity
Section titled “Security”- Credentials stored in environment variables
- No tokens in config files
- Minimal permission scopes requested