# Dexio [Verified]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://dexio.wiki/  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/dexio

## Description
One wiki for all your agents: pages read and written over MCP, a link graph, and broken-link checks. Remote MCP server at https://app.dexio.wiki/mcp (Streamable HTTP; OAuth or a bearer API key).

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "dexio": {
    "url": "https://app.dexio.wiki/mcp"
  }
}
```

## Documentation

## What the Dexio MCP server does

The Dexio MCP server gives agents access to a shared wiki through the Model Context Protocol. Its documented capabilities cover three areas: reading wiki pages, writing wiki pages, and working with the wiki’s link structure. It also supports checks for broken links, which can help identify invalid or unavailable page references.

For the 🧠 Knowledge & Memory category, Dexio is suited to workflows where multiple agents need a common body of pages rather than isolated notes held inside one conversation or application. An agent can use the wiki as a place to retrieve existing information, add or update pages, inspect relationships between pages, and look for broken references.

## How it works

The Dexio MCP server is remote rather than a locally installed process. MCP clients connect to the Streamable HTTP endpoint at `https://app.dexio.wiki/mcp`. Once connected and authenticated, the client can expose Dexio’s wiki operations to an agent as MCP tools.

The available functionality described for the service is centered on page access and wiki maintenance. Page reads retrieve content from the wiki, while page writes let an agent add or change content. The link graph represents connections between pages, and broken-link checks identify links that do not resolve correctly. The provided material does not specify additional tool names, input schemas, or return formats.

## Setup and configuration

Configure an MCP client to use the remote endpoint `https://app.dexio.wiki/mcp`. Authentication can use OAuth or a bearer API key. The available information does not describe a local installation package, client-specific configuration format, required environment variables, or account-creation steps.

To use the Dexio MCP server, the client must support a remote MCP connection using Streamable HTTP and must be able to complete one of the supported authentication methods. The exact OAuth flow and bearer-key configuration depend on the MCP client and are not specified here.

## Tools and capabilities

The Dexio MCP server’s documented capabilities include:

- Reading pages from the Dexio wiki
- Writing pages to the Dexio wiki
- Accessing the wiki’s link graph
- Checking the wiki for broken links

These capabilities make it possible to build agent workflows around shared reference pages, connected documentation, and link maintenance. The source material does not identify whether page writes create, replace, or append content, nor does it describe filtering or traversal options for the link graph.

## Limitations and notes

Dexio requires remote connectivity to its Streamable HTTP endpoint; the provided material does not document an offline mode or local server package. OAuth and bearer API-key authentication are supported, but their detailed setup is not described. Tool names, schemas, permissions, rate limits, and client compatibility are also unspecified. Confirm those details before building a workflow that depends on particular write semantics or link-graph queries.

_Full upstream README: https://allmcps.com/mcp/dexio/readme_