Skip to content

Cursor Apollo entity_profile

How to: Cursor Apollo entity_profile

client:Cursor transport:streamable-http tool:entity_profile

Add Apollo to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "apollo": {
      "url": "https://gateway.pipeworx.io/apollo/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something entity_profile does. Cursor lists the server's tools on connect and calls entity_profile itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Apollo's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

Apollo will not start until these are set, so entity_profile never becomes available.

  • PIPEWORX_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.