私がテスト・改良しているDynamicsサーバーを基にした非常に進行中のMCPサーバーです。これはPocketBaseデータベースとの高度な連携ツールを提供します。このサーバーは、Model Context Protocol(MCP)を通じた高度なデータベース操作、スキーマ管理、データ操作を可能にします。

こちらが私が使っている動画です:https://www.youtube.com/watch?v=ZuTIO3I7rTM&t=345s

なぜこれで、DynamicsEndpointsではないのか?

これは実際に最新バージョンでテストされています。現在はPocketBaseの26.1で、JavaScript-SDKの型定義に基づいて構築されており、Dynamicsの定義にある恣意的で誤った定義ではありません。多くのメソッドは動作しません。

MCPサーバーをローカルで設定する(現時点では唯一のサポート方法)

MCPサーバーをローカルで設定するには、cline_mcp_settings.jsonか、使っている(Claude、カーソル、設定は同じに見えるので、どこに保存されているかを見つけるだけです)ファイル内で設定する必要があります。やり方は以下の通りです:

1. cline_mcp_settings.jsonファイルの位置を探す: このファイルは通常、カーソルのユーザー設定ディレクトリにあります。例えば: '/Users/yourusername/Library/Application Support/Cursor/User/globalStorage/saoudrizwan.

PocketBase MCP Server

A very much in progress MCP server based off of the Dynamics one that I have been testing and refining. That provides sophisticated tools for interacting with PocketBase databases. This server enables advanced database operations, schema management, and data manipulation through the Model Context Protocol (MCP).

Here is a video of me using it: https://www.youtube.com/watch?v=ZuTIO3I7rTM&t=345s

Why This And Not DynamicsEndpoints?

This has actually been tested on the latest version. Currently 26.1 of PocketBase and is built off of the type definitions in the JS-SDK and not the arbitrary and wrong definitions found in the Dynamics one. Many of the methods don’t even work.

Setup MCP Server Locally (Only Way Supported for Now)

To set up the MCP server locally, you’ll need to configure it within your cline_mcp_settings.json or whatever you use (claude, cursor, the config looks identical you just need to find where it is stored) file. Here’s how:

1. Locate your cline_mcp_settings.json file: This file is usually located in your Cursor user settings directory. For example: /Users/yourusername/Library/Application Support/Cursor/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json

2. Configure the server: Add a new entry to the mcpServers object in your cline_mcp_settings.json file. The key should be a unique name for your server (e.g., “pocketbase-server”), and the value should be an object containing the server’s configuration.

   {
     "mcpServers": {
       "pocketbase-server": {
         "command": "node",
         "args": ["build/index.js"],
         "env": {
           "POCKETBASE_URL": "http://127.0.0.1:8090",
           "POCKETBASE_ADMIN_EMAIL": "[email protected]",
           "POCKETBASE_ADMIN_PASSWORD": "admin_password"
         },
         "disabled": false,
         "autoApprove": ["create_record", "create_collection"]
       }
     }
   }
   

   • command: The command to start the server (usually node).
   • args: An array of arguments to pass to the command. This should point to the compiled JavaScript file of your MCP server (e.g., build/index.js). Make sure the path is correct.
   • env: An object containing environment variables.
     • POCKETBASE_URL: The URL of your PocketBase instance. This is required.
     • POCKETBASE_ADMIN_EMAIL: The admin email for your PocketBase instance (optional, but needed for some operations).
     • POCKETBASE_ADMIN_PASSWORD: The admin password for your PocketBase instance (optional, but needed for some operations).
   • disabled: Whether to disable to server on startup.
   • autoApprove: list of tools to auto approve.
   • Adjust the values in the env object to match your PocketBase instance’s settings.

• Setup in vscode is similar , find or create .vscode/mcp.json and add

{
  "inputs": [
    {