Inspect tools by source
- Choose Tools in the sidebar.
- Use the Plugins, Skills, or Activity view for the kind of information you need.
- Filter by Claude MCP, Codex MCP, In-house, or Built-in where available.
- Read the source, status, and transport details on an installed integration.
- Open Recent activity to inspect reported invocations and their outcomes.
A similarly named tool from two sources is not necessarily the same configuration or account. Check which harness owns it before expecting the active task to use it. A tool invocation history is evidence of reported calls, not a guarantee that a remote service completed every intended effect.
Distinguish installed tools from examples
The discover section is labeled Examples — not installable from Rudr yet. Its cards are not working one-click installations. Do not infer that a featured service is connected or that it has access to your account.
In this build, a tool card’s on/off presentation is local to the Tools view. It should not be treated as a persisted runtime disable action or a security boundary. For actual credential removal, use the applicable authentication control or manage the owning provider’s configuration.
Recover missing capabilities
If a tool is absent, first check the source filter and selected harness. Then inspect whether its server is configured and authenticated. Do not solve a missing tool by sending credentials in a prompt.
Use MCP and plugins for the authentication controls Rudr actually provides, skills and commands for instruction attachments, and Diagnostics for harness capability limits.