How to connect SDLC integrations

Connect Notion, Atlassian, and the GitHub CLI so AI-enabled SDLC skills can create project documents, Jira issues, and draft pull requests. Install EOS plugins first. See How to consume the EOS plugin marketplace.

Do not treat an EOS plugin as a substitute for these services. engineering@eos and product@eos supply the workflows. The official Notion and Atlassian integrations supply account access. gh supplies GitHub access.

Scout is optional. For Scout install and first setup, see How to use Scout.

Choose the integration you need

Set up only the service that the next stage requires.

Integration	Required by
Notion	Project setup, PRD, TSD, implementation plan, and ticket creation
Atlassian	Bug, enhancement, and spike tickets, project ticket creation, and implementation
Authenticated GitHub CLI (`gh`)	Implementation and pull-request creation

If the service already works in your agent, stop. Do not reinstall it.

Connect Notion

Prefer the official Notion plugin or app for Cursor, Claude Code, and Codex. Install it from that agent's marketplace, then complete sign-in.

In Claude Code, you can install the official plugin from a terminal outside the active session:

sh

claude plugin install notion@claude-plugins-official

Use the official remote MCP server only when the agent has no marketplace plugin. Follow the Notion MCP setup guide. The server URL is https://mcp.notion.com/mcp.

Restart or reconnect the agent only when its install flow requires it. Then confirm that Notion tools are visible, for example notion-search or notion-fetch.

Connect Atlassian

Prefer the official Atlassian plugin or app for Cursor, Claude Code, and Codex. Install it from that agent's marketplace, then complete sign-in.

In Claude Code, you can install the official plugin from a terminal outside the active session:

sh

claude plugin install atlassian@claude-plugins-official

Use the official remote MCP server only when the agent has no marketplace plugin. Follow the Atlassian Rovo MCP setup guide. The server URL is https://mcp.atlassian.com/v1/mcp/authv2.

Restart or reconnect the agent only when its install flow requires it. Then confirm that Atlassian tools are visible, for example getJiraIssue.

Install and authenticate the GitHub CLI

Install gh from the GitHub CLI instructions, then authenticate:

sh

gh auth login

Confirm the session:

sh

gh auth status

/implement and /raise-pr need gh on PATH. Complete authentication before those stages. APM also uses gh to register the EOS marketplace. See How to consume the EOS plugin marketplace.

Confirm the result

Run /ask-eos and ask it to check your setup. The readiness flow reports whether Notion, Atlassian, and the GitHub CLI are ready. It does not install or reconnect anything unless you ask it to.

Treat a capability as ready only when the primary tool is present:

Notion tools are visible in the agent.
Atlassian tools are visible in the agent.
gh is on PATH. Authenticate before GitHub workflows if gh auth status reports no active account.

If a required integration is still missing, complete that section above, then run the readiness check again.

When the required services are ready, continue with How to use the AI-enabled SDLC.