Atlassian MCP Server vs Locize

A side-by-side look at the Atlassian MCP Server and Locize MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Atlassian MCP Server logoAtlassian MCP ServerVersion Control · Remote HTTP/SSEOfficial remote MCP server for Atlassian. Securely connect Jira, Confluence, Jira Service Management, Bitbucket, and Compass to Claude, ChatGPT, Cursor, VS Code, and other AI tools using OAuth 2.1 or API tokens.80ExcellentAuth: other
L
LocizeTranslation Services · Remote HTTP/SSE
Locize MCP server: read/write translations, publish versions, manage branches from AI assistants.42FairAuth: not declared

Verdict: choose Atlassian MCP Server for version control work over a hosted endpoint; choose Locize for translation services over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Atlassian MCP Server logoChoose Atlassian MCP Server when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: other.
Explore Atlassian MCP Server

L
Choose Locize when

  • You need dedicated capabilities in the Translation Services domain.
  • You prefer a remote HTTP/SSE transport.
Explore Locize

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAtlassian MCP Server logoAtlassian MCP Server
L
Locize
CategoryVersion ControlTranslation Services
Quality signal80/100 · Excellent42/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthotherNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars1,118—
Directory activity 9 views 0 installs 1 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Atlassian MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Locize tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Atlassian MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "atlassian-mcp-server": {
      "url": "https://mcp.atlassian.com/v2/mcp"
    }
  }
}

Locize

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "locize": {
      "url": "https://www.locize.com/docs/integration/mcp"
    }
  }
}

Frequently asked questions

Atlassian MCP Server is categorized under Version Control and uses a remote HTTP/SSE transport. Locize belongs to Translation Services and uses a remote HTTP/SSE transport. Pick Atlassian MCP Server for version control work and Locize for translation services.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Atlassian MCP Server is listed as free. Auth: other. Locize has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add atlassian-mcp-server and locize as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Atlassian MCP Server has a quality signal of 80/100 (Excellent) with 9 views, 0 installs and 1,118 GitHub stars. Locize has 42/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.