Create System Integrations Through Conversation
Connectors are the core of FIM Agent. A connector represents an external system's interface — Agent reads and writes data through connectors, and the platform auto-handles authentication and request management.
Three Ways to Connect Any System
FIM Agent's connectors don't depend on pre-built integrations. Your team can quickly create them through any of these methods:
Import OpenAPI Docs
Upload the target system's Swagger / OpenAPI file (YAML, JSON, or URL), auto-parse and generate complete connectors with all Actions. Create new or append to existing.
AI Conversation Generation
Describe interface needs in natural language in the AI panel, or provide API docs for AI to interpret. Supports conversational iteration — generate → modify → test → publish, all in conversation.
MCP Ecosystem
If the target system already has a community-maintained MCP Server, search and one-click install from MCP Hub. You can also develop custom MCP Servers.
Import API Docs, Auto-Generate Connectors
availableImport OpenAPI spec files (YAML, JSON, or URL), and the system auto-parses interface definitions, generating complete connectors with all Actions in one go.
Supports two modes: create new (generate a brand new connector from docs) and append (add new Actions to existing connectors). Each generated Action automatically includes method, path, parameter definitions, and LLM-readable tool descriptions, ready for Agent to recognize and invoke.
Create Connectors via AI Conversation
availableNo standard API docs? No problem. In the Action editor's built-in AI panel, describe your interface needs in natural language:
You can also provide API doc snippets directly to Agent, letting AI interpret and auto-generate connector configurations.
Verified case: Created a ZiHe contract system connector through conversation — provided API docs → Agent generated Actions → tested → published, entirely within the conversation.
Leverage Community System Adapters (MCP Integration)
availableNative support for Model Context Protocol (MCP). Connect any MCP Server as Agent tools — third-party MCP ecosystem works out of the box.
STDIO (local process)
SSE (remote server)
Streamable HTTP (MCP 2025-03-26 spec)
Built-in MCP Hub: search Smithery Registry community MCP Servers, one-click install for remote services, pre-filled parameters for quick local configuration.
Automatic Credential Handling
availableConnectors support multiple authentication methods, automatically injected at runtime:
Agent doesn't need to handle auth details when calling connectors — the platform auto-attaches credentials before requests are sent.
Production Verified
GitHub
Repo listing, Issue viewing, PR management
ZiHe Contract System
Search, detail, compare, timeline, statistics
MCP Community Ecosystem
Smithery Hub one-click install
These are verified examples. FIM Agent's connector model can integrate any system with an HTTP API — ERP, CRM, OA, finance software, databases, and custom internal services.
Manual + AI-assisted creation, stored in platform database
Connector export / import / fork, exportable as standalone MCP Server
Upload OpenAPI docs, AI fully auto-generates complete connectors
Connector export/import/fork and official pre-built connector library coming soon. When the connector ecosystem reaches sufficient scale, a dedicated connector directory page will launch.