Skip to content

Conversation

xR0am
Copy link
Contributor

@xR0am xR0am commented Jul 26, 2025

🚀 Add MCP ElizaOS Data Server - Real-time Plugin & Repository Analytics

Overview

This PR introduces a complete MCP (Model Context Protocol) server that exposes ElizaOS ecosystem data through real-time API endpoints. The server is distributable via npx and provides structured access to plugin statistics, repository metadata, and ecosystem analytics.

🎯 Key Features

Real Data Integration

  • ✅ Fetches live data from https://elizaos.github.io/data/
  • ✅ Dynamic plugin discovery through HTML parsing
  • ✅ Real-time statistics from daily stats JSON files
  • ✅ Zero mock data - all endpoints use actual ElizaOS data
  • ✅ Graceful error handling for network issues

MCP Framework Implementation

  • ✅ Built with mcp-framework for automatic tool discovery
  • ✅ STDIO transport (default) for seamless client integration
  • ✅ Standalone tool files in src/tools/ directory
  • ✅ Zod schemas with comprehensive descriptions
  • ✅ Type-safe with MCPInput<this> pattern

NPX Distribution Ready

  • ✅ Packaged for npx mcp-elizaos-data installation
  • ✅ TypeScript build process with validation
  • ✅ Works with MCP clients (Cursor, Claude Desktop, etc.)
  • ✅ Simple configuration via mcp-config-example.json

🛠️ Core Tools Implemented

Tool Description Real Data Source
list_available_plugins List all plugins with filtering & sorting elizaos-plugins_plugin-* directories
get_plugin_stats Fetch plugin statistics & activity Daily stats JSON files
get_repository_data Repository metadata & contributors Repository directories
get_summary_data Ecosystem overview & trends Summary/dump directories

📊 Example Usage

List Blockchain Plugins:

{
  "total_plugins": 2,
  "plugins": [
    {
      "name": "plugin-evm",
      "directory": "elizaos-plugins_plugin-evm", 
      "status": "active"
    },
    {
      "name": "plugin-solana",
      "directory": "elizaos-plugins_plugin-solana",
      "status": "active"
    }
  ],
  "categories": ["blockchain", "social", "ai", "automation", "integration", "data"],
  "filter_applied": "blockchain",
  "source": "Real data from ElizaOS GitHub Pages"
}

cursoragent and others added 9 commits July 26, 2025 02:11
- Add human-readable formatted text as first content block
- Include emojis, clear structure, and localized formatting
- Keep comprehensive JSON data as second content block for LLM processing
- Fixes double-encoded JSON issue for better client readability
- Maintains full data access for programmatic use
- Return single formatted string instead of content array
- MCP framework handles content structure automatically
- Include human-readable text with embedded JSON code blocks
- Eliminates duplicate content blocks
- Follows MCP Framework documentation pattern
- Tools now return clean data for framework to manage
- Completely removed all mock/fallback data
- Tools now fetch data directly from ElizaOS GitHub Pages directory structure
- Parse HTML directory listings to discover plugins dynamically
- Extract real statistics from actual stats JSON files
- Show real PRs, issues, and activity data
- Provide detailed error messages when real data unavailable
- No more fake/generated data - only authentic ElizaOS information

REAL DATA SOURCES:
- https://elizaos.github.io/data/elizaos-plugins_plugin-*/
- Daily stats: /stats/day/stats_YYYY-MM-DD.json
- Summaries: /summaries/*.json
- Directory discovery via HTML parsing
- Tools now return clean JSON objects instead of formatted strings
- MCP Framework handles content structure automatically
- Completely removed ALL remaining mock data from all tools
- GetRepositoryDataTool: Fetches real repo data from ElizaOS structure
- GetSummaryDataTool: Searches for real summary/dump directories
- All tools return structured JSON with proper error handling
- No more double-encoded strings or content arrays
- Follows MCP Framework documentation patterns exactly

OUTPUT NOW: Clean JSON objects that MCP clients can properly consume
BEFORE: Double-encoded strings with escaped content
✅ SOLVED: MCP Framework output issue
- Set useStringify = true (correct setting)
- Return JSON objects directly from execute()
- Framework properly stringifies with JSON.stringify()
- Output is now clean, parseable JSON in content.text
- No more [object Object] or double-encoding issues

BEFORE: '[object Object]' or double-encoded strings
NOW: Clean JSON that clients can parse properly

🎯 All tools now return properly formatted JSON data
📊 Real data from ElizaOS GitHub Pages (no mock data)
🔧 Follows MCP Framework patterns exactly
Copy link

coderabbitai bot commented Jul 26, 2025

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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.

2 participants