Skip to Content
V1MCP ServerMCP Tools

MCP Tools

The Lore MCP Server exposes the following tools via the Model Context Protocol.

lore_get

Get a Lore package by identifier and render it for the current AI runtime.

Parameters:

ParameterTypeRequiredDescription
packagestringYesPackage identifier: <namespace>/<name>:<version>
targetstringNoRuntime target override (e.g., claude-code, cursor, raw)
languagestringNoContent language (e.g., pt-BR). Defaults to en-US.

Example:

lore_get(package: "m1cloud/azure-architect:1.0.0") lore_get(package: "m1cloud/azure-architect:1.0.0", target: "cursor")

Search for packages in the registry.

Parameters:

ParameterTypeRequiredDescription
querystringYesSearch query
kindstringNoFilter by kind: Skill, Rule, Spec, Template
namespacestringNoFilter by namespace
limitnumberNoMax results (default: 10)
pagenumberNoPage of results, 0-indexed (default: 0). Use this to see results beyond the first page — the response text says explicitly when there’s more and which page to request next.

lore_resolve

Resolve dependencies for a package.

Parameters: package (string, required)

lore_list

List packages in a namespace.

Parameters: namespace (string, required), kind (string, optional), page (number, optional, 0-indexed, default 0 — see lore_search’s page above)

lore_versions

List all published versions of a package.

Parameters: package (string, required) — <namespace>/<name> without version.

Package authoring tools

On the hosted connector (mcp.lore.infraestrutura.app, Streamable HTTP transport only), an AI can also create, update, deprecate and delete packages of every kind: Skill, Rule, Spec, Template, MCPServer, Agent, Scaffold and Bundle. Nothing is written to your disk. The AI assembles the package in a draft, a private working copy held by the Registry, and publishing a draft runs exactly the same validation and permission checks as lore publish.

  • Namespace is always explicit. Authoring tools never reuse the connector’s ?org= or LORE_ORG. If you don’t say which namespace (and org) to publish to, the AI asks.
  • Permissions are unchanged. publisher can create, update and deprecate. Deleting a version requires owner.
  • Every edit is a new version. Published versions are immutable.
  • Drafts expire 24 hours after their last change. Only the person who created a draft can see it.
  • Org namespaces need an active Pro plan, and writes are refused if the plan can’t be verified.
  • Namespaces are created automatically on first publish when the Registry allows it (private under an org, public otherwise), just like lore push.
  • Publishes are attributed. The Registry records who published each version and through which client, shown as provenance in version metadata.
ToolWhat it does
lore_package_scaffoldExplains a kind’s manifest fields, file layout, size limits and a minimal valid example (read-only)
lore_package_createCreates and publishes a small package in one call: namespace, manifest (YAML), files (list of {path, content, encoding?})
lore_package_draft_createStarts a draft for a new package (namespace, org?, manifest)
lore_package_draft_put_fileWrites one file into a draft (encoding: base64 for binaries)
lore_package_draft_delete_fileRemoves one file from a draft
lore_package_draft_showShows the draft’s manifest, files and a dry-run validation; pass manifest to replace it
lore_package_draft_publishPublishes the draft (kept on failure so it can be fixed)
lore_package_draft_discardDeletes a draft
lore_package_updateOpens a draft pre-filled from a published version, targeting bump: patch|minor|major or an explicit version
lore_package_deprecateDeprecates the whole package: publishes a new patch version with status: deprecated
lore_package_deletePermanently deletes one version; confirm must repeat <namespace>/<name>:<version>. Owner only

Every file must be a declared translation (content/<lang>.md), README.md, LICENSE, or sit under a spec.include entry; anything else is reported as an error instead of being silently dropped.

Example: a Skill in one call

lore_package_create( namespace: "m1cloud", manifest: "apiVersion: lore.io/v1\nkind: Skill\nmetadata:\n namespace: m1cloud\n name: terraform-reviewer\n version: 1.0.0\n...", files: [{ path: "content/en-US.md", content: "# Terraform Reviewer\n..." }] )

Example: an MCPServer with bundled files, via a draft

lore_package_scaffold(kind: "MCPServer") lore_package_draft_create(namespace: "m1cloud", manifest: "...kind: MCPServer...spec:\n include:\n - server\nmcp: ...") lore_package_draft_put_file(draft_id: "…", path: "content/en-US.md", content: "# Jira MCP ...") lore_package_draft_put_file(draft_id: "…", path: "server/config.json", content: "{...}") lore_package_draft_put_file(draft_id: "…", path: "server/icon.png", content: "iVBORw0…", encoding: "base64") lore_package_draft_show(draft_id: "…") # fix anything listed under Validation lore_package_draft_publish(draft_id: "…")
© 2025 Lore · Built by M1 Cloud