Snappy MCP Server With Xano Integration

🚀 Snappy MCP Server Integration with Xano

A remote MCP server built on Cloudflare Workers, integrated with Xano database for tool management, session tracking, and OAuth. Now fully supports the latest version of the streaming HTTP transport protocol (2024-11-05).

🚀 Quick Start

📦 Local Development

# Clone the repository
git clone https://github.com/roboulos/remote-mcp-server.git

# Navigate to the project directory
cd remote-mcp-server

# Install dependencies
npm install

# Start the server
npm run dev

💻 Local Invocation of MCP Server

npx @modelcontextprotocol/inspector@latest

In the Inspector, enter your local IP address and port (e.g., http://localhost:8787/sse), then click "Connect".

💻 Connecting Claude Desktop to Local MCP Server

Update Claude's configuration file (usually located at ~/.config/claude/mcp-servers.json):

{
  "mcpServers": {
    "math": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:8787/sse"
      ]
    }
  }
}

After restarting Claude, it will be able to connect to your local MCP server.

🚀 Deployment to Cloudflare

1. Create a KV namespace:

   npx wrangler kv namespace create OAUTH_KV
   

2. Add the KV namespace ID to the wrangler.jsonc file.
3. Add your Xano API key to wrangler.jsonc.
4. Deploy the code:

   npm run deploy
   

💻 Invocation of Remote MCP Server

Invoke from the command line:

npx mcp-remote https://worker-name.account-name.workers.dev/sse

If you encounter issues, try clearing the ~/.mcp-auth file:

rm -rf ~/.mcp-auth

📚 Xano Project Setup

Create the following API endpoints:

1. /api/tools - GET - Retrieve a list of all tools.
2. /api/tools/execute/{tool_name} - POST - Execute a specific tool.
3. /api/sessions - POST - Create a new session.
4. /api/sessions/update-activity - PUT - Update session activity.
5. /api/logs - POST - Log MCP requests.

🔧 Troubleshooting

If you encounter connection issues, try the following steps:

1. Ensure the server is running.
2. Check your network configuration to ensure no firewalls are blocking the relevant ports.
3. Check the server logs for more information.