DØPEMÜX
Explore
Product guideCatalog configured

Tools in front. Infrastructure underneath.

An MCP tool surface, an HTTP application API, and a backing database solve different problems. Know which connection you are configuring.

Three roles to keep distinct

Assistant-facing tools expose operations through a client-supported transport such as stdio, SSE, or HTTP. Their presence in the catalog does not establish that a particular client can use them now.

Application APIs support local coordination or operator interfaces. An HTTP health route may only report liveness, not expose any MCP tools.

Backing infrastructure stores or transports data for other services. PostgreSQL, Qdrant, and Redis are not MCP servers by default.

Tool surfaces and adapters

Transport and exposure details live on each component page. Some adapters are optional, external, or unresolved.

Structured knowledgeCode present

ConPort

Structured project context, decisions, and progress: a place to retain the reasoning around the work, separately from the work’s historical event stream.

Explore ConPort
Work historyCode present

Dope-memory

An inspectable chronicle of work: activity records, recaps, session replay surfaces, and links between earlier events and later resolutions.

Explore Dope-memory
RetrievalCode present

Dope-context

Code and documentation retrieval for a workspace, with explicit indexing operations kept separate from normal search exposure.

Explore Dope-context
Code intelligenceUnresolved

Serena

A code-intelligence integration intended for symbol and code-relationship navigation. Its current transport declarations need qualification.

Explore Serena

Model access and backing infrastructure

These entries support the tools and services; they are not a count of connected assistants or live MCP servers.

Model infrastructureCatalog configured

LiteLLM proxy

A configured local model-access endpoint with aliases, routing, retries, and fallbacks. Inspect the actual route before relying on its label.

Explore LiteLLM proxy
Backing infrastructureCatalog configured

Qdrant

Vector-storage infrastructure supporting semantic retrieval indexes. It is a backing dependency, not automatically an assistant-facing MCP server.

Explore Qdrant

A few connection details matter

  • Task Orchestrator: the MCP wrapper’s default 7890 surface is distinct from the Python coordination service on 8000.
  • PAL: the HTTP health shim is not its reasoning-tool endpoint. The catalog’s tool route is Docker-exec stdio.
  • Serena: catalog HTTP metadata and the active SSE wrapper disagree; the transport is Unresolved here.
  • Research: contractual stdio should not be silently replaced by an auxiliary SSE surface.

No MCP handshakes, service starts, or provider calls were performed for this website. A catalog entry is configuration evidence, not operational availability.

Plan project scope separately

A worktree separates local files, but a fixed port, shared database, or event stream may still carry shared state. Check each component’s project identity and isolation boundary before running simultaneous projects.

Profile selection also affects client exposure. A profile can define a smaller toolset without establishing that every tool is installed or that each action is authorized.

Source evidence

Inspected source at the pinned reference revision. Source presence does not establish runtime health.