How to integrate Fibery MCP with OpenClaw

Framework Integration Gradient
Fibery Logo
OpenClaw Logo
divider

Introduction

OpenClaw is the fastest growing agent harness out there, which can work 24/7 to automate almost any kind of tasks. However, its capabilities are limited to the tools it has access to. Composio allows your OpenClaw to access Fibery with authentication management handled for you. You can execute actions on Fibery via your favorite OpenClaw interface (Telegram, WhatsApp, TUI, etc), whichever you prefer.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 850+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

How to install Fibery with OpenClaw

Using Composio API Key and Setup Prompt

Copy the setup prompt from the OpenClaw dashboard
  • Run it in your OpenClaw chat interface.
  • Authenticate Fibery from the dashboard
  • Go back to your OpenClaw interface and start asking questions.

Using OpenClaw/Composio Plugin

1. Install OpenClaw Composio plugin

bash
openclaw plugins install @composio/openclaw-plugin

2. Copy the API Key from dashboard.composio.dev

3. Setup OpenClaw Config

openclaw config set plugins.entries.composio.config.consumerKey "ck_your_key_here"

4. Restart OpenClaw

openclaw gateway restart

5. Go to your chat interface and start asking questions.

6. When prompted, authenticate the app and you're all set.

How It Works

The plugin connects to Composio's MCP server at https://connect.composio.dev/mcp and registers all available tools directly into the OpenClaw agent. Tools are called by name — no extra search or execute steps needed.

If a tool returns an auth error, the agent will prompt you to connect that toolkit at dashboard.composio.dev.

Configuration

{
  "plugins": {
    "entries": {
      "composio": {
        "enabled": true,
        "config": {
          "consumerKey": "ck_your_key_here"
        }
      }
    }
  }
}
OptionDescriptionDefault
enabledEnable or disable the plugintrue
consumerKeyYour Composio consumer key (ck_...)
mcpUrlMCP server URL (advanced)https://connect.composio.dev/mcp

What is the Fibery MCP server, and what's possible with it?

The Fibery MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Fibery account. It provides structured and secure access to your workspace data, so your agent can perform actions like querying entities, managing custom apps, running GraphQL queries, and organizing files—all with zero manual integration code.

  • Entity query and retrieval: Instantly fetch detailed information or lists of entities based on type, filters, and fields, making it easy to surface project or task data as needed.
  • Custom app and endpoint management: Let your agent list, inspect, or delete custom apps and endpoints, streamlining workspace configuration and app lifecycle management.
  • Flexible data manipulation with GraphQL: Execute custom GraphQL queries and mutations against your Fibery space to fetch, update, or manipulate structured data programmatically.
  • File and resource cleanup: Remove outdated files or entities efficiently, helping keep your workspace organized and clutter-free with automated deletions.
  • Authentication and workspace insights: Validate tokens securely and retrieve workspace or app metadata, ensuring your agent always operates with up-to-date context and permissions.

Supported Tools & Triggers

Tools
Delete Custom App EndpointTool to delete a specific custom app endpoint.
Delete EntityTool to delete a specific Fibery entity by its ID.
Delete FileTool to delete a specific file.
Execute GraphQL QueryTool to execute GraphQL queries or mutations against a Fibery space.
Authenticate (validate token via API call)Tool to validate existing Fibery personal API token by performing a real API call.
Get App InformationTool to retrieve application information.
Get Custom App EndpointsTool to list custom app endpoints.
Get Custom AppsTool to list all custom apps in the Fibery workspace.
Get EntitiesTool to query Fibery entities.
Get Fibery EntityTool to retrieve detailed info of a specific Fibery entity by its ID.
Get FileTool to retrieve a file by its secret or id.
Get GraphQL SchemaTool to retrieve the GraphQL schema for the current workspace.
Get User PreferencesTool to retrieve the current user's UI preferences.
Refresh access tokenTool to refresh an access token using a refresh token.
Authenticate with username and passwordTool to authenticate with Fibery using resource owner password credentials.
Create EntityTool to create a new Fibery entity.
Fetch Data from SourceTool to fetch data from a specified source.
POST_FETCH_DATA_COUNTTool to return the count of records for a given Fibery type (source).
Fetch Datalist OptionsTool to fetch options for a datalist filter field.
Fetch SchemaTool to fetch predefined data schema.
Exchange OAuth2 authorization codeTool to finalize OAuth2 authentication for Fibery custom apps.
Revoke Access TokenTool to revoke an existing Fibery API access token.
Validate Fibery accountTool to validate account credentials.
Validate FilterTool to validate filter definitions.
Update EntityTool to update an existing Fibery entity.
Update User PreferencesTool to update the current user's preferences by using the Commands API.
Upload FileTool to upload a file to Fibery.

Conclusion

You've successfully integrated Fibery with OpenClaw using Composio plugin. Now interact with Fibery directly from your terminal, Web UI, or any messenger app using natural language commands.

Key benefits of this setup:

  • Seamless integration across TUI, Web UIs, and Messenger apps like Telegram, WhatsApp, Slack, etc.
  • Natural language commands for Fibery operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 850+ apps for cross-app workflows
  • Programmatic tool calling for complex tool chaining

Next steps:

  • Try asking OpenClaw to perform various Fibery operations
  • Explore cross-app workflows by connecting more toolkits like Calendar, Slack, Notion, etc.
  • Build complex automation scripts that leverage OpenClaw's 24/7 running capabilities

How to build Fibery MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Fibery MCP?

With a standalone Fibery MCP server, the agents and LLMs can only access a fixed set of Fibery tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Fibery and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with OpenClaw?

Yes, you can. OpenClaw fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Fibery tools.

Can I manage the permissions and scopes for Fibery while using Tool Router?

Yes, absolutely. You can configure which Fibery scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Fibery data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.