Skip to main content
Glama
jefedeoro

JauMemory MCP Server

by jefedeoro

berrry_create_tool

Create a Berrry app and register it as a JauMemory tool in one step by providing file contents or remixing an existing app.

Instructions

Create a new Berrry app AND register it as a JauMemory tool in one step.

INPUT MODES (mutually exclusive — pass exactly one): • files_json — JSON array of files: [{"name":"index.html","content":"..."}, ...]. index.html is required. Each file ≤ 2 MB. • remix_from — subdomain of an existing Berrry app to fork.

NOTE: Berrry's NOMCP API does NOT expose AI-prompt-based generation. The "describe your app idea" feature on berrry.app/create is web-form-only. Through this tool, you must supply finished file contents (or remix an existing app). If you want AI to write the files, generate them in your assistant first, then pass them as files_json.

VISIBILITY (optional, default "public"): • public — all tiers • unlisted — Pro+ only • private — Pro+ only Non-public values return 403 if the account isn't on Pro; the tool surfaces a friendly upgrade hint and rolls back the JauMemory tool entry.

REQUIRES: a vault credential containing your Berrry NOMCP token (brry_rw_*). Store it once with vault_store, then pass nomcp_credential_id on every call.

AFTER CREATE: Use tool_call with the returned slug to hit the app's HTTP API at .berrry.app. Use path_suffix "__nomcp/..." with the same slug to manage app files/versions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name for the tool (defaults to subdomain)
tagsNoTags for categorization and search
auth_pathNoAuthentication path: "user" (API key) or "agent" (Ed25519). Default: "user"
subdomainYesSubdomain for the new app (e.g. "data-cleaner" for data-cleaner.berrry.app)
files_jsonNoJSON array of finished file contents: [{"name":"index.html","content":"..."}, {"name":"api.js","content":"..."}]. index.html is required. Each file ≤ 2 MB. NOTE: this field expects literal file contents — there is no prompt-based generation on the NOMCP API. Have your assistant write the HTML/JS first, then pass it here.
remix_fromNoSubdomain of an existing app to remix/fork instead of providing files
visibilityNoApp visibility: "public" (default, all tiers) | "unlisted" (Pro+) | "private" (Pro+). Berrry returns 403 if your tier does not include the requested level.
descriptionNoDescription of what the app/tool does
nomcp_credential_idYesUUID of the vault credential containing your Berrry NOMCP token
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses behavioral traits: creation+registration, credential requirement, visibility tier restrictions with 403 error and upgrade hint, file size limits, mutual exclusivity of inputs, and post-creation API usage. It also clarifies the API's lack of prompt-based generation. Thorough and honest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (INPUT MODES, VISIBILITY, REQUIRES, AFTER CREATE). It is front-loaded with the main purpose. While somewhat lengthy for a tool description, every sentence adds necessary information and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multi-step creation, credential handling, tier restrictions, error responses, post-creation usage), the description covers all aspects comprehensively. It explains return value (slug) implicitly and addresses edge cases like visibility 403 and rollback. No output schema exists, but the description provides sufficient guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds meaningful context beyond schema fields: highlights mutual exclusivity of files_json and remix_from, specifies that index.html is required within files_json, explains visibility defaults and tier requirements, and notes the auth_path default. This adds significant value over the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Create a new Berrry app AND register it as a JauMemory tool in one step.' This is a specific verb+resource+outcome that clearly defines the tool's purpose and distinguishes it from potential sibling tools like berrry_register_tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: mutually exclusive input modes, visibility tier requirements, credential prerequisites, and post-creation steps. It also explains when to generate files in the assistant vs. using the API. However, it does not explicitly compare to sibling tools or state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jefedeoro/JauMemory-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server