---
title: "Fibery"
description: "Read workspace database/field metadata and one explicit page of selected entity fields. Customer workspace OAuth with PKCE/refresh or a personal API token; no arbitrary commands, relation expansion, writes or token inven"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Fibery

<p>Read workspace database/field metadata and one explicit page of selected entity fields. Customer workspace OAuth with PKCE/refresh or a personal API token; no arbitrary commands, relation expansion, writes or token inventory.</p>

<details data-command-index><summary>What you can do (2)</summary>
<h2>What you can do</h2>
<p>Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/fibery#command-fibery-schema-get">Read workspace schema</a> — <code>fibery.schema.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/fibery#command-fibery-entities-list">Read selected entity fields</a> — <code>fibery.entities.list</code></td>
<td>Read</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/fibery">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for Fibery, then enter the issued values in the connection form below.</p>
<ol>
<li>For workspace OAuth, an administrator registers an application in Settings → OAuth Applications and registers <a href="https://api.tooluse.net/v1/oauth/callback">https://api.tooluse.net/v1/oauth/callback</a>. Enter its client ID and secret plus the workspace subdomain (only the name before .fibery.io) in this connection form, select reads, save and click Sign in to provider. Tooluse.net uses S256 PKCE, server-side Basic client authentication and openid/offline scopes for refresh. Workspace applications authorize only members of that workspace; a public cross-workspace app must be registered with Fibery Support. OAuth grants inherit the user&#39;s permissions, not read-only provider scopes; Tooluse.net restricts these commands to reads. Alternatively, create a personal token in Workspace menu → API Tokens, paste it into Personal API token and leave OAuth/access-token fields empty. It uses Token authentication, while OAuth uses Bearer. Use Read workspace schema for exact database/field names, then explicitly choose fields and limit/offset. Disconnect removes the local OAuth grant; revoke the app or personal token in Fibery to invalidate access at source. Use a separate connection when switching credential modes.</li>
</ol>
<p><a href="https://developers.fibery.com/guides/getting-started/authentication">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>Workspace subdomain</td>
<td>Required</td>
</tr>
<tr>
<td>Access token (optional with OAuth)</td>
<td>Optional</td>
</tr>
<tr>
<td>Personal API token (optional)</td>
<td>Optional</td>
</tr>
<tr>
<td>Fibery OAuth client ID</td>
<td>Optional</td>
</tr>
<tr>
<td>Fibery OAuth client secret</td>
<td>Optional</td>
</tr>
<tr>
<td>Registered OAuth redirect URI (optional)</td>
<td>Optional</td>
</tr>
<tr>
<td>Return URL after authorization</td>
<td>Optional</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-fibery-schema-get">
<summary><span>Read workspace schema — <code>fibery.<wbr>schema.<wbr>get</code></span></summary>
<p>Read database and field names/types from the workspace schema. Does not read entity values, token inventory or write metadata; one bounded response. Large schemas can exceed the existing response bound.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/fibery?command=fibery.schema.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<p>This tool has no input parameters.</p>

<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/fibery/commands/fibery.schema.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-fibery-entities-list">
<summary><span>Read selected entity fields — <code>fibery.<wbr>entities.<wbr>list</code></span></summary>
<p>Read one explicit limit/offset page from a database, selecting only the named flat fields plus fibery/id. No expressions, nested relation traversal, arbitrary command dispatch, writes or automatic paging.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/fibery?command=fibery.entities.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>body.type</code></td>
<td>string</td>
<td>Required</td>
<td>Exact API database/field name, including its namespace, as returned by Read workspace schema.</td>
<td><code>minLength: 3; maxLength: 200; pattern: &quot;^[^/\\x00-\\x1f\\x7f]+/[^/\\x00-\\x1f\\x7f]+$&quot;</code></td>
</tr>
<tr>
<td><code>body.fields</code></td>
<td>array</td>
<td>Required</td>
<td>Exact flat field names to return; fibery/id is always added.</td>
<td><code>minItems: 1; maxItems: 20; uniqueItems: true</code></td>
</tr>
<tr>
<td><code>body.fields[]</code></td>
<td>string</td>
<td>Optional</td>
<td>Exact API database/field name, including its namespace, as returned by Read workspace schema.</td>
<td><code>minLength: 3; maxLength: 200; pattern: &quot;^[^/\\x00-\\x1f\\x7f]+/[^/\\x00-\\x1f\\x7f]+$&quot;</code></td>
</tr>
<tr>
<td><code>body.limit</code></td>
<td>integer</td>
<td>Required</td>
<td>Maximum entities in this one response.</td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>body.offset</code></td>
<td>integer</td>
<td>Required</td>
<td>Zero-based entity offset.</td>
<td><code>minimum: 0; maximum: 9007199254740991</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/fibery/commands/fibery.entities.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "type": "CRM/Account",
    "fields": [
      "CRM/Name"
    ],
    "limit": 20,
    "offset": 0
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://developers.fibery.com/guides/getting-started/authentication">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/fibery/index.mdx