Fibrous MCP Server

Most developer tooling work still happens through a UI a human drives. Fibrous MCP MCP server moves it into the conversation instead. Fibrous Model Context Protocol Server.

The short version

MCP server providing AI agents with tools for multi-chain DeFi operations using the Fibrous SDK.

• get-supported-tokens - List available tokens
• get-supported-protocols - List DEX protocols
• get-best-route - Find optimal swap routes
• get-best-route-batch - Find optimal routes for batch swaps (Starknet only)
• build-transaction - Generate transaction data
• build-batch-transaction - Generate batch transaction data (Starknet only)

The tools it exposes

The server publishes 4 tools. What each one is for:

• Prerequisites — The Prerequisites tool exposed by this server
• Setup — The Setup tool exposed by this server
• Architecture — The Architecture tool exposed by this server
• Performance — The Performance tool exposed by this server

What it needs from you

Configuration is passed through the environment: BASE_RPC_URL, BASE_PRIVATE_KEY, STARKNET_RPC_URL, STARKNET_PRIVATE_KEY, STARKNET_PUBLIC_KEY, SCROLL_RPC_URL, SCROLL_PRIVATE_KEY, FIBROUS_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 18+ - pnpm (recommended) - TypeScript 5.0+

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Fibrous MCP's toolset — Prerequisites, Setup, Architecture and 1 more — is a fair guide to whether it matches your workflow. It is maintained by ahmetenesdur; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.