Skip to main content
Glama
zackscriven

lemma_docs_mcp

by zackscriven

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LEMMA_DOCS_CORPUS_ROOTNoOverride the default corpus root directory for Lemma documentation. The default is `PPC/Product/PracticeOS/Lemma/docs/` (sibling of `MCP_Servers/`). This environment variable is optional; no environment variables are required.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
lemma_docs_contextA

Search the local Lemma (getlemma.com) documentation corpus and return focused, ranked source excerpts for a question or task. Lemma is healthcare-practice banking: entity accounts, deposit bonuses, fixed fee loans, cash sweeps, MSO-PC compliant banking guardrails, and shared onboarding. Routes the query into one of three internal namespaces (getting-started: quickstart/onboarding/KYB; guides: deposit bonuses, fixed fee loans, MSO-PC compliance, collaboration, owning multiple entities; product-updates: changelog and roadmap) and returns compact chunks with source paths. This is a local documentation index only — it NEVER calls live Lemma or banking APIs, and it cannot move money or mutate any account state.

Coverage note: the corpus is the 8 pages Lemma exposes as markdown. Banking-operations pages (accounts, cards, transactions, move money), insurance/lockbox, invoicing, team-management, and the API reference are NOT in this index — say so instead of guessing when a query needs them.

Args:

  • query (string, required): The documentation question or task, 2-500 chars.

  • namespace ('auto' | 'getting-started' | 'guides' | 'product-updates', default 'auto'): Corpus area. Use 'auto' unless you already know the area.

  • intent ('answer' | 'build_context' | 'source_map', default 'answer'): How the returned context will be used; adjusts guidance.

  • max_chunks (int 1-12, default 6): Page size.

  • offset (int >= 0, default 0): Ranked matches to skip, for paging.

  • response_format ('markdown' | 'json', default 'markdown'): Text rendering; structured content is always attached.

Returns (structured): { query, namespace, intent, guidance, chunks: [{ id, score, namespace, source_type, path, heading, excerpt, metadata }], pagination: { total_matches, count, offset, has_more, next_offset? }, follow_ups: [string], truncated?, truncation_message?, stats: { indexed_chunks, returned_chunks } }

Chunk excerpts are capped; pass a chunk's id (or its path) to lemma_docs_get for the full text.

Examples:

  • "How does the deposit bonus accrue and when is it paid?" -> guides (deposit-bonuses).

  • "Open an account for a new PLLC" -> getting-started (quickstart, KYB, beneficial owners).

  • "Does Lemma support Zelle?" -> product-updates (roadmap workaround section).

  • "What guardrails does Lemma set up for an MSO-PC structure?" -> guides (mso-pc-compliance).

  • Follow-up paging: repeat the same query with offset=pagination.next_offset.

Errors:

  • "Lemma docs corpus root not found ..." -> set LEMMA_DOCS_CORPUS_ROOT to the absolute path of the lemma-docs-*.md folder and restart.

  • Empty chunks with guidance "No strong ... matches" -> retry with a more specific Lemma term (entity, deposit bonus, fixed fee loan, cash sweep, MSO-PC), or the topic may be outside the 8-page corpus.

lemma_docs_getA

Fetch the full text of specific indexed Lemma documentation chunks by id, or every chunk of one document by its relative path. Use this after lemma_docs_context to expand excerpts you actually need — do not use it to browse (use lemma_docs_context for discovery). Reads the local corpus index only; it NEVER calls live Lemma or banking APIs.

Args:

  • ids (string[], 1-8, optional): Chunk ids exactly as returned by lemma_docs_context.

  • path (string, optional): A relative corpus path exactly as returned in a result's 'path' field; returns all chunks of that document in order.

  • response_format ('markdown' | 'json', default 'markdown'): Text rendering; structured content is always attached. At least one of ids or path is required.

Returns (structured): { found: [{ id, namespace, source_type, path, heading, text, metadata }], missing: [string], truncated?, truncation_message? }

Examples:

  • ids=["lemma-docs-docs-guides-deposit-bonuses.md#md-1-0"] -> full text of that section.

  • path="lemma-docs-docs-guides-mso-pc-compliance.md" -> every chunk of that document (may truncate; follow the truncation message).

Errors:

  • Calling with neither ids nor path returns an error explaining both options.

  • Unknown ids/paths are reported in 'missing' rather than failing the whole call.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/zackscriven/lemma-docs-mcp'

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