Inspect the owning configuration
- Open Tools → Plugins and filter by the relevant source.
- Read the installed server or plugin’s name, source, status, and transport.
- Check that the active Code harness is the one that owns or receives this configuration.
- Use the service’s configuration and authentication requirements for that source; do not assume a token for one server authenticates another.
The discover cards are examples, not installable integrations. A visible card toggle is not a reliable way to revoke runtime access in this build; use the actual owning configuration or credential controls.
Authenticate a configured Rudr resource
When In-house MCP authentication is available:
- Select Configured MCP resource and verify Source and Working folder.
- Read whether it is Authenticated, Authentication expired, or Authentication needed.
- If the resource supports token entry, enter its credential in MCP access token and choose Save authentication.
- Check the refreshed status. If it says Saved for this app session only, do not assume persistence after restarting.
- Use Remove authentication when you intentionally want to remove that resource’s saved authentication.
Some local servers use credentials from their configured environment and do not offer token entry here. This panel is not a generic browser OAuth button for Claude or Codex servers.
Review scopes and recover errors
Check the service’s requested account and permissions before authenticating. Tool access can include writes; a connected status does not make every operation read-only. If authentication fails, preserve the sanitized error and selected resource identity, then verify the correct service-specific token or environment configuration.
See tool inspection, permissions, and problem reporting.