Koskamo

Liminal MCP

Liminal MCP provides a shared intelligence workspace for complex research and reasoning tasks. It allows agents to break down questions, check capabilities, find saved work, and receive grounded answers with visible sources and reasoning steps. The server supports cross-session handoffs, context compression, and tool delegation, enabling continuous work without rebuilding context.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Liminal MCP logo, by Physea LabsVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-06Operated by Physea Labs
You need:Create an account with an email and a passwordSend x-api-key: <key> or Authorization: Bearer <key>The first 50 solves on a new key are free; no card required
MCP endpoint (Streamable HTTP)
https://liminality.physea.ai/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to physea.ai ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Ask a question and receive a grounded answer with its basis and state
  • Check what Liminal can do now and whether it is ready
  • Find saved work and continue without rebuilding its context

Source and maintenance

Vendor evidenceRegistry 1.0.6
Maintenance checked

Protocol and capabilities

Server
Liminal 1.27.2
MCP protocol negotiated in check
2025-11-25
Tools
Sign-in required
Resources
Sign-in required
Resource templates
Sign-in required
Prompts
Sign-in required
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  },
  "experimental": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Liminal keeps your work, sources and handoffs, shared with the Liminal app. Short or direct task: use at most ONE Liminal call, or none. - focus(text=<URL or text>, task=...): instead of opening any page, file or log over 8,000 characters; answer from the returned verbatim passages. - research: a web research question answered with cited findings. - solve: ambiguous, consequential or multi-step decisions; it never claims a write executed. - read: results and sources you already have. - handoff: to continue earlier work call handoff(action="resume", subject=<name>) once; it returns the saved state. To pass work on call handoff(action="create", subject=..., task=..., session_state=<what is done and found>, evidence=...) once. One call each side; no extra notes, list or read. get_capabilities lists every tool; all are callable by name.

Tools

Sign-in required

No tool definitions available.

Prompts

Sign-in required

No prompt definitions available.

Resources

Sign-in required

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1353 ms
95th percentile latency
1353 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1353 ms · metadata changed · refuses unauthenticated tools/list (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http liminal-mcp https://liminality.physea.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add liminal-mcp --url https://liminality.physea.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable liminal-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "liminal-mcp": {
      "url": "https://liminality.physea.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "liminal-mcp": {
      "type": "streamableHttp",
      "url": "https://liminality.physea.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start liminal-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "liminal-mcp": {
      "type": "http",
      "url": "https://liminality.physea.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http liminal-mcp https://liminality.physea.ai/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://liminality.physea.ai/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "liminal-mcp": {
      "serverUrl": "https://liminality.physea.ai/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Liminal MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Liminal MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing