nyxidlisted

# NyxID for Cursor Use NyxID when the user wants a credential-backed downstream API call, service discovery, or a connection to an external service. NyxID stores the provider credential and injects it when it proxies a tool call. The agent should see the downstream response, not the provider secret. ## MCP-first workflow The plugin configures the MCP endpoint at `<base URL>/mcp`, using the plugin's `NYXID_BASE_URL` variable for the configured NyxID base URL. Authenticate in the browser when Cursor prompts. The built-in MCP tools are: - `nyx__discover_services` lists catalog services that are not connected. Use its optional `query` or `category` filters when useful. - `nyx__list_connected_services` lists the user's connected services and availability. - `nyx__connect_service` starts a connection for a `service_id` returned by discovery. Omit `credential` by default: when a human connection is needed, the result contains a hosted connection URL and `connect_link_id`. - `nyx__wait_for_connection` waits on that `connect_link_id`; call it after the user completes the hosted flow, then retry the original operation. - `nyx__search_tools` searches the connected service tools and returns their input schemas. - `nyx__call_tool` invokes a discovered tool by its full name. Pass `arguments_json` as a JSON string matching the schema returned by `nyx__search_tools`. Per-service tools may also be listed directly after a connection. Their names are derived from the service slug and OpenA