DynamicEndpoints FAQs

Question 1

How do I use DynamicEndpoints with PocketBase?

Accepted Answer

DynamicEndpoints connects to your PocketBase instance via the Model Context Protocol (MCP).  You configure it with your PocketBase URL and, optionally, admin credentials for certain operations. Use the provided tools (like `create_collection`, `query_collection`, `backup_database`) to interact with your database.

Question 2

What is DynamicEndpoints?

Accepted Answer

DynamicEndpoints is an MCP server designed to enhance PocketBase database interactions. It offers advanced tools for schema management, data manipulation, and user authentication, going beyond PocketBase's native capabilities.

Question 3

What are the environment variables required for DynamicEndpoints?

Accepted Answer

The primary environment variable is `POCKETBASE_URL`, which specifies the URL of your PocketBase instance. Optional variables include `POCKETBASE_ADMIN_EMAIL`, `POCKETBASE_ADMIN_PASSWORD`, and `POCKETBASE_DATA_DIR` for admin access and custom data directory paths.

Question 4

What features does DynamicEndpoints offer?

Accepted Answer

It provides collection management with custom schemas and migrations, advanced querying with filtering and sorting, user authentication and token management, database backup and restore functionality, and schema validation for type safety.

Question 5

Does DynamicEndpoints support data migration?

Accepted Answer

Yes, DynamicEndpoints provides tools for migrating collection schemas while preserving your existing data. You can also define data transformations during the migration process.

DynamicEndpoints

DynamicEndpoints

Key Features

Use Cases

Key Features

Use Cases