Connect once. Keep the project state in Immensity.

Immensity exposes one hosted Streamable HTTP MCP endpoint. Compatible clients connect to that endpoint, detect OAuth, send you to Immensity in the browser to approve access, and then discover the current tool surface.

The endpoint

Production MCPStreamable HTTP

https://mcp.useimmensity.com/mcp

Do not add an API key, bearer token, or project token to the configuration. Immensity uses browser-based OAuth.

Generic remote MCP configuration

Clients that accept standard MCP JSON can use this configuration:

mcp.jsonNo static credentials

{
  "mcpServers": {
    "immensity": {
      "url": "https://mcp.useimmensity.com/mcp"
    }
  }
}

OAuth is the security boundary

The client should receive an authentication challenge, open the Immensity authorization flow, and store the resulting OAuth tokens itself. Your credentials do not belong in MCP JSON.

Connection flow

Add Immensity

Install the Immensity integration or add the hosted MCP URL to the client.

Authorize

The client detects the protected resource and opens Immensity's browser approval flow.

Discover tools

After OAuth succeeds, the client reads the current tool definitions directly from the live MCP server.

Select project context

List and select an existing project, or search for a problem and create a new project.

Verified connection paths

Client	Connection	Authentication
Cursor	Remote MCP / one-click install	Browser OAuth
Codex	Remote MCP	Browser OAuth
JetBrains Junie	Global or project MCP config	Browser OAuth
JetBrains AI Chat	Use an agent such as Junie or an agent-native Codex connection	Handled by that agent

JetBrains AI Assistant's native MCP client currently reaches the protected endpoint but does not initiate the OAuth flow. Use Junie or an agent that already has Immensity configured instead.

What the host model does

The connected model performs the reasoning for MCP Analysis and Build generation. Immensity provides the grounded data, exact output schemas, validation, versioning, project state, and persistence.

This separation keeps the MCP workflow portable across clients instead of forcing every integration through a second Immensity model call.

Troubleshooting

401 before authorization

A 401 from the MCP endpoint before OAuth is expected. A compatible client should treat it as an authentication challenge and begin authorization.

Connected but no project selected

Ask the agent to call list_projects, then select_project, or start with search_problems and create_project_from_problem.

Tool list looks stale

Reconnect or refresh the MCP connection. The tools are discovered from the live remote server; normal backend tool updates do not require editing the local JSON.

Previous← Quickstart NextSearching →