- Home
- MCP servers
- Remote
Remote
- typescript
0
GitHub Stars
typescript
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
You run an MCP server that connects to Xano for tool management, session tracking, and OAuth, and you can access it locally or remotely using modern Streamable HTTP transport or legacy SSE. This guide shows practical steps to install, run, connect clients, and troubleshoot common scenarios so you can start using your MCP server with confidence.
How to use
Connect with your MCP client using either the legacy SSE transport or the latest Streamable HTTP transport. For local testing, you can run the server on your machine and point your client to the local endpoints. For remote access, deploy to a hosting environment and connect to the public endpoint.
To explore the local server with the legacy SSE transport, use the MCP Inspector and connect to the SSE endpoint. For a modern, efficient setup, use the Streamable HTTP transport with the /mcp endpoint exposed by your server. When you connect, authentication is handled via the configured Xano backend, and your session state persists across requests.
When you start a remote client such as Claude Desktop or another MCP client, point it to your deployed /mcp or /sse endpoints as appropriate. You can also test from a local client by using the local /mcp endpoint for Streamable HTTP or the /sse endpoint for SSE. Your session, tools, and OAuth state are stored in Xano so that interactions continue across requests.
How to install
# clone the repository
git clone https://github.com/roboulos/remote-mcp-server.git
# install dependencies
cd remote-mcp-server
npm install
# Configure Xano API Key
# Add your Xano API key to wrangler.jsonc in the XANO_API_KEY variable
# run locally
npm run dev
Available tools
tool_management
Defines and registers tools in Xano's ____mcp_tools table so they appear in the MCP server automatically.
session_tracking
Maintains unique session IDs for MCP interactions in Xano across requests.
oauth_auth
Stores OAuth tokens and states in Xano tables to manage authentication flows.
logging
Logs all MCP requests into the ___mcp_logs table for auditing.