Library access through MCP and API

One Memside connection

The authenticated Memside MCP connection can provide Memory tools, Library tools, or both. Separate settings control the two groups:

Access Memories through MCP
Access Library through MCP

Both controls are enabled by default and can be changed independently. The available MCP tool list follows the current settings.

Library operations

The connected Library tools support five public capabilities:

Tool	Purpose
`search_templates`	Search reviewed public Templates.
`get_creator_status`	Review owned Templates and recent workflow results.
`read_template`	Read a bounded owned draft.
`write_draft`	Replace the current private draft after confirming its latest revision.
`manage_template_workflow`	Create, submit, retry, publish, unpublish, or republish a Template.

Creator actions require an existing Library creator account. Public search does not grant access to private drafts or private Memside Memories.

API keys

The same Memside API key can use the corresponding versioned REST operations. Read-only keys support retrieval operations. Read-write keys are required for draft changes and publication workflow actions.

The public REST groups are:

Method	Path	Purpose
`GET`	`/library/templates`	Search public Templates.
`GET`	`/library/creator/status`	Review owned Template status.
`POST`	`/library/templates/{template_id}/read`	Read bounded owned draft content.
`PUT`	`/library/templates/{template_id}/draft`	Replace an owned private draft.
`POST`	`/library/templates/workflow`	Run an owned Template workflow action.

MCP visibility settings control MCP tool availability. API-key mode continues to follow the access mode assigned to the key.

Public catalog access

The Library also provides anonymous read-only discovery for public Templates. Anonymous access can search and read public catalog content but cannot star, download a complete Template, read private drafts, or perform creator actions.

Safety and consistency

Connected creator workflows use the same validation, review, ownership, and publication rules as the Library website. A connected tool cannot bypass review or publish content that the account does not own.

Draft writes require the latest known revision. This prevents an older tool state from silently replacing newer work. Repeated workflow requests are handled safely, and user-visible results remain available through creator status.

Generic examples

Public discovery:

Search the Library for a simple weekly planning Template.

Creator status:

List the current Template drafts and summarize any review state that needs attention.

Draft changes should remain narrow and explicit:

Update the instructions file in the selected private Template draft, then return the review status without publishing.

Detailed setup and workflows

The connected access guides separate conversational MCP use from direct REST requests:

Use Library with MCP covers permission setup, tool discovery, public search, owned draft work, review, and publication prompts.
Use the Library API covers API keys, authentication, route groups, read examples, and safe write-workflow guidance.