MCP 04009008

MCPAI代理

提供方 未标注

AI代理 stdio · 本地进程 OAuth 授权 社区 / 第三方
查看接入方式

全面解析MCP Turso NmrMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,MCP Turso Nmr能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

MCP 04009008 属于AI代理类 MCP 服务器,stdio · 本地进程,OAuth 授权,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npx changeset add\",

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP 04009008当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

11.8 KB
来自项目仓库与上游目录的原文,未做删改

mcp-turso-cloud

A Model Context Protocol (MCP) server that provides integration with
Turso databases for LLMs. This server implements a two-level
authentication system to handle both organization-level and
database-level operations, making it easy to manage and query Turso
databases directly from LLMs.

Features

🏢 Organization-Level Operations

  • List Databases: View all databases in your Turso organization
  • Create Database: Create new databases with customizable options
  • Delete Database: Remove databases from your organization
  • Generate Database Token: Create authentication tokens for
    specific databases

💾 Database-Level Operations

  • List Tables: View all tables in a specific database
  • Execute Read-Only Query: Run SELECT and PRAGMA queries
    (read-only operations)
  • Execute Query: Run potentially destructive SQL queries (INSERT,
    UPDATE, DELETE, etc.)
  • Describe Table: Get schema information for database tables
  • Vector Search: Perform vector similarity search using SQLite
    vector extensions

⚠️ IMPORTANT: Query Execution Security ⚠️

This server implements a security-focused separation between read-only
and destructive database operations:

  • Use execute_read_only_query for SELECT, read-only WITH/VALUES,
    EXPLAIN of reads, and allowlisted metadata PRAGMAs.
  • Use execute_query for INSERT, UPDATE, DELETE, CREATE, DROP,
    mutating PRAGMAs, and other operations that modify data.

Read tools always request read-only Turso credentials, including when
full-access clients are already cached. The token endpoint receives
authorization=read-only
as a query parameter. Read failures never fall back to full access.
Tokens and clients are cached separately by permission and refreshed
when tokens expire.

Local SQL validation rejects multiple statements, mutating PRAGMAs on
the read path, and file/extension functions. It is a conservative
routing check, not a complete SQL parser or a substitute for Turso's
server-side authorization. Unknown or quoted PRAGMA names require the
write tool. Compound statements containing internal semicolons (such
as trigger definitions) are not supported. Identifiers in generated
SQL are quoted; data values use bindings.

This separation allows for different permission levels and approval
requirements:

  • Read-only operations can be auto-approved in many contexts
  • Destructive operations can require explicit approval for safety

ALWAYS CAREFULLY READ AND REVIEW SQL QUERIES BEFORE APPROVING
THEM!
This is especially critical for destructive operations that
can modify or delete data. Take time to understand what each query
does before allowing it to execute.

Two-Level Authentication System

The server implements a sophisticated authentication system:

  1. Organization-Level Authentication
  • Uses a Turso Platform API token
  • Manages databases and organization-level operations
  • Obtained through the Turso dashboard
  1. Database-Level Authentication
    - Uses database-specific tokens
    - Generated automatically using the organization token
    - Cached for performance and rotated as needed

Configuration

This server requires configuration through your MCP client. Here are
examples for different environments:

Cline/Claude Desktop Configuration

Add this to your Cline/Claude Desktop MCP settings:```json
{
"mcpServers": {
"mcp-turso-cloud": {
"command": "npx",
"args": ["-y", "mcp-turso-cloud"],
"env": {
"TURSO_API_TOKEN": "your-turso-api-token",
"TURSO_ORGANIZATION": "your-organization-name",
"TURSO_DEFAULT_DATABASE": "optional-default-database"
}
}
}
}


### Claude Desktop with WSL Configuration

For WSL environments, add this to your Claude Desktop configuration:```json
{
    "mcpServers": {
        "mcp-turso-cloud": {
            "command": "wsl.exe",
            "args": [
                "bash",
                "-c",
                "TURSO_API_TOKEN=your-token TURSO_ORGANIZATION=your-org node /path/to/mcp-turso-cloud/dist/index.js"
            ]
        }
    }
}

Environment Variables

The server requires the following environment variables:

  • TURSO_API_TOKEN: Your Turso Platform API token (required)
  • TURSO_ORGANIZATION: Your Turso organization name (required)
  • TURSO_DEFAULT_DATABASE: Default database to use when none is
    specified (optional)
  • TOKEN_EXPIRATION: Expiration time for generated database tokens
    (optional, default: '7d')
  • TOKEN_PERMISSION: Permission level for generated tokens (optional,
    default: 'full-access')

API

The server implements MCP Tools organized by category:

Organization Tools

list_databases

Lists all databases in your Turso organization.

Parameters:

  • limit (integer, optional): Maximum results, default 1000, maximum
    10000
  • offset (integer, optional): Results to skip, default 0, maximum
    1000000

Responses include pagination with returned_count, has_more, and
next_offset.

Example response:```json
{
"databases": [
{
"name": "customer_db",
"id": "abc123",
"region": "us-east",
"created_at": "2023-01-15T12:00:00Z"
},
{
"name": "product_db",
"id": "def456",
"region": "eu-west",
"created_at": "2023-02-20T15:30:00Z"
}
]
}


#### create_database

Creates a new database in your organization.

Parameters:

- `name` (string, required): Name for the new database
- `group` (string, optional): Group to assign the database to
- `regions` (string[], optional): Regions to deploy the database to

Example:```json
{
    "name": "analytics_db",
    "group": "production",
    "regions": ["us-east", "eu-west"]
}

delete_database

Deletes a database from your organization.

Parameters:

  • name (string, required): Name of the database to delete

Example:```json
{
"name": "test_db"
}


#### generate_database_token

Generates a new token for a specific database. Expiration is
configured through `TOKEN_EXPIRATION`; the returned JWT is a secret.

Parameters:

- `database` (string, required): Database name
- `permission` (string, optional): Permission level ('full-access' or
  'read-only')

Example:```json
{
    "database": "customer_db",
    "permission": "read-only"
}

Database Tools

Database names are limited to 1–64 letters, digits, underscores, or
hyphens. Table/column identifiers accept 1–64 characters, excluding
null bytes; punctuation and quotes are safely escaped. A supplied
database becomes the current context only after its operation
succeeds.

list_tables

Lists all tables in a database, with pagination metadata.

Parameters:

  • database (string, optional): Database name (uses context if not
    provided)
  • limit (integer, optional): Maximum results, default 1000, maximum
    10000
  • offset (integer, optional): Results to skip, default 0, maximum
    1000000

Example:```json
{
"database": "customer_db"
}


#### execute_read_only_query

Executes one SELECT, read-only WITH/VALUES query, EXPLAIN of a read,
or allowlisted metadata PRAGMA against a database.

Parameters:

- `query` (string, required): One SQL statement, maximum 10000
  characters
- `params` (object, optional): Named parameters or contiguous
  positional keys starting at `"1"`; values must be strings, finite
  numbers, booleans, or null
- `database` (string, optional): Database name (uses context if not
  provided)
- `limit` (integer, optional): Maximum rows, default 1000, maximum
  10000
- `offset` (integer, optional): Rows to skip, default 0, maximum
  1000000

SELECT-style queries are wrapped with an outer limit/offset,
preserving any limit already present in your SQL. Metadata PRAGMA and
EXPLAIN results are sliced after fetching. Use a stable `ORDER BY`
when paging. Responses retain `result.rows` and add `pagination`
metadata.

Query result rows and column names have a 512 KiB JSON budget. If a
row cannot fit, select fewer/smaller columns (for example, `substr`).
`result.truncated` and `truncation_reason` explain omitted results;
`next_offset` is null when no row fits. BigInts are decimal strings
and blobs are `{ "type": "blob", "base64": "..." }`.

Example:```json
{
    "query": "SELECT * FROM users WHERE age > ?",
    "params": { "1": 21 },
    "database": "customer_db"
}

execute_query

Executes a potentially destructive SQL query (INSERT, UPDATE, DELETE,
CREATE, etc.) against a database.

Parameters:

  • query (string, required): One write statement, maximum 10000
    characters; includes mutating PRAGMAs and WITH-prefixed writes
  • params (object, optional): Same parameter types as the read tool
  • database (string, optional): Database name (uses context if not
    provided)

Example:```json
{
"query": "INSERT INTO users (name, age) VALUES (?, ?)",
"params": { "1": "Alice", "2": 30 },
"database": "customer_db"
}


Write result rows (such as `RETURNING`) are capped at 1000 rows and
the same byte budget. `rowsAffected` remains intact. Truncation does
not undo the write: do not rerun a write to fetch omitted rows.

#### describe_table

Gets schema information for a table.

Parameters:

- `table` (string, required): Table name
- `database` (string, optional): Database name (uses context if not
  provided)

Example:```json
{
    "table": "users",
    "database": "customer_db"
}

vector_search

Performs vector similarity search using SQLite vector extensions.

Parameters:

  • table (string, required): Table name
  • vector_column (string, required): Column containing vectors
  • query_vector (number[], required): 1–4096 finite numbers
  • limit (integer, optional): Maximum results, default 10, maximum
    1000
  • database (string, optional): Database name (uses context if not
    provided)

Example:```json
{
"table": "embeddings",
"vector_column": "embedding",
"query_vector": [0.1, 0.2, 0.3, 0.4],
"limit": 5,
"database": "vector_db"
}


## Development

### Setup

Use Node.js 24.15.0 or newer and pnpm 12.5.1 (pinned in
`package.json`). `.node-version` selects the development runtime.```bash
pnpm install
pnpm check
pnpm test

Vite+ provides the build, formatting, linting, type checking, and test
runner through vite.config.ts:

  • pnpm build — bundle the executable and declarations into dist/
  • pnpm start — run the built server with your Turso configuration
  • pnpm dev — rebuild on source changes
  • pnpm inspect — open the MCP inspector against the built server
  • pnpm check — check formatting, lint, and types
  • pnpm check:fix — apply formatting and safe lint fixes
  • pnpm format / pnpm format:check — format or check formatting
  • pnpm test — build and run offline SQL, permission, token, MCP
    handler, and CLI tests; no Turso credentials or live database access
    needed. SQL execution tests use an isolated in-memory libSQL
    database.

Dependency versions live in the pnpm-workspace.yaml catalog. New
releases must be at least two days old before installation.

Editors

Install the Oxc extension in Zed or the Vite Plus Extension
Pack
in VS Code. Checked-in .zed/settings.json and
.vscode/settings.json use Oxfmt with the shared vite.config.ts
formatting settings. Prettier configuration is no longer used.

Publishing```bash

pnpm changeset
pnpm version
pnpm check
pnpm test
pnpm release
```

pnpm release builds and publishes through Changesets. pnpm pack
can verify the package locally without publishing.

Troubleshooting

API Token Issues

If you encounter authentication errors:

  1. Verify your Turso API token is valid and has the necessary
    permissions
  2. Check that your organization name is correct
  3. Ensure your token hasn't expired

Database Connection Issues

If you have trouble connecting to databases:

  1. Verify the database exists in your organization
  2. Check that your API token has access to the database
  3. Ensure the database name is spelled correctly

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see the LICENSE file for details.

Acknowledgments

Built on:

  • Model Context Protocol
  • Turso Database
  • libSQL

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
MCP 04009008 怎么安装?

在客户端按下面的安装命令接入:npx changeset add\",。装完在客户端配置里引用同一个包或端点。

MCP 04009008 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

MCP 04009008 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP 04009008 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

MCP 04009008 能提供哪些能力?

资料显示能力标签包括 版本管理、JavaScript、构建工具、OAuth认证。具体工具清单以官方文档为准。

MCP 04009008 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

MCP 04009008 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。