space-mcp
Integrates with JetBrains Space, providing tools to manage merge requests (view, list, create, close, reopen, timeline, diff) and trigger Patronus CI dry runs with TeamCity checks.
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., "@space-mcp show my open merge requests"
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.
Space MCP
MCP server and CLI for JetBrains Space merge requests and Patronus CI dry runs.
Installation
Install uv, then:
uv tool install git+https://github.com/bindreams/space-mcp.gitThis installs two entry points:
Command | Purpose |
| CLI for merge requests, CI runs, and auth |
| MCP server (stdio transport) |
Related MCP server: gitlab-mcp
Authentication
A JetBrains Space personal token is required. Generate one at Personal Tokens.
Token is resolved in order:
SPACE_TOKENenvironment variableOS keyring (stored via
space auth login)~/.config/space/credentials.json(plaintext fallback)
space auth login # store token in keyring (prompted)
space auth login --token PAT # non-interactive
space auth status # show token source and detected context
space auth logout # remove stored credentialsDuring login you will also be offered to authenticate Docker with registry.jetbrains.team.
MCP Tools
Tool | Description | Parameters |
| Get MR details (title, state, author, reviewers) |
|
| List MRs for a repository |
|
| Full MR timeline: comments, reviews, dry run results |
|
| Create a new merge request |
|
| Close a merge request |
|
| Reopen a closed merge request |
|
| Download a file attachment from MR discussion |
|
| List Patronus runs (dry runs / safe merges) for an MR |
|
| Run details with TeamCity checks and problems |
|
| Start a CI dry run for an MR |
|
| Cancel a running Patronus run |
|
Most tools return YAML; timeline returns Markdown. Parameters marked with ? are optional.
MCP server configuration
First, authenticate via the CLI — the MCP server picks up stored credentials automatically:
space auth loginThen add to .mcp.json (project) or ~/.claude.json (global):
{
"mcpServers": {
"space": {
"command": "space-mcp"
}
}
}CLI
Global options: -P/--project, -R/--repo, --json, --no-color.
Project and repo are auto-detected from the git remote when inside a Space repository.
space mr — Merge requests
space mr view [REF] # MR details (number, URL, branch, or current branch)
space mr list # list MRs (-s open|closed|merged|all, -A author, -H branch)
space mr create BRANCH # create MR from branch (-t title, -b base, -d description)
space mr close [REF] # close an MR
space mr reopen [REF] # reopen a closed MR
space mr timeline [REF] # full timeline with discussions and dry run results
space mr checks [REF] # Patronus CI check status (--watch to poll)
space mr diff [REF] # diff between target and source (--stat, --name-only)
space mr checkout [REF] # fetch and checkout the MR branch
space mr merge [REF] # safe merge via Patronus (--rebase, --squash, --dry-run)
space mr download ID # download attachment by ID (-o output path)space run — Patronus CI runs
space run list # list runs for current branch (-b branch, -B base)
space run view RUN # run details with TeamCity checks (UUID or URL)
space run start [REF] # start dry run (--merge, --rebase, --squash, --watch)
space run cancel RUN # cancel a running Patronus run
space run watch RUN # live progress with terminal animationspace auth — Authentication
space auth login # store token (--token, --insecure-storage)
space auth logout # remove credentials
space auth status # show token source and contextspace api — Raw API access
space api /api/http/... # authenticated GET to Space
space api /app/rest/... --patronus # authenticated GET to Patronus
space api /api/http/... -X POST -f key=val # POST with JSON bodyspace status — Dashboard
space status # MR and latest CI run for current branchDevelopment
See CONTRIBUTING.md for development setup and testing.
License
Copyright 2026, Anna Zhukova
This project is licensed under MPL-2.0. The license text can be found at LICENSE.md.
Available Tools
16 toolsget_attachmentDownload AttachmentA
Download a file attachment from a Space MR discussion.
Use the attachment ID from get_merge_request_timeline output (shown as [id: ...] next to each attachment).
For text files, returns the file content directly. For binary files, returns the download URL.
Args: attachment_id: Attachment UUID
Returns: File content (text) or download URL (binary).
Inputs: attachment_id (required). Returns: result
get_merge_requestGet Merge RequestA
Get details of a specific merge request.
Args: project: Project key (e.g., "ij" for IntelliJ) repository: Repository name (e.g., "ultimate") review_id: Review/MR identifier (numeric ID or full review ID)
Returns: YAML with MR title, state, author, branches, and reviewers.
Inputs: project (required), review_id (required), repository (required). Returns: result
get_merge_requestsFind Merge RequestsA
List merge requests for a repository.
Args: project: Project key (e.g., "ij") repository: Repository name (e.g., "ultimate") branch: Optional source branch name to filter by state: Optional state filter: "Opened", "Closed", "Merged", "RequiresAuthorAttention", or "NeedsReview" limit: Maximum number of results (default 1; set to 0 for unlimited) author: Optional author username to filter by (case-insensitive; an unknown username yields a clear "no such user" error)
Returns: YAML list of merge requests.
Inputs: project (required), repository (required), limit, state, +2 more. Returns: result
get_merge_request_timelineGet Merge Request TimelineA
Get the full timeline of a merge request: comments, dry runs, commits, reviews.
Returns a chronological markdown timeline with day sections, threaded replies (Patronus dry run results, safe merge status), and code review discussions.
Args: project: Project key (e.g., "ij") repository: Repository name (e.g., "ultimate") review_id: Review/MR identifier
Returns: Markdown timeline grouped by day, with threaded replies indented.
Inputs: project (required), review_id (required), repository (required). Returns: result
get_patronus_runGet Patronus RunA
Get details of a specific Patronus run including TeamCity build checks and problems.
Use the run ID from get_patronus_runs or from a Patronus URL (e.g., https://patronus.labs.jb.gg/robot/).
The returned TeamCity build IDs can be inspected further using the teamcity CLI: teamcity run view
Args: run_id: Patronus run UUID
Returns: YAML with run overview, TeamCity checks, and problems.
Inputs: run_id (required). Returns: result
get_patronus_runsList Patronus RunsA
Find Patronus runs (dry runs / safe merges) for a merge request.
Use this to discover CI dry runs and safe merge attempts for a merge request. Each run has an ID that can be passed to get_patronus_run.
Args: project: Project key (e.g., "ij") review_id: MR number (e.g., "194108")
Returns: YAML list of runs with IDs for follow-up queries.
Inputs: project (required), review_id (required). Returns: result
patch_merge_requestEdit Merge RequestA
Edit an existing merge request's title and/or description.
Omit a field to leave it unchanged; pass "" for description to clear it.
At least one of title/description is required.
Args: title: New title, or omit to leave unchanged. description: New description ("" clears it), or omit to leave unchanged.
Returns: YAML with the updated merge request.
Inputs: project (required), review_id (required), title, description. Returns: result
post_cancel_patronus_runCancel Patronus RunA
Cancel a running Patronus run (dry run or safe merge).
Args: run_id: Patronus run UUID
Returns: Confirmation message.
Inputs: run_id (required). Returns: result
post_close_merge_requestClose Merge RequestA
Close a merge request.
Args: project: Project key (e.g., "ij") review_id: MR number (e.g., "194108") or internal ID
Returns: Confirmation message.
Inputs: project (required), review_id (required). Returns: result
post_code_discussionCreate Code DiscussionA
Create an inline code discussion on a specific file and line of a merge request.
Args: project: Project key (e.g., "ij") review_id: MR number (e.g., "194108") or internal ID repository: Repository name (e.g., "ultimate") revision: Git commit SHA the comment is anchored to filename: File path (e.g., "src/main.py") line: Line number (new side of the diff) text: Comment text (Markdown supported)
Returns: Confirmation with file and line reference.
Inputs: line (required), text (required), project (required), filename (required), +3 more. Returns: result
post_delete_merge_requestDelete Merge RequestB
Delete a merge request.
Args: project: Project key (e.g., "ij") review_id: MR number (e.g., "194108") or internal ID
Returns: Confirmation message.
Inputs: project (required), review_id (required). Returns: result
post_merge_request_commentComment on Merge RequestA
Post a general comment on a merge request.
Args: project: Project key (e.g., "ij") review_id: MR number (e.g., "194108") or internal ID text: Comment text (Markdown supported)
Returns: Confirmation message.
Inputs: text (required), project (required), review_id (required). Returns: result
post_reopen_merge_requestReopen Merge RequestA
Reopen a closed merge request.
The source branch must still exist. If it was deleted on close, re-push it before reopening.
Args: project: Project key (e.g., "ij") review_id: MR number (e.g., "194108") or internal ID
Returns: Confirmation message.
Inputs: project (required), review_id (required). Returns: result
post_reply_to_code_discussionReply to Code DiscussionA
Reply to an existing code discussion on a merge request.
The discussion_channel_id can be found in the timeline output of a merge request.
Args: project: Project key (for context only) review_id: MR number (for context only) discussion_channel_id: Channel ID of the code discussion to reply to text: Reply text (Markdown supported)
Returns: Confirmation message.
Inputs: text (required), project (required), review_id (required), discussion_channel_id (required). Returns: result
put_merge_requestCreate Merge RequestA
Create a new merge request.
Args: project: Project key (e.g., "ij") repository: Repository name (e.g., "ultimate") source_branch: Branch with changes (e.g., "azhukova/fix-auth") target_branch: Branch to merge into (e.g., "master") title: MR title description: Optional MR description
Returns: YAML with created MR number, title, and branches.
Inputs: title (required), project (required), repository (required), source_branch (required), +2 more. Returns: result
put_patronus_dry_runStart Patronus Dry RunA
Start a Patronus dry run for a merge request.
Runs all configured quality checks (TeamCity builds) without merging. Use get_patronus_run to track progress.
Args: project: Project key (e.g., "ij") review_id: MR number (e.g., "194108")
Returns: Markdown with run ID, Patronus URL, and status. On failure, returns actionable guidance on what to do next.
Inputs: project (required), review_id (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool targets a distinct resource and action: read/list/create/edit/close/reopen/delete MRs, timeline, comments vs inline discussions, and Patronus run queries/actions. Singular/plural and general/inline comment distinctions are clear.
All tools follow a consistent verb_noun pattern using HTTP verbs (get, put, patch, post) with clear resource nouns. Even action-oriented names like post_close_merge_request and post_reply_to_code_discussion maintain a predictable structure.
At 16 tools, the set is slightly above the typical well-scoped range (3-15) but is justified by covering both merge request lifecycle and Patronus dry run/safe merge operations. Each tool has a clear purpose, so the count feels appropriate for the domain.
The tool surface covers full MR lifecycle (create, read, list, edit, close, reopen, delete), commenting (general and inline), replies, attachments, and Patronus run inspection/start/cancel. A minor gap is the lack of a tool to initiate a 'safe merge', though this might be intentionally excluded.
Maintenance
Related MCP Connectors
MCP server for interacting with the Supabase platform
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
A MCP server built for developers enabling Git based project management with project and personal…
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for managing your repositories on Forgejo/Gitea server.70Mozilla Public 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server for interacting with GitLab API, supporting both self-hosted instances and gitlab.com. Provides tools for managing issues, merge requests, code review, pipelines, milestones, releases, search, and file access.MIT
- AlicenseBqualityFmaintenanceMCP server for interacting with Gitea, enabling issue and PR management, repository browsing, file reading, and safe git command execution.11101 npm1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Forgejo that exposes tools for pull requests, repositories, and issues, leveraging the local fj CLI.-