list-user-connectors
List the project's user-defined connectors: published ones, and your own drafts. Needs the fabric:orchestrate.read grant.
curl -sS -X POST https://fabric.wexa.ai/mcp/$FABRIC_PROJECT_ID \
-H "authorization: Bearer $FABRIC_API_KEY" \
-H "Mcp-Session-Id: $MCP_SESSION_ID" \
-H "content-type: application/json" -H "accept: application/json" \
-d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list-user-connectors","arguments":{}}}'{
"content": [
{
"type": "text",
"text": "{\"lifecycle_id\":\"qlc_000017\",\"result\":{\"connectors\":[{\"connector_id\":\"6b1a3d5e7f9c0b2a4d6e8f02\",\"name\":\"Payroll\",\"mode\":\"live\",\"lifecycle\":\"draft\",\"access_scope\":\"individual\",\"action_count\":1}]}}"
}
],
"isError": false
}Parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
| none | This tool takes no parameters. |
Show full response
An example response, with one draft.
{
"content": [
{
"type": "text",
"text": "{\"lifecycle_id\":\"qlc_000017\",\"result\":{\"connectors\":[{\"connector_id\":\"6b1a3d5e7f9c0b2a4d6e8f02\",\"name\":\"Payroll\",\"category\":\"user_payroll\",\"description\":\"Read employees from the payroll API.\",\"logo\":\"\",\"mode\":\"live\",\"connected\":false,\"lifecycle\":\"draft\",\"access_scope\":\"individual\",\"user_id\":\"6a0f1e2d3c4b5a6978877665\",\"has_credentials\":true,\"base_url\":\"https://payroll.example.com/v1\",\"action_count\":1,\"actions\":[{\"key\":\"get_employee\",\"name\":\"Get employee\"}],\"project_id\":\"6a0f1e2d3c4b5a6978877601\",\"org_id\":\"6a0f1e2d3c4b5a6978877600\"}]}}"
}
],
"isError": false
}Keeping the lifecycle_id is what lets you ask later why a call was allowed, refused or held.
More details
Response fields
connectors is the list. Each connector has these fields:
connector_id: The connector's id.name: Its name.category: Its category. A user-defined connector's category starts withuser_.description: Its description; empty when it has none.logo: Its logo; empty when it has none.mode:live(calls the real API) orsimulated.connected: Whether its actions are skills agents can use.lifecycle:draftorpublished.access_scope:individual(a draft),projectororganization.user_id: Its author.has_credentials: Whether credentials are saved. The credentials themselves are never returned.base_url: A live connector's base URL.action_count: How many actions it has.actions: Its actions, each with akeyand aname.project_id: This project.org_id: This organization.
These are the connectors people built from an API description, as opposed to the ones Wexa offers in its catalog. You see the published ones, and your own drafts. Another person's draft is never listed.
A draft is its author's alone. A published connector is visible in its project, or in every project of its organization when it was published there. For one connector's full definition, call get-user-connector.
Only reads, so not marked consequential: it is audited lightly and is never held for approval.
Every tool call works the same way: How every tool call works.