Gryz

What Gryz does

Gryz provides shared context for AI assistants and a workspace for managing information that should persist beyond one conversation. Memory entries can represent personal preferences, project facts, or decisions, while private notes provide a scratchpad that is not published to the web. Assistants can also create and maintain shareable Markdown or HTML documents.

The workspace includes Projects for organizing documents and notes, Skills for reusable assistant instructions, and Tasks with status, priority, assignee, due date, subtasks, and linked resources. Agents can also access connected MCP servers through Gryz when those connections are enabled in the Gryz dashboard.

How it works

The service is exposed through a streamable HTTP MCP endpoint:

https://www.gryz.ai/api/mcp

An MCP client connects with OAuth or a bearer API key. OAuth sign-in behavior depends on the client; API keys can be created from the Gryz account page and sent as Authorization: Bearer YOUR_API_KEY.

Memory is scoped as personal or project data and can be recalled by relevance and recency. Notes have per-note AI access settings that distinguish collaboration from read-only access. Documents can be public or private, and owners control whether assistants may read, edit directly, or submit suggestions for approval.

Document writes support optimistic concurrency through revision values. Passing a document revision back as if_match causes the write to be refused if the document changed after it was read. Restoring a prior revision creates a new version rather than rewriting history.

Setup and configuration

Add the remote server URL to an MCP client that supports streamable HTTP. VS Code can install Gryz from its MCP extension search or add the URL through the MCP server command. Cursor accepts the URL in its MCP settings, and Windsurf provides Gryz through its Cascade marketplace. Claude supports adding the URL as a connector. Other compatible clients can use the same endpoint.

After connection, agent_onboarding can configure the assistant for Gryz and answer usage questions. It is read-only on Gryz; changes to a local instruction file require explicit approval.

Tools and capabilities

Memory tools include remember, recall, list_memories, and forget. Notes can be listed, retrieved, created, appended, updated, or deleted.

Document tools cover publishing, retrieval, listing, replacement, appending, targeted edits, revision history, restoration, suggestions, and deletion. Targeted edits can replace text, modify sections, add table rows, or update checklist items, with a dry_run option for previews.

Project tools list and retrieve hubs and associate or disassociate documents. Skill tools list, retrieve, fork, create, update, and delete reusable instructions. Task tools create, list, retrieve, and update work items.

broker_list_tools and broker_call_tool expose enabled tools from connected MCP servers. Comment tools list, add, and delete agent-authored comments on eligible documents.

Limitations and notes

Gryz requires a Gryz account for OAuth or API-key access. Skill creation and forking depend on account plan levels. Document and comment operations are governed by permissions, ownership, and approval settings. Deleted notes are briefly restorable from the dashboard, while deleted skills retain their history through soft deletion.