From cowork-with
Guides MCP setup for Atlassian and Figma integration. Use when the user needs to set up, configure, or troubleshoot MCP server connections for Jira, Confluence, or Figma.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cowork-with:cowork-with-onboardingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Walk the user through setting up their environment for the cowork-with plugin.
Walk the user through setting up their environment for the cowork-with plugin.
This plugin requires two globally installed MCP servers: Atlassian (for Jira + Confluence) and Figma. The plugin itself does not bundle MCP servers — users install them once at the global level and all projects benefit.
Before guiding installation, check if MCP servers are already configured:
cat ~/.claude/.mcp.json 2>/dev/null to check for existing configatlassian and/or figma entries exist, skip to Step 2 for the already-configured server(s)atlassianUserInfo and whoami (Figma) to verify authentication — if both succeed, skip to CompletionThe user needs to add MCP servers to their global Claude Code configuration. Run these commands in their terminal (outside Claude Code):
claude mcp add --transport sse -s user atlassian https://mcp.atlassian.com/v1/sse
claude mcp add --transport http -s user figma https://mcp.figma.com/mcp
The -s user flag installs at the user level so the MCP servers are available across all projects.
After running these commands, ask the user to restart Claude Code (Ctrl+C and relaunch) so the new MCP servers are loaded.
After restart, the user needs to authenticate each server.
Tell the user to:
/mcp and press Enteratlassian from the listTell the user to:
/mcp and press Enterfigma from the listAuthentication is complete when the user returns to Claude Code with a success message for both servers.
For a smoother workflow, suggest allowing MCP tools without per-call prompts. The user can add this to their project's .claude/settings.json or global ~/.claude/settings.json:
{
"permissions": {
"allow": [
"mcp__atlassian__*",
"mcp__figma__*"
]
}
}
If MCP servers aren't showing up:
cat ~/.claude/.mcp.jsonatlassian and figma entries are presentIf authentication fails:
/mcp and select the server to re-authenticateAfter authentication succeeds, confirm readiness and display available commands:
Setup Status:
Available Commands:
| Command | Description |
|---|---|
/cowork-with:cowork-with-jira | Jira workflow — issue creation, status transitions, sprint queries, epic management |
/cowork-with:cowork-with-wiki | Wiki workflow — read product docs, search Confluence, manage personal pages |
/cowork-with:cowork-with-figma | Figma workflow — design-to-code, design tokens, Code Connect, screenshots |
/cowork-with:cowork-with-onboarding | Re-run this setup guide |
npx claudepluginhub labrinyang/cowork-with-marketplace --plugin cowork-withManages Jira issues with JQL, Confluence pages with CQL, sprint workflows, and MCP server authentication for Atlassian API integrations.
Generates .mcp.json and .claude/settings.json to configure MCP servers, tokens, and tool permissions for agent-flow pipeline. Supports CLI flags for tracker type, instance URL, and source control remote.
Configures MCP (Model Context Protocol) servers for Claude Code to connect to external tools, databases, APIs, and services like Jira, Sentry, PostgreSQL, Figma, Slack via HTTP, SSE, or stdio with authentication.