Your front door
MCP client
VS Code, Claude, Cursor, or another Streamable HTTP client.
FrootAI — AmpliFAI your AI Ecosystem Get Started
Connect to FrootAI knowledge, attach external MCP servers through one local router, or run the specialized Harvest pipeline.
The MCP system, in motion
Follow the request path to see what FrootAI MCP hosts, what the local federation router connects, what Orchard Harvest produces, and where the server directory fits.
Hosted FrootAI MCP
Ask one public endpoint for grounded FrootAI architecture, modules, Plays, and marketplace guidance.
Your front door
VS Code, Claude, Cursor, or another Streamable HTTP client.
Public endpoint
Receives MCP requests and routes them to the hosted knowledge surface.
Grounded context
Seven tools across the protocol, modules, Plays, and directory guidance.
Boundary: No install and no downstream credentials. The hosted endpoint exposes seven public, read-oriented FrootAI tools.
Start here
Use FrootAI MCP for knowledge and federation, Harvest MCP for repository conversion, or the directory to find an external server. Orchard Catalog is a legacy reference, not another product you need to choose.
Knowledge + federation
Use the hosted endpoint for seven public knowledge tools, or run frootai-mcp locally to attach trusted external servers and keep credentials on your machine.
Repository-to-play pipeline
Use the specialized nine-tool pipeline when you need to discover, extract, retrieve, import, customize, approve, or review a Solution Play.
External MCP discovery
Find an external server and inspect its publisher, trust evidence, credentials, package, and freshness. The directory does not connect servers by itself.
Browse the directory
Review trust and credentials
Attach with local frootai-mcp
Open account and usage
The local FrootAI MCP process is the unified router and bridge. It keeps downstream credentials local and exposes attached tools as <area>.<tool>.
Publisher trust is evidence, not a guarantee. Review credentials, permissions, destructive capabilities, and source before connecting a server.
Listed does not mean federated. Validated specs, local router support, hosted capabilities, and specialized packages are labeled separately.