Skip to content

Cursor Re:port Flow MCP Resource/server-info

How to: Cursor Re:port Flow MCP server-info

client:Cursor transport:streamable-http resource:server-info

Add Re:port Flow MCP to Cursor

  1. 01

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

{
  "mcpServers": {
    "reportflow-mcp": {
      "url": "https://mcp.re-port-flow.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    server-info is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.

  3. 04

    If it does not appear, check that Re:port Flow MCP is connected and that you are looking at its resources rather than its tools.

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

Set these first

Re:port Flow MCP will not start until these are set, so it never reaches Cursor.

  • REPORTFLOW_CLIENT_ID
  • REPORTFLOW_AUTH_URL
  • REPORTFLOW_API_BASE_URL
  • REPORTFLOW_TOKEN_STORE

Same resource, other clients

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.