Provides specialized tools for Discord Heart Reactions workflow automation through NocoDB integration, including analytics and table management for Discord reactions data
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@NocoDB MCP Servershow me the last 10 Discord reactions from the heart reactions table"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
NocoDB MCP Server
A standard FastMCP Model Context Protocol server for seamless NocoDB integration with Claude Code.
π― What This Is
This MCP server provides Claude Code users with direct access to NocoDB operations. Built using the standard FastMCP library with streamable-http transport for remote hosting. Perfect for Discord Heart Reactions workflow and other NocoDB automation projects.
Related MCP server: MySQL MCP
β¨ Features
Complete NocoDB API Integration - All CRUD operations supported
Discord Heart Reactions Optimized - Built specifically for the Discord workflow
Production Ready - Health checks, rate limiting, graceful shutdown
Docker Ready - Easy deployment with Docker or Coolify
Auto-deployment - GitHub Actions for automated builds
Comprehensive Monitoring - Built-in health checks and metrics
π Quick Deployment
Option 1: Coolify (Recommended)
Create New Resource β Docker Image
Image:
gordov1su4/mcp-server-nocodb:1.2.0Port:
3001Environment Variables:
NOCODB_API_TOKEN=your_tokenNOCODB_URL=https://nocodb.v1su4.comPORT=3001
Health Check:
/healthendpointDeploy and enjoy!
For detailed Coolify deployment instructions, see COOLIFY_DEPLOYMENT_GUIDE.md.
Option 2: Docker
Option 3: Docker Compose
π§ Environment Variables
Variable | Required | Default | Description |
| Yes | - | Your NocoDB API token (from Account Settings β Tokens) |
| No |
| NocoDB instance URL |
| No |
| Server port |
| No |
| Python output buffering |
Note: This server uses NocoDB API v3 as the primary API (requires NocoDB 0.264.0+). Latest stable: 0.265.1. It automatically falls back to v2 if v3 is not available. API v3 provides embedded relations, unified record linking, and standardized responses.
π Available MCP Tools
Note: This server uses NocoDB API v2. In API v2, "projects" are called "bases", but tool names maintain backward compatibility.
Connection & Management
nocodb_test_connection- Test NocoDB connection and list bases (projects)nocodb_list_projects- List all bases (projects in API v2 terminology)nocodb_list_tables- List tables in a base (project_id parameter is base_id)
Data Operations
nocodb_get_records- Retrieve records with paginationnocodb_create_record- Create new recordsnocodb_update_record- Update existing recordsnocodb_delete_record- Delete recordsnocodb_search_records- Search with filters
Specialized Tools
nocodb_create_discord_reactions_table- Create Discord reactions tablenocodb_get_analytics- Get Discord reactions analytics
π§ͺ Testing
Health Check
Test Connection
π Claude Code Integration
Update MCP Configuration:
{ "mcpServers": { "nocodb": { "transport": { "type": "streamable-http", "url": "https://mcp-nocodb.v1su4.com/" } } } }Restart Claude Code and enjoy NocoDB tools!
Option 2: Claude CLI (Recommended for newer versions)
Add your MCP server:
claude mcp add --transport streamable-http nocodb https://mcp-nocodb.v1su4.com/Manage existing connections:
# List all connected servers claude mcp list # Remove old connections (if needed) claude mcp remove server-nameTest the connection:
claude mcp test nocodb
ποΈ Architecture
FastMCP Server: Standard MCP server with streamable-http transport
Server-Sent Events: Real-time communication via SSE protocol
NocoDB API v3: Primary API using
/api/v3/endpoints (NocoDB 0.264.0+). Falls back to v2 if needed.
π Native MCP vs Custom MCP
NocoDB now has native MCP Server support (0.265.0+) as documented in the official MCP documentation.
β οΈ Important: Do You Still Need This Custom Server?
You may not need this custom deployment if:
β You only need standard CRUD operations (native MCP handles this)
β You're okay with one endpoint per base (native MCP is per-base)
β You want OAuth for web clients (native MCP supports this)
Keep this custom server if you need:
β Table creation (
nocodb_create_discord_reactions_table)β Custom analytics (
nocodb_get_analytics)β Cross-base operations (all bases in one server)
β Custom workflows (Python-based logic)
See MIGRATION_TO_NATIVE_MCP.md for a decision guide.
This custom server provides:
β Cross-base operations (all bases in one server)
β Custom tools (analytics, table creation)
β Works with any NocoDB version
β Single deployment for all bases
Native MCP provides:
β OAuth integration for web clients (Claude Web, ChatGPT)
β Base-specific access control
β Official NocoDB support
β No separate deployment needed
Both can be used together - Native for OAuth/web clients, custom for desktop/cross-base operations.
Self-Hosted Setup: For native MCP, use https://nocodb.v1su4.com/mcp instead of https://app.nocodb.com/mcp. See SELF_HOSTED_NATIVE_MCP_SETUP.md for details.
Compatibility: Works with NocoDB v2+ instances, compatible with n8n workflows
π Documentation
Coolify Deployment Guide - Detailed deployment instructions for Coolify
NocoDB API Setup Guide - NocoDB API configuration and setup
Troubleshooting Guide - Common issues and solutions
Docker Configuration - Container setup details
π Security
Rate limiting to prevent abuse
API token authentication required
HTTPS enforced
Comprehensive logging
Environment variable configuration
π Monitoring
Real-time health checks
Performance metrics
Request logging
Error tracking
Resource usage monitoring
π€ Contributing
Fork the repository
Create a feature branch
Make your changes
Test thoroughly
Submit a pull request
π License
MIT License - feel free to use and modify as needed.
π Support
For issues or questions:
Check the health endpoint
Review server logs
Test with the CLI tools
Check environment variables
Built for Discord Heart Reactions workflow π