Quick-reference cards for every MCP server covered in the series. What each one connects, who it suits, setup complexity, and what to verify before connecting it to a live system.
Use this page as a reference when setting up a new MCP connection. Each card covers the same four things: what the server connects to, who it is for, what you check before connecting it to anything live, and how to install it.
Start with Part 1 if you want the conceptual foundation first.
GitHub MCP
Code, PRs and issues — directly from Claude
GitHub MCP lets Claude read and write in your GitHub account — create PR drafts, update issues, read diffs and fetch code. Eriksson's enterprise agentic loop is built on this connection.
Use cases
- Create PR drafts directly from agent output
- Read and comment on issues
- Fetch recent commit history into the context window
- Automate release notes from merge history
Before you connect
- What scope does the access token have? (read vs write vs admin)
- Which repos are exposed to the MCP server?
- Who approves PR creation — Claude proposes, human merges?
- Do you have an audit log for what Claude does in the repo?
npx @modelcontextprotocol/server-github
Jira MCP
Tickets, sprints and reports without leaving Claude
Jira MCP connects Claude to your Jira workspace. Adawi's pattern (project reports → steering group dashboard) and Eriksson's loop (agent loop → Jira status update → PR draft) both rely on this connection.
Use cases
- Update ticket status automatically after an agent run
- Generate a sprint summary for the steering group
- Fetch blockers and dependencies into the context window
- Create tickets from meeting transcripts
Before you connect
- API token scope: read, write or admin?
- Which project/board is exposed — entire workspace or specific project?
- Who owns ticket updates when Claude writes them?
- Do you have a verification routine for sprint state before Claude reports upward?
npx @modelcontextprotocol/server-jira
Bokio MCP
Bookkeeping and accounting for Swedish SMBs
Bokio MCP connects Claude to Bokio — the leading accounting system for Swedish SMBs. Tomic's pattern shows how Claude can handle ongoing bookkeeping, categorise transactions and prepare monthly reconciliation.
Use cases
- Categorise transactions with business context
- Prepare monthly reconciliation with explanatory text
- Answer accounting questions with real account data as grounding
- Generate VAT declaration support material
Before you connect
- Have you tested with historical data before going live?
- Who verifies that Claude categorises with the right account numbers?
- Is the access token limited to read until you trust the flow?
- Do you know who is responsible if a booking is wrong?
See Bokio API documentation
deep-thought
Deep reasoning and multi-step planning as an MCP tool
deep-thought is an MCP tool for situations where Claude needs to reason structurally and deeply — multi-step planning, complex dependency analysis, or decisions that require more than one pass. Documentation in progress.
Use cases
- Multi-step planning with structured reasoning
- Complex systems dependency analysis
- Architecture decisions with explicit reasoning chain
Before you connect
- Documentation in progress — link here when ready.