Operate the system
Manage plugins, marketplaces, and connectors
Plugins bundle capabilities; connectors expose external apps or services; provider support varies. FireCursor makes those integration paths discoverable without pretending one provider’s setup applies to all of them.
Quick answer
The shortest useful version.
Start with the target provider, inspect installed plugins and connector availability, verify the source and permissions, follow the supported setup path, and remove integrations you no longer trust or use.
Step by step
Do this with confidence.
- 01
Choose the provider first
A connector that works in one runtime may not exist or may authenticate differently in another.
- 02
Inspect provenance
For plugins and marketplace indexes, confirm the publisher, source, version, and included capabilities before adding them.
- 03
Review permissions
Understand connected accounts, read and write scopes, external side effects, and revocation paths.
- 04
Verify in a bounded task
Test discovery, sign-in, and one safe read operation before authorizing consequential actions.
Why provider-aware setup wins
A universal ‘Connect’ button can hide meaningful differences in authentication, availability, and consequence. FireCursor routes users into the setup or usage path the active provider actually supports.
The result is less magical-looking and much more dependable.