Docs

What docs MCP server does

The docs MCP server gives an MCP-compatible agent access to Empryo's documentation through two documented capabilities: searching the documentation and reading documentation content. It is intended for information retrieval, such as finding an Empryo feature, locating relevant guidance, or opening a documentation page after a search.

The connected product is Empryo, a tool that works with code repositories through desktop, terminal, or headless usage.

How it works

An agent sends a documentation search or read request through MCP. Search helps locate relevant Empryo documentation, while read returns documentation content for use in the agent's response. The server does not modify documentation or other resources, so it is suitable for lookup tasks where the agent should only retrieve information.

The docs MCP server does not require authentication according to the listing. It also has no local access, which means it is not intended to read files, inspect a local repository, or use local project state as part of a lookup.

Tools and capabilities

The documented capabilities are:

• Search Empryo's documentation.
• Read Empryo's documentation.
• Retrieve documentation without authentication.
• Keep access read-only.

These capabilities support questions about Empryo's documented behavior and usage. They do not establish access to Empryo's desktop application, terminal environment, repository map, code editor, test runner, or project memory; those functions are described in the Empryo project material but are not listed as capabilities of this MCP server.

Limitations and notes

Use the docs MCP server for Empryo documentation retrieval, not for general web search or local development work. The listing explicitly rules out local access and describes the server as read-only, so an agent should not be expected to edit files, run commands, change Empryo settings, or write documentation through it.

Those details should be confirmed from the server's current distribution before deployment. No authentication setup is described either, because the listing says authentication is not required.

For teams evaluating scope, the key distinction is between documentation knowledge and codebase access.