This MCP server provides a complete Parse Server-like API integrated with the MCP (Model Context Protocol). It supports data reading (get objects by ID, queries with filters, counts, and aggregation), data writing (create, update, delete, batch operations, and array/number field manipulations), schema management (create/get/update/delete class and fields), security features (roles, users, ACLs, and Class Level Permissions), and Cloud Functions (call cloud functions and run background jobs). You can run the server with Node.js using npm start for production or npm run dev for development with file watching. The server exposes REST endpoints inspired by Parse, enabling clients to perform standard CRUD, schema management, and security operations through HTTP requests. The included environment variables in .env or in your MCP config control the Parse connection and security behavior, including enabling self-signed certificates for development when necessary. Use the provided npm scripts and the configuration examples to integrate this MCP server into your workflow or editor/tooling like Claude Desktop or VS Code.

Prerequisites:

• Node.js (version compatible with the project, typically LTS)
• npm (comes with Node.js)
• Git (optional, for cloning)

Steps:

1. Clone the repository (or download the source): git clone https://github.com/emanuelmartin/mcp-parse-server.git cd mcp-parse-server

2. Install dependencies: npm install

3. Create a .env file (or rely on environment variables) with the necessary Parse configuration. Example: PARSE_URL=https://tu-parse-server.com/parse PARSE_APP_ID=tu-app-id PARSE_REST_KEY=tu-rest-key PARSE_MASTER_KEY=tu-master-key

   Optional for development only

   ALLOW_SELF_SIGNED_CERT=true

4. Start the server: npm start

5. (Optional) Development mode with watch: npm run dev

6. If you export an MCP config, ensure the mcp_config section points to the correct entry file (index.mjs) and sets the appropriate environment variables.

Tips and common notes:

• The MASTER KEY is optional but required for schema, roles, and certain administrative operations. Keep it secure and only use in development or tightly controlled environments.
• Do not enable ALLOW_SELF_SIGNED_CERT in production; use valid TLS certificates and set the corresponding NODE_TLS_REJECT_UNAUTHORIZED behavior accordingly.
• When deploying, ensure the Parse server URL (PARSE_URL) is reachable by clients and that network/firewall rules permit traffic to the Parse API endpoints.
• If integrating with Claude Desktop or VS Code, you can embed the mcpServers configuration with the node entry and the required environment variables as shown in the README example to streamline testing.
• Review the Readme’s usage and examples to understand how to structure requests for schema creation, role management, and Cloud Function invocation.