▶ Demo: connecting your first MCP server
Module 06 demo · ~4 minutes · find, vet, connect, govern; the same moves work for any official MCP server
Repo, landscape & proofs
client-project/
.claude/ (settings, skills, agents)
research/ (the team's filed notes)
The landscape
reviewed directory · claude.ai/directory
official vendor MCP servers · the default
community directories · tens of thousands, unvetted
vetting: three questions, three real answers ✓
The connection
.mcp.json (project scope, committed)
signed in via /mcp ✓
teammate approval, one time ✓
Where a registration can live
enterprise policy · IT decides what may run at all
project · .mcp.json, committed: everyone who clones
personal · local (you, this repo) or user (you, everywhere)
Proofs
tools on the menu, prefixed ✓
real question answered through the MCP server ✓
registration removed: tools vanish ✓
registration restored: tools return ✓
where MCP servers come from
Three sources, in the order to trust them:
1. The reviewed directory at
claude.ai/directory. Listings are
reviewed before they appear.
2. Official vendor MCP servers: published
by the company that owns the
system, at that company's address.
3. Community directories: tens of
thousands of MCP servers, most by
unknown authors. Research, yes.
Client repos, no.
the three questions · official Atlassian MCP server
Who wrote it, who maintains it?
Atlassian. The company that owns
Jira and Confluence.
What does it send, and where?
Documented: your requests go to
Atlassian's own service, under the
account you sign in with.
What access will it hold?
Whatever your Atlassian account
already has. Nothing more.
Three questions, three real answers.
This one passes.
.mcp.json (the registration, committed)
{
"mcpServers": {
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/..."
}
}
}
Project scope: this file is committed,
so the connection travels with every
clone of the repo.
your browser opens · the real Atlassian login
a teammate's first session tomorrow
This project wants to use an MCP
MCP server from .mcp.json:
atlassian
https://mcp.atlassian.com/...
Use this MCP server? [Yes] [No]
One approval, once, per person. Then
their sessions have the tools too.
Nobody's Claude starts calling an
outside system without them saying
yes to it.
fresh session · the inventory
Tools available here:
Built in: Read, Write, Edit, Bash,
Grep, Glob
Skills: meeting-brief, doc-helper
Command: /weekly-log
From the atlassian MCP server:
mcp__atlassian__search
mcp__atlassian__getJiraIssue
mcp__atlassian__getConfluencePage
New hands, wearing the MCP server's name.
a real question, answered through the MCP server
You asked what was decided about
vendor pricing.
Calling mcp__atlassian__search for
"vendor pricing decision"...
Found: "Vendor pricing approach,"
Confluence, updated Aug 12. The team
agreed to hold at $180k and cite the
July analysis.
(That page content now lives in this
session's context window.)
the approved list (IT's managed settings)
Approved MCP servers, this practice:
the Atlassian official MCP server
an internal docs-platform MCP server
the GitHub official MCP server
Deployed by IT at the policy level.
An MCP server not on this list does not
run, no matter who asks, and the
answer to "can I just install this?"
was written down before anyone asked.
fresh session · after the removal
Tools available here:
Built in: Read, Write, Edit, Bash,
Grep, Glob
Skills: meeting-brief, doc-helper
Command: /weekly-log
No atlassian tools. The vendor's
MCP server is still running in their
cloud, untouched. Your repo just
stopped pointing at it.
fresh session · after the restore
Tools available here:
Built in: Read, Write, Edit, Bash,
Grep, Glob
Skills: meeting-brief, doc-helper
Command: /weekly-log
From the atlassian MCP server:
mcp__atlassian__search
mcp__atlassian__getJiraIssue
mcp__atlassian__getConfluencePage
Back on the menu.
The call path
youthe request
→
Claude Codethe client
→
Atlassian MCP serverruns in their cloud
→
Jira & Confluencethe systems
Module 06 · Demo
Connecting your first MCP server
Find it, vet it, connect it, govern it. Every prompt shown here works with any official vendor MCP server. Three parts:
1 · Find and vet
2 · Connect
3 · Govern and prove
You can do this today
Jira and Confluence, Slack, GitHub, Notion, your client's internal platforms: every one of them connects exactly this way. Find it, run the three questions, connect it at the right level, and know where the off switch is. The prompt pack walks you through your first one.
Part 1 · Find and vet
Part 2 · Connect
Part 3 · Govern and prove