Connecting tools

tsh-core bundles three MCP servers. Two of them need one interactive sign-in each, once per machine; the third needs nothing.

Server	Gives Claude	Sign-in
Atlassian	Jira work items and Confluence pages, read and updated directly	Browser login via /mcp
Figma	Designs: layout, variables, components and a rendered export	Browser login via /mcp
Context7	Current, version-specific library documentation	None

Sign in

Run /mcp inside a Claude Code session:

/mcp

Pick atlassian, finish the browser sign-in, then do the same for figma. You are done on this machine, for every project.

Both servers are remote and OAuth-authenticated, so every call runs under your own account and grants nothing you could not already open in Jira or Figma yourself. Atlassian works with Atlassian Cloud only; Figma is available on all seats and plans.

Plugin-provided servers appear in /mcp as plugin-provided. You can disable one per project from the same panel.

If you skip a sign-in

Nothing else breaks. The server simply shows as needing authentication.

• Figma: agents that need a design report what is missing rather than guessing at one. The UI verification gate in tsh-product-engineering reports VERIFICATION NOT RUN instead of judging a design it cannot read.
• Atlassian: Jira and Confluence access is unavailable. For example, e2e-engineer reads acceptance criteria from a Jira issue key through this server, and without it you supply the criteria directly.

What is deliberately left out

Two connections are not bundled, because each would fail for most people. Both are documented, with an opt-in command, in the tsh-core README.

• Bitbucket. The Atlassian server exposes Bitbucket Cloud only under API-token authentication, never OAuth. That needs an Atlassian org admin to enable it first, the Bitbucket workspace linked to the organisation, and a scoped token per person. See The Atlassian connector.
• Figma's desktop server. It is a separate local endpoint, served by the desktop app with Dev Mode enabled. It shows as a failed connection for anyone not running the desktop app, and it needs a Dev or Full seat on a paid plan, where the remote server needs neither. See The Figma connector.

Other servers and tools

Context7 is hosted, read-only and needs nothing on your machine. The servers shipped by the cloud plugins and the Playwright CLI are not part of tsh-core and have their own requirements, listed in the integrations overview.