mcp-parse

claude mcp add mcp-parse -- node /opt/mcp/mcp-parse/build/index.js
# no server env: connection details are passed per call

It speaks Parse Server's REST API: introspect the schema, run queries and aggregations, do CRUD on objects, and call cloud code functions. So an agent can answer "what classes exist and what is in them" on a live backend.

Stateless on purpose

There is no configured connection. Every tool call carries its own serverUrl, appId, restApiKey, and masterKey, so one running server can talk to as many Parse apps as you point it at. When a master key is present it takes precedence over the REST key, which is what you want for schema reads and anything the client-facing key is not allowed to see. Nothing about which backend you are touching is baked in at start time.