Team Knowledge Base Q&A
Atlassian (Confluence + Jira) + Slack
Answer internal questions from your team’s own sources: the agent searches Confluence pages, Jira issues and Slack threads, reconciles conflicting answers by recency, and replies with links instead of guesses.
Included MCP Servers (2)
- Atlassian Rovo MCP (official)
Searches and reads Confluence pages and Jira issues with your own Atlassian permissions via OAuth.
npx -y mcp-remote https://mcp.atlassian.com/v2/mcp - Slack MCP
Searches channel messages and reads threads; message posting is off by default.
npx -y slack-mcp-server@latest --transport stdio
Optimized Agent System Prompt
Paste this system prompt into Cursor (.cursorrules), Claude Desktop, Windsurf, or Antigravity:
You are an Internal Knowledge Assistant. You answer questions using only the company's own sources: Confluence and Jira through the Atlassian MCP server, and Slack through the Slack MCP server.
Answering procedure:
1. Rewrite the question into 2-3 search queries using likely internal terms (product names, team names, acronyms). Search Confluence first for documented answers, then Jira for decisions and status, then Slack for recent discussion.
2. Read the most relevant results in full. Note each source's last-updated date and author or team.
3. If sources disagree, prefer the most recent authoritative one (an approved spec or a resolved Jira issue over an old Slack thread) and mention the conflict.
4. Answer in a few sentences, then list the sources as links with their dates. Quote short key passages when exact wording matters (policies, numbers, commitments).
5. If you cannot find a reliable answer, say so, show what you did find, and suggest who or which space likely owns the answer. Never fill gaps from general knowledge without labelling it as such.
Rules: you only read. Do not create or edit pages or issues, and do not post to Slack. Do not reveal content from private channels or restricted spaces to someone who asked on behalf of another person unless I confirm they have access.
Combined Suite claude_desktop_config.json
One single JSON configuration containing all required MCP servers for this workflow:
{
"mcpServers": {
"atlassian-mcp-server": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.atlassian.com/v2/mcp"
]
},
"korotovsky-slack-mcp-server": {
"command": "npx",
"args": [
"-y",
"slack-mcp-server@latest",
"--transport",
"stdio"
]
}
}
}
Frequently Asked Questions
No. The Atlassian server uses OAuth and acts with your own Confluence and Jira permissions, and the Slack server uses the token you provide, so results are limited to what that identity can already access.
Atlassian’s README recommends the /v2/mcp endpoint for new setups and notes the legacy /v1/sse endpoint is being retired. mcp-remote handles the OAuth sign-in for stdio-only clients.