parse-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PARSE_APP_ID | Yes | Your Parse application ID | |
| PARSE_MASTER_KEY | No | Master key required for admin operations (e.g., creating classes, managing users, running cloud functions) | |
| PARSE_SERVER_URL | Yes | The URL of your Parse Server instance (e.g., http://localhost:1337/parse) | |
| PARSE_JAVASCRIPT_KEY | No | Optional JavaScript key for additional security |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-objectA | Create a new object in a Parse class. The object will be saved to the database immediately. |
| get-objectB | Retrieve a single object by its ID from a Parse class |
| update-objectB | Update an existing object in a Parse class |
| delete-objectB | Delete an object from a Parse class by its ID |
| query-objectsA | Query objects from a Parse class with filters, sorting, and pagination. Supports MongoDB-style query operators. |
| signup-userB | Register a new user account. Username and password are required. |
| login-userA | Authenticate a user with username and password |
| logout-userA | Log out the currently authenticated user |
| get-current-userA | Get the currently authenticated user |
| update-userC | Update a user's information |
| delete-userB | Delete a user account |
| request-password-resetB | Send a password reset email to a user |
| query-usersA | Query user accounts with filters |
| upload-fileB | Upload a file to Parse. Provide base64-encoded content. |
| delete-fileB | Delete a file from Parse storage |
| create-roleB | Create a new role for role-based access control |
| get-roleC | Get information about a role |
| add-users-to-roleC | Add users to a role |
| remove-users-from-roleB | Remove users from a role |
| query-rolesA | List all roles |
| get-schemaA | Get the schema definition for a Parse class |
| get-all-schemasA | Get all class schemas in the Parse application |
| create-classA | Create a new Parse class with optional field definitions |
| add-fieldA | Add a new field to an existing Parse class |
| delete-fieldA | Delete a field from a Parse class (WARNING: This will delete all data in that field!) |
| delete-classA | Delete an entire Parse class (WARNING: This will delete all objects in the class!) |
| get-configA | Get Parse Config parameters for remote app configuration |
| set-configC | Set Parse Config parameters (requires masterKey) |
| run-cloud-functionC | Execute a Cloud Code function defined on the Parse Server |
| aggregateB | Run an aggregation pipeline on a Parse class (similar to MongoDB aggregation) |
| distinctB | Get distinct values for a field in a Parse class |
| set-object-aclB | Set Access Control List (ACL) permissions on an object |
| add-relationC | Add objects to a relation field |
| remove-relationB | Remove objects from a relation field |
| query-relationB | Query objects in a relation field |
| batch-createB | Create multiple objects in a single batch operation |
| batch-deleteA | Delete multiple objects in a single batch operation |
| query-nearB | Query objects near a geographic point |
| query-within-boxA | Query objects within a geographic bounding box |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Getting Started with Parse | Introduction to Parse Server and Parse JS SDK setup |
| Parse Objects | Working with Parse.Object - creating, saving, updating, and deleting data |
| Parse Queries | Querying data with Parse.Query - filters, sorting, pagination, and operators |
| Parse Users | User management - signup, login, sessions, and authentication |
| Parse Files | File storage and management with Parse.File |
| Roles and ACLs | Role-based access control and Access Control Lists |
| Cloud Code | Server-side functions, triggers, and background jobs |
| Live Queries | Real-time data subscriptions with LiveQuery |
| Schema Management | Managing class schemas and field definitions |
| Security Best Practices | Security guidelines for Parse applications |
| Relations | Working with relations between objects - pointers and Parse.Relation |
| GeoPoints | Geolocation queries with Parse.GeoPoint |
| Parse Config | Remote app configuration with Parse.Config |
TDQS
Scored across 39 tools
Each tool targets a distinct resource type and action, with clear separation between object, user, role, schema, file, config, relation, batch, and geo operations. Even similar tools like query-near and query-within-box are clearly differentiated by their spatial semantics.
All tool names consistently follow a verb-noun pattern using lowercase and hyphens (e.g., create-object, get-schema, add-users-to-role). Multi-word actions maintain a uniform structure, making the API predictable and easy to navigate.
At 39 tools, the server offers an extensive surface that exceeds the recommended range for typical MCP servers. While each tool is purposeful, the sheer number makes the toolkit feel heavy and may increase the cognitive load for agents.
The tool set provides comprehensive coverage of Parse Server capabilities, including full CRUD for objects and users, file management, role-based access control, schema operations, configuration, aggregation, relations, and geo queries. There are no significant gaps that would prevent completing core workflows.