Connectors
Bring relevant context into the task.
Use authorized context from connected systems where the connection, permissions, and workflow support it.
Directory
2,042 listings across 34 categories
Browse the catalog by name, publisher or category. Listings come from the open APIs.guru directory (CC0). A listing describes a service; it does not mean a connector is configured or available in your workspace.
Directory listing
Meshery API.
- Category
- Cloud
the purpose of this application is to provide an application that is using plain go code to define an API This should demonstrate all the possible comment annotations that are available to turn go code into a fully compliant swagger 2.0 spec
This is a catalog listing. It does not mean the service is connected to your workspace; availability depends on what is configured and permitted for you.
Connected Context
Know the source and its scope.
A connection is useful when its boundaries are understandable.
- 01
Context
Access only what the supported connection permits.
- 02
Source visibility
See the referenced source where available.
- 03
Review
Keep sensitive external actions behind required human review.
Permissions
Read access is not write permission.
Connections and actions vary by service and configuration. Reading context does not imply permission to write. Confirm availability and data handling in documentation; no integration list is established here.
- Workspace context
- Connector boundary
- External tool
Action requires approval
Results return to the workspace