LegalForge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key used for generating the legal documents. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_legal_documentC | Generate professional legal documents (Privacy Policy, Terms of Service, Cookie Policy) using AI |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate_legal_document' has a clear and distinct purpose.
Since there is only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (generate_legal_document).
A single tool is too few for a server named 'LegalForge MCP Server', which suggests a broader legal domain. This feels thin and incomplete for generating legal documents, as it lacks supporting tools like editing, reviewing, or managing templates.
The tool surface is severely incomplete for legal document generation. While 'generate_legal_document' covers creation, there are obvious gaps such as updating, deleting, listing, or customizing documents, which are essential for a full workflow.