Start with one real question and leave with a next step.
Start with the question in front of you, then use the guide to make the next decision easier.
Try saying
“I am trying to make this decision. What should I look at first?”
Start with context
Bring the smallest useful example.
Look for the signal
Separate what is known from what is assumed.
Take one step
Choose an action you can review.
Fonio MCP (Community)
What this is
The fonio-mcp-community repository is an unofficial, open-source MCP server for fonio.ai's public API. It is MIT licensed and designed for people who want to run the server themselves from Claude, Cursor, ChatGPT, or another MCP client.
It is not an official fonio product, not a Specky-hosted service, and not a replacement for fonio's own login or support. If fonio publishes an official MCP later, prefer the official implementation.
What it can do
- Search the community snapshot of fonio's help content and API reference.
- Produce paste-ready assistant prompts, knowledge-base drafts, and examples.
- Validate a fonio API key and inspect remote integration-manifest servers.
- Prepare an outbound call, then place it only after the destination and short-lived confirmation match.
The server does not claim to create or save an assistant when the public fonio API does not expose that operation. The model receives instructions and output; you still review and apply the result in fonio.
Recommended setup: run it yourself
Clone the repository and run the local stdio server:
git clone https://github.com/fathyshalaby/fonio-mcp-community.git
cd fonio-mcp-community
npm install
cp .env.example .env.local
# Add a long random FONIO_MCP_SECRET for HTTP/OAuth mode
npm run mcp
For a remote HTTP MCP deployment, self-host it on your own HTTPS origin and set FONIO_MCP_SECRET plus NEXT_PUBLIC_MCP_ORIGIN. The repository also documents Docker and Vercel deployment.
Then add your own origin to the MCP client. For Claude Code:
claude mcp add --transport http unofficial-fonio-mcp https://your-host.example/mcp
The fonio API key belongs in the community server's authorized session or local environment. Never paste it into a public issue, a client config committed to Git, or a volunteer-hosted server you do not trust.
Outbound-call safety
Outbound calls can cost money and reach a real person. The community server prepares the exact number first and requires both a short-lived confirmation token and a matching confirmedToNumber before it can dial. That is a safety boundary, not an intent gate; it protects against an accidental or repeated call.
When to use this alongside Specky
Use the community MCP when you want an agent to work directly with fonio's assistant-building and public API surface. Use the Specky fonio integration when you want finished fonio call transcripts to become evidence in your Specky Product Graph, with the webhook delivery status and optional follow-up call workflow in the same product workspace. They solve different jobs and can be used together.
Source and support
The community project is provided as-is, with no uptime, support, or liability promise from Specky or fonio GmbH. Check the official fonio documentation if the community snapshot and the live product disagree.
Ready to apply this?
Start with your own product and keep the first read grounded. You can create an account after you see the result.