RequestRocket Platform
Authentication
Sign up and in to the RequestRocket app with hosted login.
Authentication depends on what is connecting. A person signs in to the app. An agent connects to the Core MCP. A script sends a user token to the Core API. Callers of your proxy or MCP server use an inbound credential instead.
| Connection | Credential | What it authorizes |
|---|---|---|
| RequestRocket app | Hosted login session | The app actions allowed by the user's organisation roles |
| Core MCP | MCP OAuth token or user token | Management tools acting as that RequestRocket user |
| Core API | User token | Management API calls acting as that RequestRocket user |
| Proxy or published MCP server | Inbound credential | Calls through that configured proxy or MCP server |
A user token is not an inbound credential. Do not give a caller your RequestRocket user token.
Open the sign-in page
Open https://app.requestrocket.com/login.
New to RequestRocket? Use https://app.requestrocket.com/signup to create an account.
Sign out
Sign out when you are done. Signing out ends the browser session. It does not delete the user tokens you created.
Change a password
Sign out of RequestRocket and at your next sign in, click "Forgot password" and follow the prompts.
Troubleshooting
| Problem | What to do |
|---|---|
| Hosted login does not accept the password | Use Forgot password on the hosted sign-in page. |
A script receives 401 | Add the user token to the Core API Authorization header. |
A proxy call receives 401 | Send the proxy's inbound credential, not an app session or user token. |