제가 테스트하고 개선해온 Dynamics 기반 MCP 서버가 매우 진행 중입니다. 이 서버는 PocketBase 데이터베이스와 상호작용할 수 있는 정교한 도구를 제공합니다. 이 서버는 Model Context Protocol(MCP)을 통해 고급 데이터베이스 운영, 스키마 관리, 데이터 조작을 가능하게 합니다.

제가 사용하는 영상입니다: https://www.youtube.com/watch?v=ZuTIO3I7rTM&t=345s

왜 이게 아니라 DynamicsEndpoints가 아닌가요?

이 기능은 최신 버전에서 실제로 테스트된 바 있습니다. 현재 PocketBase 26.1 버전이며, Dynamics 버전에서 발견된 임의의 잘못된 정의가 아니라 JS-SDK의 타입 정의를 기반으로 만들어졌습니다. 많은 메서드가 제대로 작동하지 않습니다.

MCP 서버를 로컬에서 설정하세요 (현재로서는 지원만 가능합니다)

MCP 서버를 로컬에서 설정하려면 cline_mcp_settings.json 또는 사용하는 파일(클로드, 커서, 설정은 동일해 보이지만 저장된 위치를 찾기만 하면 됩니다) 내에서 설정해야 합니다. 방법은 다음과 같습니다:

1. cline_mcp_settings.json 파일 찾기: 이 파일은 보통 커서 사용자 설정 디렉터리에 위치해 있습니다. 예를 들어: '/사용자/사용자 이름/라이브러리/애플리케이션 지원/커서/사용자/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": [
    {