The Fibric community.
Fibric is open at the seams. The operators and connectors that run on it are integrations built on MCP, which means anyone can build one and any operator can run it. This is where the people doing that work talk, share what they've shipped, and help each other ship the next thing.
Three places to show up.
No walled garden. The code is in the open, the conversation is in the open, and questions get answered by people who have actually shipped a connector.
GitHub
The SDK, the reference connectors, and the issues that move the platform forward. Read the source, file a bug, open a pull request. This is where the work lives.
github.com/fibricCommunity space
A real-time room for the people building on Fibric. Ask a question about the executor, show off a connector you wired up over the weekend, or work through a governance edge case with someone who has hit it before.
discord.gg/fibricDiscussions
For the longer threads: design proposals, "is this the right capability boundary," and the questions worth keeping searchable. Slower than chat, but it sticks around for the next person.
github.com/fibric/discussionsThings you can use today.
You don't have to start from a blank file. There's a directory of connectors, a set of guides, and a changelog that tells you exactly what changed and when.
-
01 · Browse The connector directoryMarketplace →
Every operator and connector you can install, in one place. The platform is free; you pay for the integrations you actually run. Because capability points to a connector through indirection, swapping one vendor for another is config, not a rewrite.
-
02 · Learn GuidesRead the guides →
Step-by-step walkthroughs for the things people actually want to do: connect a system, set an intent, write a connector, read a receipt. Written plainly, with real examples, no hand-waving over the governed parts.
-
03 · Track ChangelogSee what's new →
What shipped, version by version. New capabilities, SDK changes, and the things that might affect a connector you maintain. If you build on Fibric, this is the page worth bookmarking.
Write a connector. Ship it to everyone.
An integration on Fibric is an MCP server with governance baked in. The SDK gives you the shape; the kernel handles the hard parts so you never write them twice.
-
Define it with the SDK
defineConnector, tool, and auth are most of what you need. You describe the capability and the tools; the SDK wires it as an MCP server. Every signal becomes one canonical envelope on the way in.
-
Let governance do its job
You don't implement safety yourself. The model proposes a validated plan and a deterministic executor disposes. Single-flight per entity and idempotency keys are kernel primitives, so a runaway loop is structurally impossible and trust fails closed.
-
List it in the marketplace
Once it's working, publish it. Other operators install it the same way they install anything else, and every action it takes writes an attributable, reversible receipt. Your connector inherits the governance, automatically.
Where the community shows its work.
Two places to come up for air: the things we do live, and the things people have built that are worth a closer look.
The best way in is to build something.
Connect a system, set an intent, and watch a governed action run. Then come tell the community what you wired up.