Company MCP

MCP servers let AI tools such as Claude work directly with our systems. Each one below signs you in through the browser with your own account, so you never need to paste a token.

Sub-categorynone-f SkillsShared Claude skills built by the team: what each one does, how to run it and how to install it. None published yet.

Servers

Atlassian (Jira)
Atlassian's remote MCP server. Lets your AI client search, read, create and update Jira tickets (and Confluence pages) using your own Atlassian permissions.
Setup
1. Make sure you can sign in to nonef.atlassian.net. If you cannot, ask for an invite first.
2. In a terminal, add the server to Claude Code:
```
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp
```
3. Start Claude Code, run /mcp, choose atlassian and sign in with your Atlassian account in the browser window that opens.
4. Using a different client (Claude Desktop, VS Code, Cursor)? Follow the vendor docs linked below; the server address is the same.
Who to ask for access
Punch
Vendor docs
Official setup guide ↗ (opens in a new tab)
GitLab
GitLab's official MCP server. Lets your AI client read and work with projects, issues, merge requests and pipelines in the none-f GitLab group, using your own GitLab permissions.
Setup
1. Make sure you are a member of the nonef1 group on GitLab.com. MCP server access must also be switched on for the group by a group owner; ask if you are not sure it is.
2. In a terminal, add the server to Claude Code:
```
claude mcp add -s user --transport http GitLab https://gitlab.com/api/v4/mcp
```
3. Start Claude Code, run /mcp, choose GitLab and sign in with your GitLab account in the browser window that opens.
4. Using a different client? Follow the vendor docs linked below.
Who to ask for access
Punch
Vendor docs
Official setup guide ↗ (opens in a new tab)

Servers

Atlassian (Jira)

Setup

GitLab

Setup