Skip to content

Add lucid-mcp-server to community servers list in README.md #2177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

smartzan63
Copy link

@smartzan63 smartzan63 commented Jun 21, 2025

Description

This MCP server provides integration with Lucid App (LucidChart, LucidSpark, LucidScale) enabling multimodal LLMs to access and analyze Lucid diagrams through visual exports. The server implements document discovery, metadata retrieval, PNG image export, and built-in AI analysis capabilities.

Server Details

  • Server: Lucid MCP Server (lucid-mcp-server)
  • Changes to: Complete implementation with tools, AI analysis, and comprehensive testing

Motivation and Context

This implementation enables LLMs to interact with Lucid App diagrams, solving the need for multimodal AI analysis of visual diagrams. It provides:

  • Seamless integration between LLMs and Lucid workspace
  • Visual diagram analysis through AI-powered image processing
  • Document discovery and metadata access
  • Support for multiple Lucid products (Chart, Spark, Scale)

How Has This Been Tested?

  • ✅ Comprehensive unit test suite (67/67 tests passing)
  • ✅ 80%+ test coverage across all modules
  • ✅ Integration testing with MCP Inspector
  • ✅ API functionality tested with mocked Lucid services
  • ✅ Error handling and edge cases covered
  • Tested with GitHub Copilot in agent mode - successfully integrated into workflows

Breaking Changes

No breaking changes - this is the initial MVP release of the server.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client (GitHub Copilot in agent mode)
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Key Features Implemented:

  • MVP Release: Initial version with 2 core tools for Lucid App integration
  • Tools:
    • get-document - Retrieves document metadata and exports PNG images with optional AI analysis
    • search-documents - Discovers documents in the Lucid workspace with keyword filtering
  • AI Analysis: Built-in multimodal LLM analysis using Azure OpenAI GPT-4o
  • Transport Support: STDIO transport (sufficient for current workflows)
  • Comprehensive Testing: Full unit test coverage with mocked services
  • TypeScript Implementation: Fully typed with Zod schema validation

Technical Stack:

  • Model Context Protocol SDK v1.13.0
  • Official Lucid Developer API SDK
  • Azure OpenAI integration for AI analysis
  • TypeScript with comprehensive type safety
  • Vitest testing framework

Environment Variables:

  • LUCID_API_KEY (required)
  • AZURE_OPENAI_API_KEY (optional, for AI analysis)
  • AZURE_OPENAI_ENDPOINT (optional)
  • AZURE_OPENAI_DEPLOYMENT_NAME (optional)

NPM Package:

  • Initial MVP Release: Published as lucid-mcp-server@0.1.3
  • Global installation support via npm install -g
  • MIT License

image

The diagram that was analyzed in the previous screenshot

image

@smartzan63 smartzan63 force-pushed the add-lucid-mcp-server branch from 7cd7054 to 20961f6 Compare June 23, 2025 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant