Lovie Company Formation MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable verbose logging to stderr | |
| LOVIE_API_KEY | No | Bearer token — overrides stored OAuth token | |
| LOVIE_MCP_URL | No | Custom MCP server URL | https://mcp.lovie.co/mcp/mcp |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lovie_auth_requiredA | The user is not authenticated with Lovie. Tell them to run |
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
While there is only one tool, its purpose (requiring authentication) is fundamentally different from the server's claimed domain (company formation). This creates confusion about what the server actually does.
The tool name 'lovie_auth_required' does not follow a verb_noun pattern and is more descriptive of a state than an action. With only one tool, no consistent naming pattern is established.
A single tool claiming to be for company formation is far too few. The tool merely acts as an authentication gate, not a functional capability.
The tool surface is severely incomplete for company formation. No tools for company creation, banking, invoicing, etc. are actually provided despite the server name.