Nile Mcp

Created By
niledatabasea year ago
MCP server for Nile Database - Manage and query databases, tenants, users, auth using LLMs
Overview

What is Nile MCP?

Nile MCP is a Model Context Protocol server implementation for the Nile database platform, enabling LLM applications to manage and query databases, tenants, users, and authentication through a standardized interface.

How to use Nile MCP?

To use Nile MCP, install the package via npm, configure your environment variables, and start the server. You can then interact with the server using natural language commands through applications like Claude Desktop or Cursor.

Key features of Nile MCP?

  • Database Management: Create, list, get details, and delete databases.
  • Credential Management: Create and list database credentials.
  • SQL Query Support: Execute SQL queries directly on Nile databases.
  • Comprehensive error handling and user-friendly messages.
  • Type Safety: Written in TypeScript with full type checking.

Use cases of Nile MCP?

  1. Managing multiple databases for different applications.
  2. Executing SQL queries for data retrieval and manipulation.
  3. Integrating with LLM applications for enhanced database interactions.

FAQ from Nile MCP?

  • Can Nile MCP manage multiple databases?

Yes! Nile MCP allows you to create and manage multiple databases seamlessly.

  • Is Nile MCP free to use?

Yes! Nile MCP is open-source and free to use.

  • How do I start the server?

You can start the server by running node dist/index.js after building the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
niledatabase
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago