Juno MCP Server
Enables AI-powered security investigation and threat analysis by connecting MCP-compatible clients to Uptycs Juno.
README
<h1> Juno MCP Server <img src="https://www.uptycs.com/hubfs/uptycs_logo_2C_on-light_rgb-1.svg" alt="Uptycs" height="32" align="right"> </h1>
MCP server for Uptycs Juno — the AI-powered security assistant.
Connect Juno to any MCP-compatible client to investigate threats, analyze findings, and manage security investigations.
What you can do
- Investigate threats — "Are there any privilege escalation attempts in the last 24 hours?"
- Follow up — "What user accounts were involved in the lateral movement?"
- Scope investigations — Target specific connectors, time ranges, and personas
- Manage investigations — List, create, and delete investigations
- Browse connectors — See which external integrations (GitHub, Splunk, AWS, etc.) are configured
- Share — Publish investigation runs for others to see
How it works
flowchart LR
Client["MCP Client"]
Server["juno-mcp-server"]
subgraph UptycsJuno["Uptycs Juno"]
Juno["AI Assistant"]
Connectors["Connectors<br/>(GitHub, Splunk, …)"]
Juno -. "calls during investigation" .-> Connectors
end
Client -- "tool calls" --> Server
Server -- "responses" --> Client
Server -- "HTTPS + JWT auth" --> Juno
Juno -- "findings, recommendations, summaries" --> Server
style Client fill:#4a90d9,stroke:#2c5f8a,color:#fff
style Server fill:#2ecc71,stroke:#1a9c54,color:#fff
style Juno fill:#e74c3c,stroke:#c0392b,color:#fff
style Connectors fill:#e74c3c,stroke:#c0392b,color:#fff
- The MCP client discovers available Juno tools via the MCP protocol
- When a tool is called, the server authenticates with your Uptycs API key (JWT) and calls the Juno API
- Juno processes the request and returns findings, summaries, and recommendations back through the server
Prerequisites
- Python 3.11+
- uv package manager
- An Uptycs account with Juno enabled
- An Uptycs API key (how to create one)
Installation
git clone https://github.com/uptycslabs/juno-mcp-server.git
cd juno-mcp-server
API key
Download your API key JSON file from the Uptycs console (Configuration > API Keys):
{
"key": "YOUR_API_KEY",
"secret": "YOUR_API_SECRET",
"customerId": "YOUR_CUSTOMER_ID",
"domain": "your-domain",
"domainSuffix": ".uptycs.net"
}
Configure your MCP client
Add the following to your MCP client configuration. Example for Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"juno": {
"command": "uv",
"args": ["--directory", "/path/to/juno-mcp-server", "run", "juno-mcp"],
"env": {
"UPTYCS_API_KEY_FILE": "/path/to/apikey.json"
}
}
}
}
Restart your MCP client. You should see Juno tools available.
Tools
Investigations
| Tool | Description |
|---|---|
create_investigation |
Start a new security investigation |
list_investigations |
List recent investigations |
get_investigation |
Get investigation details |
delete_investigation |
Delete an investigation |
Runs & Follow-ups
| Tool | Description |
|---|---|
get_run |
Get investigation run results |
create_follow_up |
Ask a follow-up question on a completed run |
Sharing
| Tool | Description |
|---|---|
publish_run |
Share a run with other users |
unpublish_run |
Unshare a run |
list_published_runs |
List shared runs |
Connectors
| Tool | Description |
|---|---|
list_connectors |
List configured external integrations (GitHub, Splunk, AWS, etc.) |
get_connector |
Get details of a specific connector |
Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
UPTYCS_API_KEY_FILE |
Yes | — | Path to your Uptycs API key JSON file |
JUNO_MCP_BLOCKING |
No | false |
Set to true to enable blocking mode (see below) |
Blocking mode
By default, create_investigation and create_follow_up return immediately with a pending run, and the client must poll get_run until the run completes.
With blocking mode enabled, these calls wait internally until the investigation completes and return the full results directly — no polling required.
{
"mcpServers": {
"juno": {
"command": "uv",
"args": ["--directory", "/path/to/juno-mcp-server", "run", "juno-mcp"],
"env": {
"UPTYCS_API_KEY_FILE": "/path/to/apikey.json",
"JUNO_MCP_BLOCKING": "true"
}
}
}
}
Note: Investigations can take several minutes to complete. In blocking mode, the tool call will wait until done.
License
Copyright Uptycs, Inc. All rights reserved.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.