Vocci

What Vocci MCP server does

The Vocci MCP server exposes selected Vocci information through the Model Context Protocol. Its scope is read-only: an agent can access authorized sessions, notes, files, and memory search, but the supplied material does not indicate that it can create, edit, delete, or otherwise mutate Vocci data.

This makes the server relevant for agents that need to consult existing Vocci context while working on another task. For example, an agent may need to retrieve information from a prior session, locate a note, read an available file, or search stored memory. The available description does not identify additional Vocci resources or operations, so those four access areas define the documented scope.

How it works

Vocci MCP server access is limited to authorized Vocci sessions and related content. The MCP client connects an agent to the server, and the server exposes the supported read operations for use during an agent interaction. The provided material does not document the authorization flow, whether access is configured per user or workspace, or how search results are ranked.

Because the documented interface is read-only, using the server should not be treated as a way to manage Vocci data. Any workflow that requires writing a note, changing a file, updating memory, or modifying a session is outside the stated capability.

Tools and capabilities

The documented capabilities are:

• Reading authorized Vocci sessions.
• Reading Vocci notes.
• Reading accessible Vocci files.
• Searching Vocci memory.

The source description does not provide exact MCP tool names, input schemas, output formats, pagination behavior, or filtering options. Developers should consult the linked Vocci documentation for those implementation details before building against a specific call shape.

Limitations and notes

The Vocci MCP server is documented as read-only, so it is intended for retrieval and context lookup rather than content management. Authorization is part of the stated access model, but the supplied material does not explain how credentials are supplied, what permissions are available, or what happens when a resource is not authorized.

No installation command, transport details, required environment variables, supported MCP clients, or license information are included in the provided material. Those details should be verified in Vocci's developer documentation. The description also does not establish whether files are returned in full, whether memory search covers all stored memory, or whether sessions and notes can be searched using shared filters.