Fibery ACTION
List Entities
Lists entities for a type. See the docs here
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Fibery account once, then configure and run List Entities from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "fibery-list-entities",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
fibery: { authProvisionId: "apn_xxxxxxx" },
type: "Type",
where: "Where",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "fibery-list-entities",
"configured_props": {
"fibery": { "authProvisionId": "apn_xxxxxxx" },
"type": "Type",
"where": "Where"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "fibery",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "fibery-list-entities",
arguments: {
type: "Type",
where: "Where",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
type Type | string | A custom type in your Fibery account Required Dynamic |
where Where | string | A list of expressions to filter the results. See docs here.
E.g. [ "=", [ "Development/name" ], "$pipedream" ] Optional |
params Params | object | The params to pass with the where query. E.g. { "$pipedream": "pipedream" } Optional |
fields Fields | string[] | The select fields for an entity type. This prop is an array of strings.
Each string should have the same structure as in the docs
E.g. ["fibery/id",{"Development/Team":["fibery/id"]}] Optional Dynamic |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- fibery-list-entities
- Version
- 0.0.2
- App
- Fibery
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗