Developer · Local MCP server
Grain
Run SQL queries and inspect database schemas through safe, visible MCP tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.pattrnlabs/grain- Version
- 0.10.20
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- pattrnlabs (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/pattrnlabs) · how
- Website
- grain.tools
- Repository
- github.com/pattrnlabs/grain
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | grain-tools | 0.10.20 | stdio |
How to connect Grain
Grain runs locally from a Node.js package published to the npm registry: grain-tools version 0.10.20. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y grain-tools@0.10.20. It reads these environment variables: GRAIN_CONNECTIONS (secret), GRAIN_MCP_SAFE_MODE and GRAIN_MAX_ROWS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"grain": {
"command": "npx",
"args": [
"-y",
"grain-tools@0.10.20"
],
"env": {
"GRAIN_CONNECTIONS": "<secret>",
"GRAIN_MCP_SAFE_MODE": "<value>",
"GRAIN_MAX_ROWS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| GPU ServerMCP server for GPU monitoring: nvidia-smi, VRAM, utilization, temperature. | Local · stdio |
| GPUQuant AI InfrastructureSearch AI infrastructure, inspect facility evidence and explore sourced company relationships. | Remote · HTTPLive check: ✓ handshake |
| GRAFOMEM CGR CaptureRecord agent judgments and their real outcomes on GRAFOMEM Cloud. Capture now, score later. | Local · stdio |
| GrafyxReal-time codebase graph for AI assistants: call graphs, dependencies, symbol lookup. | Local · stdio |
| GramClawManage Telegram outreach, campaigns, follow-ups, conversations, and pipelines from an MCP client. | Remote · HTTP |
| GranethPre-flight check for AI coding agents: hallucinated packages + secrets, 6 ecosystems, no account. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| GraphifySearch indexed code, trace dependencies, assess change impact, and recall repository memory. | Remote · HTTPLive check: sign-in required |
| GraphkeeperMines git history for file co-change patterns into a queryable knowledge graph via MCP. | Local · stdio |