Atlassian Goals & Projects MCP Server
Provides tools to fetch Atlassian Goals and their latest status updates, search Atlassian Projects, and retrieve detailed project updates including highlights and linked Jira work items.
Allows retrieval of linked Jira work items (epics/issues) with key, summary, status, and URL from Atlassian Project updates.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Atlassian Goals & Projects MCP Server What's the latest status on goal MEWS-3762?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Atlassian Goals & Projects MCP Server
An MCP server that gives AI assistants (Claude, Cursor, etc.) direct access to Atlassian Goals and Atlassian Projects via the Townsquare / Atlas GraphQL API.
Works on macOS and Windows. Each user authenticates with their own Atlassian API token.
What you can do with this MCP
Atlassian Goals
Fetch any Atlassian Goal by key (name, owner, status)
Read the latest goal status update including detailed notes
Atlassian Projects
Search Atlassian Projects with optional TQL filters and pagination
Fetch detailed project updates within a date range, including:
Status update summaries
Highlights: decisions, learnings, and risks
Linked Jira work items (epic/issue key, summary, status, URL)
Update notes
Related MCP server: Jira MCP Server
Tools
Tool | Scope | Description |
| Goals | Fetch an Atlassian Goal by key (id, name, owner, archived status) |
| Goals | Latest status update + detailed notes for an Atlassian Goal |
| Projects | Search Atlassian Projects with optional TQL filter and pagination |
| Projects | Detailed updates, highlights (decisions/learnings/risks), linked Jira items for one or more Atlassian Projects in a date range |
Prerequisites
Node.js 18+ (macOS and Windows)
A personal Atlassian API token (each user creates their own)
Your Atlassian site's Cloud ID
Step 1: Generate your Atlassian API token
Each user needs their own token. Tokens are personal and should not be shared.
Go to https://id.atlassian.com/manage-profile/security/api-tokens
Click Create API token
Give it a label (e.g. "MCP Server") and click Create
Copy the token immediately — you will not be able to see it again
Your API token inherits the permissions of your Atlassian account. It can read any Goal or Project you have access to.
Step 2: Find your Cloud ID
Visit this URL in your browser (replace yoursite with your actual Atlassian subdomain):
https://yoursite.atlassian.net/_edge/tenant_infoThe JSON response contains a cloudId field — copy that UUID value.
Step 3: Clone and build
git clone https://github.com/jaimesm-mews/atlassian-goals-projects-mcp.git
cd atlassian-goals-projects-mcp
npm install
npm run buildStep 4: Configure your MCP client
The server reads credentials from environment variables set in your MCP client config. You need four values:
Variable | Description | Example |
| Your Atlassian site URL |
|
| Your Atlassian account email |
|
| Your personal API token (from Step 1) |
|
| Site Cloud ID (from Step 2) |
|
Cursor (macOS and Windows)
Add to your Cursor MCP config (.cursor/mcp.json in your project, or via Cursor Settings > MCP):
macOS:
{
"mcpServers": {
"atlassian-goals-projects": {
"command": "node",
"args": ["/Users/yourname/atlassian-goals-projects-mcp/dist/index.js"],
"env": {
"ATLASSIAN_BASE_URL": "https://mews.atlassian.net",
"ATLASSIAN_EMAIL": "you@mews.com",
"ATLASSIAN_API_TOKEN": "your-token-here",
"ATLASSIAN_CLOUD_ID": "your-cloud-id-here"
}
}
}
}Windows:
{
"mcpServers": {
"atlassian-goals-projects": {
"command": "node",
"args": ["C:\\Users\\YourName\\atlassian-goals-projects-mcp\\dist\\index.js"],
"env": {
"ATLASSIAN_BASE_URL": "https://mews.atlassian.net",
"ATLASSIAN_EMAIL": "you@mews.com",
"ATLASSIAN_API_TOKEN": "your-token-here",
"ATLASSIAN_CLOUD_ID": "your-cloud-id-here"
}
}
}
}Claude Desktop / Claude Enterprise
Add to your Claude config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"atlassian-goals-projects": {
"command": "node",
"args": ["/absolute/path/to/atlassian-goals-projects-mcp/dist/index.js"],
"env": {
"ATLASSIAN_BASE_URL": "https://mews.atlassian.net",
"ATLASSIAN_EMAIL": "you@mews.com",
"ATLASSIAN_API_TOKEN": "your-token-here",
"ATLASSIAN_CLOUD_ID": "your-cloud-id-here"
}
}
}
}Windows users: use double backslashes in paths (
C:\\Users\\...\\dist\\index.js) or forward slashes (C:/Users/.../dist/index.js).
Example usage
Once the MCP is connected, ask your AI assistant things like:
Goals:
"Fetch the Atlassian Goal MEWS-3761"
"What's the latest status update on goal MEWS-3762?"
Projects:
"Search for all Atlassian Projects"
"Search Atlassian Projects matching key MEWS-3866"
"Get updates for Atlassian Projects MEWS-3866 and MEWS-4181 from 2026-03-24 to 2026-03-28"
Troubleshooting
Problem | Solution |
| Check that all 4 |
| Verify your email and API token are correct. Tokens expire if revoked at API token management |
| Check the goal key is correct (e.g. |
Server not appearing in Cursor/Claude | Restart the MCP client after changing config. Check the path to |
Development
npm run dev # Run with tsx (no build step, hot reload)
npm run build # Compile TypeScript to dist/
npm start # Run compiled versionLicense
MIT
Available Tools
4 toolsget_goalA
Fetch an Atlassian Goal by its key. Returns the goal's id, key, name, owner, and archived status.
Inputs: goalKey (required).
get_goal_latest_updateA
Fetch the latest status update (summary + detailed notes) for an Atlassian Goal.
Inputs: goalKey (required).
get_project_updatesA
Fetch detailed updates, highlights (decisions/learnings/risks), linked Jira items, and update notes for one or more Atlassian Projects within a date range.
Inputs: dateTo (required), dateFrom (required), projectKeys (required).
search_projectsA
Search Atlassian Projects (Townsquare). Returns project key, name, state, and pagination info. Use searchString for TQL filtering.
Inputs: after, first, searchString.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct resource and action: goal retrieval, goal update retrieval, project search, and project update retrieval. There is no overlap between goals and projects, and the update tools are clearly scoped to their respective entities.
All tools follow a verb_noun pattern with get_ or search_ prefixes. The compound name 'get_goal_latest_update' is slightly less elegant but still consistent with 'get_project_updates' and does not break the overall naming scheme.
With only 4 tools, the server is lean but appears well-scoped for a read-only informational purpose focused on goals and projects. No tools are redundant, and the count is reasonable for the apparent domain.
The surface has significant gaps: there is no way to list or search goals, and no detailed project fetch endpoint. Users must already know a goal key to retrieve it, which creates a discovery dead end. Mutation and update operations are entirely absent, limiting the server to a narrow read-only subset.
Maintenance
Related MCP Connectors
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
MCP server for AI dialogue using various LLM models via AceDataCloud
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to interact with Atlassian products (Confluence and Jira) for content management, issue tracking, and project management through a standardized interface.4,948 npm6MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for Atlassian Jira that enables AI assistants to manage issues, sprints, comments, and worklogs through natural language.MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for the Atlassian Goals API. Enables AI assistants like Claude to query, search, and update Atlassian Goals and Projects.153MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI assistants to Jira and Confluence, enabling search, create, update, and comment operations with rich Markdown-to-ADF conversion.1542 npm1MIT