Skip to main content
A Server-Sent Events (SSE) MCP server runs as an HTTP service — either on your local machine or hosted remotely. MIRA connects to it via a URL, making SSE servers ideal for shared team tooling and hosted APIs.

​
Prerequisites

  • The SSE server must be reachable from your machine (local port or public URL).
  • The server must implement the MCP SSE transport spec: GET /sse to open the event stream, POST /message to receive requests.

​
Add the server in MIRA

1

Open Settings

Press ⌘, and navigate to MCP Tools.
2

Click Add Server

Click the + Add Server button.
3

Select transport

Choose SSE from the Transport dropdown.
4

Enter the server URL

Type the base URL of the MCP server (without /sse).Examples:
EnvironmentURL
Local dev serverhttp://localhost:3001
Docker containerhttp://host.docker.internal:3001
Remote serverhttps://mcp.mycompany.com
5

Add HTTP headers (optional)

Click Add Header to inject authentication or custom headers.
Authorization: Bearer your-api-key
Header values are stored in the OS keychain. They are never logged or included in exports.
6

Give the server a name

Enter a short name (e.g. company-tools). This becomes the tool namespace prefix.
7

Set scope

Choose Session or Global. See Session vs Global.
8

Save and connect

Click Save. MIRA opens the SSE stream and calls list_tools. Discovered tools appear in the server card.

​
Connection status

StatusMeaning
🟢 ConnectedSSE stream open; tools discovered
🟡 ConnectingWaiting for the server to respond
🔴 ErrorConnection failed; hover for detail

​
Security considerations

  • Use HTTPS for any remote SSE server to protect tool arguments and results in transit.
  • MIRA does not validate the server’s TLS certificate for self-signed certificates on localhost (http://localhost:*). For all other hosts, a valid certificate is required.
  • API keys in the Authorization header are stored in the OS keychain, not in the MIRA database.

​
Troubleshooting

SymptomFix
Error: ECONNREFUSEDServer is not running on the specified port
Error: 401 UnauthorizedCheck that the Authorization header value is correct
Tools list is emptyEnsure the server returns a valid list_tools response
Stream drops after 30 sAdd keep-alive pings to the server; MIRA reconnects automatically after 5 s
Edit this page — Open a pull request